News Blockchain and technology

Polygon publishes Purley code: what changes for Heimdall operators?

Heimdall v0.14.0 was published on 20 November after Purley activated on mainnet. Nodes need a compatible version; Polygon Labs says this update requires neither a Bor change nor a resynchronisation.

Checked on 21 November 2026.

Pale bridge between navy block groups with an orange gate and inspection cube
Illustration: infrastructure and a checkpoint, not a technical diagram of Polygon.

Activation has already happened

The public release of Heimdall v0.14.0 gives Polygon operators the Purley upgrade code, with the same functionality as the previously distributed v0.14.0-priv version. Polygon Labs' announcement on 20 November 2026 explains that both relevant networks have already passed the activation height. This is an availability and compatibility announcement after activation, rather than a countdown to a future fork.

According to the developer announcement on Polygon's forum (Opens in a new tab), mainnet activated at block 58,280,000 on 20 November at 01:39:38 UTC. The Amoy testnet activated at block 52,108,000 on 12 November at 15:41 UTC. That earlier date concerns the test network, not the new public code release.

The team says every node needs a compatible version: v0.14.0-priv or later on mainnet, v0.14.0-beta-priv or later on Amoy, or the new public release. An operator who already installed the compatible private release is in a different position from one still running pre-upgrade software.

Targeted checks for votes, bridges and staking

The release notes describe several changes activated at the Purley height. A validator's vote extension is included signed and authenticated in every block carrying it, and bridge events are confirmed before being acted on. These rules govern information being accepted and used; they do not promise to eliminate every bridge risk.

Stake updates are admitted only at the validator's next sequence number, or nonce. An expired checkpoint buffer is also retained until an approved checkpoint replaces it. In this context, the sequence number helps define the order of updates, while a checkpoint forms part of network coordination. There is no need to present these changes as a performance leap when the announcement supplies no such measurement.

A further fix concerns cancelled governance proposals without a destination: they are no longer charged. Other release changes address the bridge worker queue, validation of staking messages and packaging configuration. The picture is precise maintenance across several workflows, rather than a new trading product for token holders.

What operators need to do, and what they do not

Polygon Labs describes a straightforward binary replacement, without configuration changes, state migration or resynchronisation. It explicitly says that Purley requires no Bor change. Those instructions apply to this release; they do not establish the requirements for a future upgrade.

For a system-package installation, the announcement instructs operators to obtain the appropriate package and matching checksum file from the official release, verify them locally, stop the service, install, check the version and restart. Record the network being managed and the previously running version as well. That check helps avoid confusing Amoy with mainnet, or a filename with the software actually running.

Ordinary users do not need to replace node software merely because they hold an asset on the network. The update concerns infrastructure maintained by operators. Our guide to blocks and validation rules explains the general role of checking network information without assuming every network works like Bitcoin. Publishing the code permits inspection of the changes; using them safely still depends on sound operations.

Correction and clarification

Found an error? Contact the editors

Share article Back to top