Polygon's Purley Upgrade Went Live on Mainnet Before Its Source Code Was Published
Key Takeaways
- •Purley activated on the Amoy testnet at block 52,108,000 on November 12 and on mainnet at block 58,280,000 on November 20, with both activations running private builds before the v0.14.0 source code was tagged on GitHub.
- •The fork tightened one rule on each of three Ethereum-linked data routes: deposits now require confirmed bridge events with signed, authenticated vote extensions, stake updates must carry the validator's next nonce to enforce ordering, and expired checkpoints stay in the buffer until an approved checkpoint replaces them.
- •Every Heimdall node must run v0.14.0-priv or later in a plain binary upgrade with no new configuration keys, state migration, resync or change to Bor, and token holders are asked to take no action.
- •Neither Polygon's forum announcement nor the GitHub release notes explain why the public release followed the live fork or describe Purley as a security fix, though the earlier Heimdall-v2 release v0.4.4 was an ABCI security patch accompanied by a technical write-up.
- •The release defines no block count for event confirmation and announces no change to deposit or withdrawal times, with Ethereum-to-Polygon delivery still documented as occurring within a single sprint of roughly a few minutes.

Polygon's Purley upgrade activated on the Polygon PoS mainnet on November 20 before its source code was published. According to Polygon's announcement on its developer forum, activation took place at Heimdall block 58,280,000, reached at 01:39:38 UTC, and the public v0.14.0 release is described as functionally identical to the private build that mainnet nodes had been required to run.
The fork changed consensus rules covering token deposits, staking updates and checkpoints. Every Heimdall node now has to run version v0.14.0-priv or later.
The Fork Went Live Before the Code Did
Purley reached the Amoy testnet first, activating at block 52,108,000 on November 12, and arrived on mainnet eight days later. Both activations ran on private builds. Node operators installed those binaries, but the source code became public only when v0.14.0 was tagged on GitHub on November 20.
The GitHub release notes name one difference from the private build: a validator-join account lookup now uses the task context, a change outside consensus. The hard fork itself was merged as a single pull request, #699.
Neither document explains why the public release came second, and the release notes do not describe Purley as a security fix. Software teams sometimes hold back code until a change is live so that it cannot be studied and targeted before nodes upgrade. Polygon has not said that was the reason here.
There is precedent for a fuller account arriving later. An earlier Heimdall-v2 release, v0.4.4, went out as an ABCI security patch accompanied by a write-up describing how late, malformed vote extensions could halt the chain. Vote extensions sit at the center of Purley as well.
The opposite reading deserves equal weight. A private rollout followed by a full code release is ordinary practice for consensus changes, and the code is now open to anyone who wants to check what changed.
Three Routes From Ethereum, One Consensus Layer
Polygon PoS runs on two layers. Bor produces blocks, while Heimdall-v2 handles validation, checkpoint submission and coordination with Ethereum. Heimdall-v2 is a rewrite of the original Heimdall, built on forks of Cosmos SDK and CometBFT.
Heimdall cannot take Ethereum data on trust. Polygon's documentation describes a side transaction as a message whose contents the consensus engine cannot verify by itself, so validators vote on whether the data is correct. Those votes travel as vote extensions, and the first transaction in each Heimdall block carries them in encoded form.
Three kinds of Ethereum-linked data pass through that vote: token deposits heading to Polygon, stake changes made in Ethereum staking contracts, and checkpoints heading back to Ethereum. Purley tightens one rule on each route.
Deposits: The Step Between Ethereum and a Balance
The deposit flow runs in three stages. First, on Ethereum, the deposit passes through the bridge's RootChainManager contract, which locks the tokens and triggers a StateSynced event. Second, in Heimdall — the step changed by Purley — validators watch for the event, one submits a state-sync transaction, and the record enters Heimdall state once more than two thirds of validators agree. Third, at the start of each sprint, currently 16 blocks, Bor pulls pending records and the StateReceiver system contract delivers them, minting the tokens on Polygon.
Purley's bridge rule applies at the middle step. Heimdall now confirms bridge events before acting on them, and the vote extensions that carry validators' verdicts are signed and authenticated in every block that includes them. The two checks close different gaps: a signature ties a vote to a specific validator, while confirmation tests whether the Ethereum event behind that vote meets Heimdall's rules before anything is credited.
The release does not define "confirmed." It sets no block count and announces no change to deposit times. Polygon's bridging documentation describes Ethereum-to-Polygon delivery as happening within a single sprint, roughly a few minutes.
For anyone waiting on a deposit, the Ethereum transaction hash proves only the first step. A balance that has not appeared is still in the second or third stage, and the token contract on Polygon is the record that settles it. A wallet or tracker total is a weaker signal.
Staking: Ethereum Changes Recorded in Sequence
Polygon validators stake on Ethereum, then submit Heimdall transactions acknowledging each stake change. Heimdall's stake module saves an update once a majority of validators agree that it matches the Ethereum event.
After Purley, Heimdall accepts a stake update only if it carries that validator's next nonce — a counter that tracks the validator's stake changes and has nothing to do with the nonce a wallet uses. An update can no longer be accepted while an earlier one is missing, so changes are recorded in the order they occurred.
A smaller fix in the same module does not wait for the fork height: stake messages with a nil amount are now rejected during basic validation, with the result code left unchanged.
Checkpoints: The Buffer Behind Withdrawals
Traffic in the other direction relies on checkpoints. Heimdall gathers Bor blocks into Merkle trees and periodically publishes the root to Ethereum. According to Polygon's checkpoint documentation, an approved checkpoint goes into a buffer, the bridge submits it to Ethereum with validator signatures, and an acknowledgment clears it. If that acknowledgment is overdue, a No-ACK signal moves the process on.
Withdrawals depend on this channel. Under the bridge's lock-and-mint model, tokens burned on Polygon are released on Ethereum only after a checkpoint covering the burn has reached Ethereum.
Purley keeps an expired checkpoint in the buffer until an approved checkpoint replaces it, rather than letting the slot clear on expiry. The release does not describe what the earlier behavior risked, and it announces no change to withdrawal times.
What Node Operators and Token Holders Need to Do
Purley is already active on both networks, so every Heimdall node has to run a compatible build. Polygon describes the change as a plain binary upgrade with no new configuration keys, no state migration, no resync and no change to Bor.
The upgrade checklist:
- Mainnet: v0.14.0-priv or later, or the public v0.14.0
- Amoy: v0.14.0-beta-priv or later, or the public v0.14.0
- Debian package: verify against its .checksum file with
sha256sum -cbefore installing - Container:
ghcr.io/0xPolygon/heimdall-v2:v0.14.0 - Confirm:
heimdalld versionprints 0.14.0
Because Heimdall processes the validator votes behind deposits, stake updates and checkpoints, build compatibility matters to operators across all three flows even though Bor itself is unchanged.
The release also tidies a few operational details. Configuration templates now leave external_address empty instead of shipping a node's address, the bridge's worker queue has its own name, and from the Purley height, cancelled governance proposals with no destination set are no longer charged.
Token holders have nothing to do. The release asks no one to move or migrate funds.
The Explanation Still Missing
The release leaves one question unanswered: why a fork touching vote extensions, bridge events, stake ordering and checkpoints shipped as a private build first. The clearest answer would be a technical write-up like the one Polygon published for v0.4.4. Until one appears, the forum post, the GitHub notes and pull request #699 remain the complete official record, and the code is now available for independent review. For readers assessing the rollout, the most concrete items to watch are any later technical explanation and the release's documented behavior around event confirmation, stake ordering and checkpoint replacement; none has been tied to a new deposit or withdrawal timetable.