Zebra 6.0.0 supports NU6.3 Ironwood
The first stable release supporting NU6.3 Ironwood sets the mainnet activation height to 3,428,143. All node operators must upgrade before activation.
The Zcash Foundation released Zebra 6.0.0, the first stable release that supports Mainnet activation of NU6.3 Ironwood. The Ironwood activation height is 3,428,143, expected around 13:00 UTC on July 28, 2026, and the Testnet height is 4,134,000. Promoting the work from 6.0.0-rc.0 to a stable version added a mempool validation security fix, networking and read-state fixes, and a new build dependency, libclang. The author urges every node operator to upgrade before activation.
Ironwood is a new shielded pool that reuses Orchard's Action and the Halo2 proof system while having its own note commitment tree, nullifier set, chain value pool and chain history metadata, and it is offered with the v6 transaction format. The z_gettreestate, z_getsubtreesbyindex and verbose getblock RPCs expose the Ironwood note commitment tree and subtree roots from NU6.3 activation, and the Ironwood pool is also included in valuePools in getblockchaininfo and getblock.
Security advisory GHSA-84j3-rw4c-gqmj (medium severity) concerns P2SH mempool validation. Full script validation ran before the cheap policy check that filters out non-standard P2SH scripts with many signature operations, so a peer sending transactions that are cheap to create but expensive to verify could occupy verification capacity and reduce responsiveness. The impact was limited to degraded availability, with no crash, consensus error, wrong block acceptance or loss of funds. Non-standard transparent inputs are now rejected before script verification, and verification runs on a shared Rayon thread pool.
There are also fixes since the release candidate. A mempool that has started is no longer cleared by a transient sync signal, and Zebra no longer disconnects peers that give an empty FindBlocks or FindHeaders response near the chain tip. A start-up hang in the read-state syncer and syncer restarts caused by incorrect error conversion were also fixed. The build now requires libclang because of the rocksdb 0.24 update, and the library minimum Rust version rose from 1.85.1 to 1.88. The state DB migrates in place to format 28.0.0, so no resync is needed, but downgrading is not supported, so a backup is recommended.
This summary is based on the original; check the original for exact details.