We have recently hit a hard fork on Mumbai Testnet. If you weren’t able to upgrade the node before block no 25275000
, please follow the below instructions to upgrade and bring your node back in sync.
-
Stop the bor service
sudo service bor stop
-
Navigate to bor directory
cd ~/bor
-
Fetch the latest changes and use Bor v0.2.15-beta2:
git fetch git checkout v0.2.15-beta2
-
Build latest changes
make bor-all
-
Check bor version
ubuntu@ip-20-0-1-195:~/bor$ bor version Bor Version: 0.2.15-beta-2 Git Commit: 111a204bbaa0d6b1e94fa58a56c00dab8adc1652
-
Go back to the home directory
cd ~
-
Download the latest genesis file. We are upgrading the genesis contract through changed genesis.
curl https://raw.githubusercontent.com/maticnetwork/launch/87c417decfe8a1c981b5f6733497d984dd4acc52/testnet-v4/sentry/sentry/bor/genesis.json --output ~/genesis.json
-
Init bor with genesis file
bor --datadir ~/.bor/data init ~/genesis.json
If you are using a non-default
datadir
, please ensure you input the correct one you have been using. -
You should see the output as follows:
... ... INFO [12-03|19:57:02.531] Successfully wrote genesis state database=chaindata hash=... ... INFO [12-03|19:57:02.556] Successfully wrote genesis state database=lightchaindata hash=... ... ...
-
Start the bor service
sudo service bor start
If your node is still not syncing after restarting bor, then follow the below steps:
-
Open bor ipc
bor attach ~/.bor/data/bor.ipc
-
Rewind the chain by a few hundred blocks (to block
25274500
)debug.setHead("0x181A884")
-
Check if the chain has started syncing and has gone past the hardfork block
25275000