Heimdall v0.3.4 Mainnet and Mumbai Release

Hello all,

We are releasing a new incremental stable release for Heimdall - v0.3.4 for Mainnet and Mumbai.

Instructions to Upgrade

Before proceeding, please create a backup of your heimdall config.toml.

  1. Stop heimdalld service

    sudo service heimdalld stop
  2. Install Heimdall with a version tag, network name (mainnet or mumbai), and node type (sentry or validator).

    # Replace the network and node type
    curl -L https://raw.githubusercontent.com/maticnetwork/install/main/heimdall.sh | bash -s -- v0.3.4 <network_name> <node_type>
  3. Check heimdall version

    /usr/bin/heimdalld version
    # It should print 
    # 0.3.4
  4. Restart heimdall service

    sudo service heimdalld start

Change log

Compared to last stable version v0.3.3 , the following features and improvements have been implemented. (Checkout the 0.3.4 tag on GitHub for more information)

Docker Images

You can find the latest docker images here:

Heimdall: Docker


Polygon Team


Can I point you at Bor not staying synced, falling behind. · Issue #887 · maticnetwork/bor · GitHub

Heimdalld 0.3.4 leads to an unstable Bor in our environments with Bor 0.3.9, on mainnet. No issues on Mumbai.

Unsure whether it’s Bor or Heimdall that’s to blame. It is reproducible, and downgrading heimdalld to 0.3.3 resolves the issue and Bor remains stable.