Stable release v0.13.2: the public source of the Karwar hardfork, functionally identical to v0.13.2-priv. Karwar is already active on both networks, so every node must run v0.13.0-priv or later, or this release. It's a plain binary upgrade: no config changes, state migration or resync.
| Network | Karwar height (Heimdall) | Activated (UTC) |
|---|---|---|
| Amoy | 50,020,000
| 2026-10-23 02:29 |
| Mainnet | 57,006,000
| 2026-11-03 08:54 |
Gated at the Karwar height:
- Vote extensions are bounded in size.
- Checkpoints use canonical signatures (app, bridge, checkpoint).
Not height-gated:
- Block-sync serving reserves the block size before loading a block.
- RPC
Status/catching_upno longer waits on the consensus lock. - Span rotation skips the pending-stall path for pre-Rio bor heads.
- Go 1.26.10,
x/netv0.60.0,amqp091-gov1.14.0.
On the local/default network config (not mainnet or Amoy), the Phuket, Zurich, Ithaca and fee-withdraw gates now activate from height 1, as Kyoto, Lugano and Karwar already do. An existing chain on that config needs a fresh genesis.
It bumps cometbft to v0.3.11-polygon and cosmos-sdk to v0.2.17-polygon. These replace the vendored copies used by the private builds; the code is the same.
What's Changed
- v0.13.2 candidate (Karwar) by @marcello33 in #681
Full Changelog: v0.12.2...v0.13.2