Heimdall v1.2.5 (Mainnet)

Announcements
1

Hi all,

We are releasing a new Heimdall version v1.2.5 which is a hotfix for the Bhilai Hard Fork on Mainnet, which upgrades the bor client to version v2.1.1. Please note that this release is same as v1.2.4, there was an issue with docker image generation for v1.2.4, so we released v1.2.5.

Action Required:

All mainnet operators are strongly recommended to upgrade their heimdall nodes to heimdall v1.2.5 to ensure continued compatibility and stability post-HF.

This release addresses network compatibility issues and is essential for seamless participation in mainnet consensus following the Bhilai upgrade.

Steps for Upgrading Heimdall

Before proceeding, please create a backup of your heimdall config file whose default location is: /var/lib/heimdall/config/config.toml. This might differ if you have setup heimdall at a different location.

  1. Stop heimdalld service

    sudo service heimdalld stop

  2. Install heimdall with a version tag, network name (amoy or mainnet), 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 -- v1.2.5 <network> <node_type>

  3. Check heimdall version

    /usr/bin/heimdalld version

# It should print
# 1.2.5

  4. Restart heimdall service

    sudo service heimdalld start

  5. Restart the telemetry services

    sudo service telemetry restart

Docker Images

You can find the latest docker images here:

Heimdall: https://hub.docker.com/r/0xpolygon/heimdall/tags

Thanks,

Polygon Team

2 Likes
2

Upgraded to Heimdall v1.2.5 without issues—appreciate the clear steps. Reminder to all mainnet operators: this is a critical hotfix for Bhilai HF, so don’t delay the upgrade. Also, double-check your config backup before proceeding. Smooth upgrade ensures you stay in sync with the network.

1 Like