0xPolygon/heimdall-v2 - v0.13.2 New

Published: Nov 3, 2026
TESTNET Deadline: Oct 23, 2026
MAINNET Deadline: Nov 3, 2026

Release Summary

Heimdall-v2 stable release v0.13.2 is now available. This is the public source release for the Karwar hardfork and is functionally identical to the previous private release `v0.13.2-priv`.

This is a mandatory upgrade for all node operators. The Karwar hardfork is already active on both Mainnet (at block 57,006,000) and Amoy (at block 50,020,000). All nodes must run this version or `v0.13.0-priv` or later to remain in sync.

The upgrade is a simple binary swap, with no configuration changes, state migration, or resync required.


Karwar Hardfork Changes

The following changes became active after the Karwar fork height:

Bounded Vote Extensions: To enhance network stability, the size of vote extensions is now limited.
Canonical Signatures for Checkpoints: Checkpoints for the application, bridge, and checkpoint modules now use canonical signatures for improved consistency.


Other Improvements

This release also includes several improvements that are effective immediately:

Improved Block-Sync: The block-sync service now reserves memory for the block size before loading the full block, enhancing performance and stability.
More Responsive RPC: The `Status` RPC endpoint (`catching_up` field) no longer waits for the consensus lock, making it more responsive.
Dependency Updates: The release is built with Go 1.26.10 and now uses public forks of CometBFT (`v0.3.11-polygon`) and Cosmos-SDK (`v0.2.17-polygon`).

Release Notes

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_up` no longer waits on the consensus lock.
- Span rotation skips the pending-stall path for pre-Rio bor heads.
- Go 1.26.10, `x/net` v0.60.0, `amqp091-go` v1.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`](https://github.com/0xPolygon/cometbft/releases/tag/v0.3.11-polygon) and cosmos-sdk to [`v0.2.17-polygon`](https://github.com/0xPolygon/cosmos-sdk/releases/tag/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 https://github.com/0xPolygon/heimdall-v2/pull/681


**Full Changelog**: https://github.com/0xPolygon/heimdall-v2/compare/v0.12.2...v0.13.2

Links

Back to 0xPolygon/heimdall-v2 releases