Berlin Fork Upgrade - Mumbai Testnet

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

  1. Stop the bor service

    sudo service bor stop

  2. Navigate to bor directory

    cd ~/bor

  3. Fetch latest changes and use Bor v0.2.5:

    git fetch
    git checkout v0.2.5
    
  4. Build latest changes

    make bor-all

  5. Go back to home directory

    cd ~

  6. 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
  7. Init bor with berlin genesis file

    bor --datadir ~/.bor/data init genesis.json

  8. Start the bor service

    sudo service bor start

For Validator Node

  1. Stop the bor service

    sudo service bor stop

  2. Navigate to bor directory

    cd ~/bor

  3. Fetch latest changes and use Bor v0.2.5:

    git fetch
    git checkout v0.2.5
    
  4. Build latest changes

    make bor-all

  5. Go back to home directory

    cd ~

  6. 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
  7. Init bor with berlin genesis file

    bor --datadir ~/.bor/data init genesis.json

  8. 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

  1. SSH into your node

  2. Edit the file ~/node/bor/start.sh and add the following line in arguments passed to bor:

    --ethstats <node-name>:testnet@bor-mumbai.vitwit.com:3000
    

    After editing, the bor part of start.sh file should look as follows:

    ...
    ...
    
    bor --datadir $DATA_DIR \
    --ethstats <node-name>:testnet@bor-mumbai.vitwit.com:3000 \
    --port 30303 \
    --http --http.addr '0.0.0.0' \
    
    ...
    ...
    
  3. 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).

  4. Now, restart bor service:

    sudo service bor restart
    
  5. Check if your node is reflecting here https://bor-mumbai.vitwit.com/

Thanks!

1 Like