Zcash Ironwood Upgrade Faces Possible Delay Over Z3 Migration

Zcash’s Ironwood upgrade may be delayed as exchanges, wallet providers and mining pools work through the migration from legacy zcashd infrastructure to the new Z3 software stack.

The possible Ironwood delay is tied to ecosystem readiness rather than a newly disclosed exploit. Shielded Labs and other Zcash contributors have been discussing whether activation should be pushed back to allow more time for testing, audits and infrastructure migration before the network upgrade goes live.

The Z3 stack includes Zebra as the node implementation, Zaino as the data service and Zallet as the wallet component. Exchanges, mining pools, custodians, wallets and infrastructure providers need enough time to update systems before Ironwood activation because Zcashd support is being phased out.

Ironwood had been targeted for late July after zcashd end-of-support at block height 3,417,100. That timeline was already conditional on development, testing, reviews and coordination across the Zcash ecosystem.

Upgrade Replaces Old Orchard Activity

Ironwood was proposed after Zcash developers remediated a critical Orchard shielded-pool vulnerability that could have allowed counterfeit ZEC creation inside the privacy pool.

Shielded Labs’ Ironwood proposal would reject transactions that create new outputs in the old Orchard pool. Funds remaining in Orchard would only be able to move out through Zcash’s turnstile accounting system before entering the new shielded pool.

That design is meant to let node operators verify that no more than the correct amount of ZEC can circulate after activation. The old Orchard pool would stop internal circulation, while the new pool becomes the active shielded environment.

Zcash contributors have said there is no evidence that the Orchard flaw was exploited. The verification problem remains because Orchard’s privacy design prevents a full public reconstruction of historical shielded activity inside the affected pool.

Zcash Recovery Depends On Clean Coordination

The delay discussion follows earlier Zcash coverage around the late-July Ironwood target and the later assessment that Orchard exploitation was unlikely.

The upgrade now depends on two separate readiness tracks. The first is Ironwood itself, including consensus-rule implementation, audits and review. The second is ecosystem migration, where exchanges, wallets, mining pools and infrastructure operators must complete Z3-related updates safely.

A delay would keep the old Orchard pool issue unresolved for longer, but a rushed activation could create exchange, wallet or mining-pool disruption if key infrastructure is not ready. The current discussion is focused on timing, not a confirmed second vulnerability.