Heimdall Mumbai Update v0.2.3-beta1

Hi All,

We have added a method in the Checkpoint module that looks up the rootchain (ethereum for mainnnet and goerli for mumbai) and updates the existing checkpoint. This can be used (by firing a CLI command) in cases where the checkpoint details persisted in the state are incorrect and it follows the usual tendermint consensus before updating the state. One such incident had occurred in the mumbai network due to which we had to roll it out and update the checkpoint details today. The nodes that did not have the latest code got an error in consensus and hence the additional steps to restore the latest snapshot along with upgrading heimdall below.

Instructions to Upgrade Mumbai Heimdall:

  1. Download the latest snapshot
wget -c https://matic-blockchain-snapshots.s3-accelerate.amazonaws.com/matic-mumbai/heimdall-snapshot-2021-10-06.tar.gz
  1. Stop Heimdall services:
sudo service heimdalld stop
sudo service heimdalld-rest-server stop
  1. Remove heimdall data directory and untar the file
tar -xzvf heimdall-snapshot-2021-10-06.tar.gz -C <HEIMDALL_DATA_DIRECTORY>

For example (with default values):

rm -rf ~/.heimdalld/data
mkdir ~/.heimdalld/data
tar -xzvf heimdall-snapshot-2021-10-06.tar.gz -C ~/.heimdalld/data

Note that if your Heimdall data directory is different then please mention that directory name correctly.

  1. Navigate to heimdall directory
cd ~/heimdall
  1. Checkout to the new release tag:
git fetch
git checkout v0.2.3-beta1
  1. Build:
make install network=mumbai
  1. Restart Services:
sudo service heimdalld restart
sudo service heimdalld-rest-server restart

Please let us know if you have any questions.

Thank you.


Release on Github: https://github.com/maticnetwork/heimdall/releases/tag/v0.2.3-beta1

Docker Image for the latest release: https://hub.docker.com/layers/maticnetwork/heimdall/v0.2.3-beta1/images/sha256-3c2209607fe175f63c112886bb16198f9675dbfc2d353b426947fa940ffbbd6a?context=explore

Any updates on when block production might resume in the Mumbai testnet?

Block production had not stopped, there was a consensus error in heimdall on nodes that weren’t upgraded due to which bor had stopped syncing on these nodes.

Thank you for the explanation @ssandeep, everything looks back to normal now!