Stable release v0.14.0: the public source of the Purley hardfork, functionally identical to v0.14.0-priv. Purley is already active on both networks, so every node must run v0.14.0-beta-priv (Amoy) or v0.14.0-priv (mainnet) or later, or this release. It's a plain binary upgrade: no config changes, state migration or resync.
| Network | Purley height (Heimdall) | Activated (UTC) |
|---|---|---|
| Amoy | 52,108,000
| 2026-11-12 15:41 |
| Mainnet | 58,280,000
| 2026-11-20 01:39 |
Gated at the Purley height:
- A validator's vote extension is carried signed and authenticated in every block that includes it, and bridge events are confirmed before they are acted on (see
docs/purley-vote-flow.md). - Stake updates are admitted only at the validator's next nonce.
- An expired checkpoint buffer is kept until an approved checkpoint replaces it.
- Cancelled governance proposals with no destination set are no longer charged.
Not height-gated:
- The bridge's machinery worker queue is bound with its own name.
- Stake messages with a nil amount are rejected in
ValidateBasicwithout changing the result code. - Packaging config templates leave
external_addressempty instead of shipping a node's address.
It pins cometbft to v0.3.14-polygon, which is v0.3.11-polygon (the last cometbft release used in production) plus the Purley consensus change. It replaces the vendored copy used by the private builds; the Go code is the same. cosmos-sdk stays at v0.2.17-polygon. cometbft v0.3.12-polygon and v0.3.13-polygon are not part of this release.
One non-consensus bridge line differs from v0.14.0-priv: the validator join account lookup now uses the task context.
What's Changed
- all: Purley hardfork by @kamuikatsurgi in #699
Full Changelog: v0.13.2...v0.14.0