Skip to content
Crypto.world

The Ledger

IoTeX Activates Zanzibar, Moving Voter Rewards On Chain

IoTeX activated the Zanzibar hardfork at mainnet block 53,533,081 on October 19, 2026. The upgrade brings IIP-59 on-chain voter reward distribution, with automatic migration limited to eligible Hermes delegates.

IoTeX Activates Zanzibar, Moving Voter Rewards On Chain

Block 53,533,081 puts IIP-59 live

IoTeX activated its Zanzibar hardfork at mainnet block 53,533,081 on October 19, shifting eligible voter staking rewards from Hermes, an off-chain distribution service, into the network protocol. IoTeXScan records the mainnet v2.5.0 activation at 02:28:37 UTC. The release schedule had estimated the fork for about 02:00 UTC, so the explorer’s timestamp confirms when the upgrade actually appeared on the chain.

Source github.com

Zanzibar activates IoTeX Improvement Proposal 59, which puts reward calculation and payment into protocol rules rather than leaving distribution to an external service. “At activation, delegates whose inherited reward address is a configured Hermes vault migrate to on-chain reward distribution,” the IIP-59 authors write. The proposal lists Raullen Chai and Chen Chen as its authors.

Hermes migration is not universal

The automatic migration applies only to candidates whose reward address is one of the configured Hermes vaults and whose DelegateProfile contains both reward-portion fields. IoTeX’s release note counted 88 candidates meeting those conditions in the candidate set at block 52,004,121. The migration runs once at activation, so a delegate missing either field does not get another automatic pass.

The same snapshot included nine Hermes-vault candidates with incomplete reward portions; those remain on the Hermes route. Another 26 candidates that did not use a vault reward address were unaffected by the migration and could opt in separately. Under IIP-59, that opt-in is owner-only and one-way; the release note directs eligible operators to use ioctl stake2 voterrewardoptin.

Era settlement replaces off-chain distribution

Under the new rules, delegate commission is paid to the owner while the voter portion accumulates in a pending pool. At a reward-era boundary, the protocol freezes the relevant reward and staking data, then settles voter payments in bounded chunks over later blocks. IIP-59 defines a reward era as 24 epochs, and says each voter’s payment can go directly to an account or, where configured and eligible, into a native staking bucket.

The design changes who calculates and sends the rewards, not the reward share a delegate has set for voters. It also leaves legacy delegates on the existing handling rather than forcing every candidate into the new system. The IIP-59 governance page records the proposal as passed, with 41,062,730.34 votes in favor from 38 voters and no votes against or abstaining.

Node operators needed the v2.5 release

IoTeX’s release page identifies v2.5.1 as the recommended maintenance release and says it includes Zanzibar from v2.5.0. Operators still running v2.4.x were instructed to upgrade; the project warned that an older node would fork away from the network at activation. Mainnet operators did not need a replacement genesis file or configuration change, and the release instructions say a resync was not required.

Zanzibar also activates BLS proof-of-possession checks for candidate registration and updates, alongside fixes to transfer logs, state reads and blacklist handling. For voters, the practical distinction is now delegate-specific: rewards move on chain only when that delegate migrated automatically or its owner opted in. The hardfork’s activation block marks the point those protocol rules took effect.

Sources

  1. Original source · Release notes GitHub github.com

Other pages read

  1. IoTeX github.com
  2. IoTeX Improvement Proposals github.com
  3. IoTeXScan iotexscan.io
  4. IoTeX Hub hub.iotex.io

Related stories

Explore

More articles