PURLEY IS ACTIVE ON POLYGON MAINNET

Polygon Labs has released Heimdall v0.14.0 for Polygon mainnet and the Amoy testnet after both networks passed their Purley activation heights. The company said mainnet activated at Heimdall block 58,280,000 at 01:39:38 UTC on November 20. Amoy activated earlier, at block 52,108,000 on November 12. Heimdall is the network layer that coordinates validators and checkpoints for Polygon's proof-of-stake chain. TokenPost independently reported the public release and the same set of validator, bridge and staking changes. The announcement describes Purley as activated, not merely scheduled, so the immediate issue for node operators is software compatibility rather than a future cutover.

THE HARD-FORK SOURCE IS NOW PUBLIC

Version 0.14.0 is the public source release of Purley and is functionally identical to the private v0.14.0-priv build used for mainnet activation, according to Polygon. The project's signed GitHub release says every node must run that private build or a later compatible version, including the new public release. Polygon characterizes the installation as a plain binary upgrade: no configuration changes, state migration or resynchronization are required. It also says Purley requires no change to Bor, Polygon's block-production client. Publishing the code gives validators and outside developers a common release to inspect and deploy after the coordinated activation.

Related reporting: Hashi Launches Bitcoin-to-Sui Bridge for hBTC DeFi

VALIDATOR VOTES AND BRIDGE EVENTS GET NEW CHECKS

The central consensus change concerns vote extensions, which let validators attach additional data to their votes. Under Purley, a validator's vote extension is carried as signed and authenticated data in every block that includes it. The same flow requires bridge events to be confirmed before the network acts on them. Those controls are designed to make the origin and approval state of the extra data explicit at the point of consensus. Polygon has not published a claim that the release increases transaction throughput or lowers user fees, and the release should not be read as evidence of either. The documented scope is validator coordination and the handling of bridge-related information.

STAKING AND CHECKPOINT HANDLING ALSO CHANGE

Purley admits a stake update only at the validator's next nonce, tightening the order in which staking messages can take effect. It also keeps an expired checkpoint buffer until an approved replacement checkpoint arrives, instead of dropping that buffer without a successor. Cancelled governance proposals with no destination set are no longer charged. Outside the height-gated consensus changes, Heimdall now rejects staking messages with a nil amount during basic validation, separates the bridge machinery worker queue under its own name, and leaves the external-address field empty in packaged configuration templates. These changes address several operational edge cases without adding configuration keys.

VALIDATOR ADOPTION IS THE NEXT PRACTICAL TEST

Because the activation height has already passed, the practical measure of the release will be whether validators converge on compatible public software without disrupting checkpoints or bridge processing. Polygon's release provides Debian packages, container images and checksum instructions, but it does not quantify current validator adoption or publish performance results from mainnet after activation. Nor does it establish that every exchange or infrastructure provider has completed its own maintenance. The strongest confirmation so far is the activated network height and the availability of signed public code. Further evidence will come from node-version distribution, checkpoint continuity and any post-activation incident reports. For users, the upgrade is infrastructure maintenance rather than a new token feature or an investment signal.

Sources

AI-generated editorial image; not a photograph of the reported event. Prepared with AI assistance and source verification.