Zcash targets July 28 launch for Ironwood network upgrade
Zcash targets a July 28 mainnet launch for its Ironwood network upgrade, which will replace the Orchard private pool after an "infinity" bug was discovered in May. Core developer Sean Bowe confirmed activation at block height 3,428,143, roughly 8 a.m. EST—one week later than an earlier July 21 target. The privacy-focused blockchain is racing to close a once-compromised shielded pool and restore trustless supply verification across its ecosystem.
Key Takeaways
- Ironwood is scheduled to activate on July 28 at block height 3,428,143, about 8 a.m. EST.
- The upgrade closes the Orchard pool, blocks new activity there, and routes funds through an accounting checkpoint into a new private pool.
- Migration may reveal whether counterfeit ZEC was ever minted via the Orchard vulnerability.
- Major organizations have committed to NU6.3 activation, though some developers had warned late-July timing was tight for exchanges and wallets.
Why is Zcash replacing the Orchard shielded pool?
Zcash's Ironwood upgrade is the protocol's answer to an "infinity" bug found in May on Orchard, the network's main private transaction pool. Announced in June, the change shuts down the current Orchard pool, prevents new deposits and transfers within it, and stands up a replacement shielded pool.
Funds leaving Orchard must pass through an on-chain accounting checkpoint before they can enter Ironwood. That design is meant to patch the flaw that once left the pool exposed to theoretically unlimited counterfeit minting, while keeping Zcash's privacy architecture intact for users who rely on shielded transactions.
Could Ironwood reveal whether the Orchard bug was exploited?
One of the upgrade's most closely watched effects is forensic. In June, Shielded Labs said Ironwood may provide evidence about whether the Orchard vulnerability was ever exploited in the wild.
As users migrate holdings, any hypothetical counterfeiter faces a difficult choice: move counterfeit funds and risk exposing them, or leave them behind and risk being unable to move them later. Node operators could then independently verify that no excess ZEC left the legacy pool—clues that the bug may not have been used to create fake tokens.
Why was the Ironwood launch pushed back one week?
Not everyone in the Zcash ecosystem wanted a late-July deadline. Shielded Labs had floated delaying Ironwood, warning that exchanges, mining pools, and wallet providers might not have enough time to prepare systems for mainnet activation.
On Thursday, Bowe said the activation height had been "set and tagged," with major organizations committed to NU6.3 at height 3,428,143. That confirmation locks in a July 28 go-live, one week after the earlier July 21 target, giving infrastructure partners a slightly longer runway.
What should Zcash users watch before July 28?
For holders and traders, the practical question is coordination. Wallet, exchange, and mining-pool operators must update software and migration flows before Ironwood activates. Anyone using Orchard shielded addresses should follow guidance from their provider as the cutoff approaches.
The Ironwood rollout sits at the intersection of privacy tech and supply integrity—one of the sharper tests for Zcash in 2026. For broader coverage of protocol upgrades and crypto security, see our Fintech & Crypto Alerts hub. Full technical background is in CoinTelegraph's report on the scheduled activation.