Jump to content
Today Crypto

Crypto stories, filed each day

Polygon Publishes Heimdall v0.14.0 After Purley Goes Live

Polygon has released Heimdall v0.14.0 after Purley activated on mainnet and Amoy, publishing the network changes and giving node operators a binary upgrade path.

The Today Crypto Editors

Polygon Publishes Heimdall v0.14.0 After Purley Goes Live

Polygon has published Heimdall v0.14.0 for its mainnet and Amoy testnet after both networks activated the Purley hard fork. The release makes the source code public and is functionally identical to the private build used for activation, according to Polygon Labs’ release announcement.

For node operators, Purley is already active, so running an older version is no longer the stated option for either network.

Amoy activated first; mainnet followed

Amoy crossed its Purley activation height at Heimdall block 52,108,000 on Nov. 12 at 15:41 UTC. Mainnet activated at block 58,280,000 on Nov. 20 at 01:39:38 UTC. Polygon says both networks had passed their activation heights when it announced the public release later that morning.

The version details and changes are also listed in the Heimdall v0.14.0 release on GitHub. The update changes how Heimdall handles validator vote extensions, bridge events, staking messages and checkpoints. Vote extensions are carried as signed, authenticated data in blocks that include them, while bridge events must be confirmed before the network acts on them.

Purley also limits stake updates to a validator’s next nonce, the sequence number used to order that validator’s updates. An expired checkpoint buffer stays in place until an approved checkpoint replaces it. Cancelled governance proposals with no destination set are no longer charged.

Operators can upgrade without a resync

Polygon describes v0.14.0 as a plain binary upgrade: no configuration changes, state migration or resync are required, and no configuration keys are added or changed. The announcement says Amoy nodes must run v0.14.0-beta-priv or later, while mainnet nodes must run v0.14.0-priv or later; this public release also qualifies. No Bor change is required for Purley.

That gives operators a direct upgrade path after activation without changing node configuration or rebuilding state. The release notes provide Debian packages and a container image, and instruct operators installing the Debian package to verify it against its matching checksum file.

Several changes in the release are not gated by Purley’s activation height. Heimdall rejects stake messages with a nil amount during basic validation, binds the bridge machinery worker queue to its own name, and leaves the external_address field empty in packaging configuration templates. The release notes also identify the CometBFT version pinned for this build as v0.3.14-polygon.

The source code is now public, but the network changes described as Purley are already in force on both listed networks. For operators, the immediate task is to run a supported Heimdall version; the published instructions do not call for a Bor upgrade or a resync.

Sources