Polygon has published Heimdall v0.14.0, the public release of its Purley upgrade software, after the changes activated on mainnet early on November 20. According to Polygon Labs' announcement, the public build is functionally equivalent to the private mainnet build already supplied to operators. Making the source public and activating new network rules are separate milestones.
The project records mainnet activation at Heimdall block 58,280,000, at 01:39:38 UTC on November 20. Amoy, the test network, reached its activation point on November 12. The two networks did not activate simultaneously, and today's public release should not be described as a future activation deadline.
What becomes publicly inspectable
Heimdall is part of Polygon PoS's validator infrastructure. The release concerns how participating nodes handle consensus-related information and associated bridge and staking processes. It is distinct from a new token launch or a change to the historical MATIC-to-POL conversion described in our Polygon profile.
Polygon's release notes describe authenticated validator vote extensions and confirmation of bridge events before action. They also specify that stake updates must follow the validator's next nonce, a sequence number that helps order successive updates. These are processing rules, not a reported measurement of faster transfers or higher staking returns.
Publishing source code gives developers something concrete to inspect and compare. It does not, by itself, establish that an independent audit has finished or that every deployed node is running the intended software. Those conclusions require their own evidence.
The operator question is which build is running
The official announcement says the applicable private build or a later compatible release is required now that activation heights have passed. It describes the public release as a binary upgrade without configuration changes, state migration or resynchronization. Polygon also says Purley does not require a Bor change.
For an operator already on the applicable private build, the immediate task is to compare that installation with the public release instructions. For an operator on older software, the announcement cannot be treated as an optional future scheduling note. First identify the network, the running version and the official instructions that apply to it.
A binary-only upgrade still involves operational work. Confirm the package's source, architecture and verification material before replacing software. Record the version before and after the change, and examine the service's health after restarting. These are practical checks, not a claim that this release has been tested here.
The GitHub notes identify one non-consensus bridge-line difference from the private build, involving the context used for a validator join account lookup. Functional equivalence therefore should not be paraphrased as a claim that every line or packaged dependency is byte-for-byte identical.
What this means for ordinary holders
A node-maintenance announcement does not automatically require a wallet holder to install validator software. It also does not establish an exchange's deposit status or guarantee that a particular bridge route is available. Those questions depend on the service and network actually being used.
For readers considering staking participation, distinguish the protocol's handling of stake updates from the terms of a delegation or custody service. A sequencing rule does not set a guaranteed reward, remove withdrawal conditions or certify an operator's performance.
The useful advance is a public implementation associated with an already activated upgrade. It makes the applicable software and its stated behavior easier to examine, while leaving deployment verification, service availability and financial outcomes as separate questions.