From 39ed6e47a4502959f0314c6ca99f481e27757cf7 Mon Sep 17 00:00:00 2001
From: Jerry <jerrycgh@gmail.com>
Date: Thu, 8 Jun 2023 14:05:29 -0700
Subject: [PATCH] Explicitly disable MVHashMap in mining

Currently, we determine if MVHashMap should be enabled by checking the block number with parallelUniverse flag in genesis, which has a value of 0. Some headers' block number is 0, so MVHashMap was enabled, which led to a few errors. Disable this flag explicitly until we figure out a proper hardfork solution.
---
 miner/worker.go | 8 +-------
 1 file changed, 1 insertion(+), 7 deletions(-)

diff --git a/miner/worker.go b/miner/worker.go
index 72fb137389..c46d0b2c8d 100644
--- a/miner/worker.go
+++ b/miner/worker.go
@@ -986,13 +986,7 @@ func (w *worker) commitTransactions(env *environment, txs *types.TransactionsByP
 
 	var depsWg sync.WaitGroup
 
-	var EnableMVHashMap bool
-
-	if w.chainConfig.Bor.IsParallelUniverse(env.header.Number) {
-		EnableMVHashMap = true
-	} else {
-		EnableMVHashMap = false
-	}
+	EnableMVHashMap := false
 
 	// create and add empty mvHashMap in statedb
 	if EnableMVHashMap {