Zcash core developer Sean Bowe shared the latest progress on the Ironwood upgrade via X on June 12. Over the past 48 hours, organizations involved in protocol development held two meetings and reached consensus on the specification and implementation details of Ironwood. Formal verification and security audits by three firms are now proceeding simultaneously.
Three Key Changes Finalized
The meetings finalized three priority changes: disabling the Orchard pool binding in Coinbase to reduce computational burden on early validators; hardware wallet migration authentication data, using the anchor point as the verification data source for hardware wallets migrating to the new privacy pool; and ZIP and spec processing order, establishing the priority between Zcash Improvement Proposals and specification files to avoid development conflicts. These changes correspond to the three technical pillars of Ironwood: specification definition, wallet compatibility, and development consistency. In May, Zcash detected an infinite minting bug in the Orchard privacy pool, causing ZEC to drop over 48% in a single day. Ironwood is the core proposal to fix that vulnerability.
Formal Verification and Audits Underway
The Ironwood circuit and ZIP 2005 integration draft are currently under peer review. Valar Group has completed testnet deployment and partial wallet-side changes. Formal verification work is running in parallel, with developers planning a meeting on June 13 to finalize the verification strategy. Formal verification uses rigorous mathematical proofs from computer science to demonstrate that program logic has no hidden vulnerabilities, covering all possible input combinations unlike traditional testing. Additionally, at least three major blockchain auditing firms have started security audits of the Orchard privacy pool, and multiple AI auditing tools are also running concurrently to doubly ensure the reliability of the Ironwood upgrade.
From Detection to Verification: Zcash Upgrade Timeline
The Ironwood upgrade path dates back to mid-May: an AI model detected the infinite minting bug in Orchard → Zcash publicly proposed Ironwood → the development team set a July launch timeline → organizations reached consensus on specs → now entering the final stage with formal verification and multiple auditors running in parallel. If verification and audits complete on schedule, the Ironwood upgrade is expected to go live in July, migrating Zcash's privacy pool from Orchard to a new specification and making ZEC's circulating supply verifiable.