Zcash founder Zooko Wilcox is framing the proposed Ironwood upgrade as a direct answer to the supply-verification problem created by the recently disclosed Orchard counterfeiting vulnerability. In posts on X and the Zcash community forum, Wilcox said Ironwood is intended to let full nodes verify the soundness of ZEC’s circulating supply immediately upon activation, rather than waiting for funds to migrate out of the existing shielded pool.
Ironwood promises day-one ZEC supply checks
Wilcox wrote on X that Ironwood would give Zcash users local, trustless confirmation of the network’s supply from the first block of activation. “When Zcash Ironwood activates, you will immediately, on Day 1 of Ironwood, gain trustless verification from your own full node that the actual supply of Zcash is correct,” he wrote, referring to “16M ZEC now, 21M ZEC eventually.” He added that this claim holds “regardless of whether or not there are any counterfeit coins in the Orchard pool.”
In a longer post on the Zcash community forum, Wilcox said the central point is that users should not need to infer supply integrity from later behavior by holders or potential attackers. “As soon as Ironwood activates, you get verification of the current actual supply of ZEC from your full node. You do not have to wait and see how many ZEC migrate from Orchard to Ironwood and you do not have to do game-theoretic reasoning about how an attacker might behave or how other legitimate users might behave in order to have this verification. This is important to me, because my goal is to get the most outsiders to start trusting Zcash over the next ten years.”
The mechanism described by Wilcox would constrain the legacy Orchard pool as Ironwood comes online, with the new design using turnstile-style accounting to restore verifiable supply integrity. On X, he wrote: “Because Ironwood will, on Day 1, in the first block that activates Ironwood, snuff out any excess ZEC in the Orchard pool, in excess of the 4.5M ZEC that is legitimately part of the supply of ZEC in the Orchard pool. It will snuff out any excess ZEC immediately, trustlessly, and globally. It will snuff out any excess ZEC regardless of whether there actually is any excess ZEC.”
Zcash targets trustless verification after Orchard bug
The Ironwood discussion follows the disclosure of a critical vulnerability in the Orchard pool, which went live in May 2022. Shielded Labs hired security researcher Taylor Hornby in April 2026 for ongoing Zcash protocol security research, including AI-assisted review, and Hornby discovered the Orchard counterfeiting bug on May 29 after using Anthropic’s Opus 4.8 as part of a targeted circuit review. The big could have allowed unlimited, counterfeit ZEC inside Orchard; an emergency fix was deployed on June 1, and Zcash Open Development Lab’s coordinated response with the ecosystem was completed on June 2.
Wilcox, Jason McGee and Hornby publicly explained the issue on the Zcash forum on June 4 and June 5, saying past exploitation cannot be cryptographically ruled out while also stating that they believe exploitation was unlikely. Wilcox has emphasized that Ironwood’s objective is not to prove there was never an exploit, but to make the current supply verifiable. “This appears to be super confusing to almost everyone, because they are confusing two different things: No counterfeit coins were created. The current supply is sound, i.e. 16M ZEC now, 21M ZEC eventually. These are different things. I’m prioritizing the second one.”
Public discussion of Ironwood began on June 6, with developers targeting activation around block height 3,417,100 in late July 2026, subject to final testing, audits and ecosystem coordination. ZEC rebounded about 45% from the prior week’s low near $300 after the Ironwood proposal, while remaining roughly 22% lower on the week. Wilcox summarized the proposal’s intended outcome this way: “The goal of Ironwood is that, regardless of whether we are in universe 1 or universe 2, in both cases everyone gets trustless verification that the supply is sound on Day 1 of Ironwood.”
AI Transparency Note: This article was prepared with the assistance of an AI system based on the sources listed and was reviewed, edited, and approved by a human editor before publication. All quotes, data points, and factual claims are intended to be grounded in the cited source material; however, errors cannot be ruled out entirely.