The Mumbai testnet will be upgrading to the latest Geth with the Berlin Fork. The Berlin fork block will kick on block number 13996000
. You will need to upgrade before 18th of May to ensure that your node stays in sync. If you do not upgrade your node before that it will be out of Sync.
You can follow the instructions below to upgrade your Node.
We have also added instructions for adding flags for Telemetry. You can add that to you Sentry node and then you can check the Telemetry dashboard with your node listed.
Steps for Upgrading Mumbai Nodes
For you Sentry Node
-
Stop the bor service
sudo service bor stop
-
Navigate to bor directory
cd ~/bor
-
Fetch latest changes and use Bor v0.2.5:
git fetch git checkout v0.2.5
-
Build latest changes
make bor-all
-
Go back to home directory
cd ~
-
Download the berlin genesis file according to your node type:
- Sentry →
curl https://raw.githubusercontent.com/maticnetwork/launch/master/testnet-v4/sentry/sentry/bor/genesis.json --output genesis.json
- Sentry →
-
Init bor with berlin genesis file
bor --datadir ~/.bor/data init genesis.json
-
Start the bor service
sudo service bor start
For Validator Node
-
Stop the bor service
sudo service bor stop
-
Navigate to bor directory
cd ~/bor
-
Fetch latest changes and use Bor v0.2.5:
git fetch git checkout v0.2.5
-
Build latest changes
make bor-all
-
Go back to home directory
cd ~
-
Download the berlin genesis file according to your node type:
- Validator →
curl https://raw.githubusercontent.com/maticnetwork/launch/master/testnet-v4/sentry/validator/bor/genesis.json --output genesis.json
- Validator →
-
Init bor with berlin genesis file
bor --datadir ~/.bor/data init genesis.json
-
Start the bor service
sudo service bor start
Telemetry Setup Instructions for Mumbai Nodes
You need to ensure that you need to update this only on your Sentry Node
-
SSH into your node
-
Edit the file
~/node/bor/start.sh
and add the following line in arguments passed to bor:--ethstats <node-name>:[email protected]:3000
After editing, the bor part of start.sh file should look as follows:
... ... bor --datadir $DATA_DIR \ --ethstats <node-name>:[email protected]:3000 \ --port 30303 \ --http --http.addr '0.0.0.0' \ ... ...
-
Replace above with a fully qualified name according to the Naming convention as below:
<entity_name>-<network_name>--<unique_identifier>
Eg:
vitwit-mumbai-sentry-ip10_0_0_1
blockvigil-mumbai-explorer-1
unique_identifier is just an identifier for you to distinguish between different nodes you are running (if you have multiple nodes).
-
Now, restart bor service:
sudo service bor restart
-
Check if your node is reflecting here https://bor-mumbai.vitwit.com/
Thanks!