Zcash developers report that the Ironwood network upgrade is approaching testnet activation, marking a critical step toward restoring confidence after a critical counterfeiting vulnerability triggered a severe price collapse last month. According to forum posts published Thursday, work is simultaneously advancing on a formal proof of soundness for the new protocol, though migrating exchanges, wallets, and mining pools to the updated software stack remains the most significant deployment hurdle.
Announced in June, Ironwood introduces a novel shielded pool and accounting system designed to allow public verification of Zcash’s circulating supply without compromising transaction privacy. The upgrade directly addresses the uncertainty exposed by the Orchard vulnerability disclosed in May, which left developers unable to cryptographically prove whether counterfeit ZEC had ever been minted.
The vulnerability disclosure sparked a panic that erased more than half of ZEC’s value in two days, driving the price from above $600 to a low near $300. The token has since recovered approximately half of those losses, recently trading around $457, according to CoinGecko data.
“At Shielded Labs our focus has been security, and in particular our new project, which we are calling Zero, of supporting enterprise users (e.g. mining pools, exchanges, and wallets),” Zcash co-founder Zooko Wilcox wrote. “Our current focus within the Zero project is to help them prepare to safely make the transition to Ironwood.”
The crisis originated when security researcher Taylor Hornby, using Anthropic’s Claude Opus 4.8, uncovered a four-year-old flaw in Zcash’s Orchard shielded pool that could have permitted unlimited undetected counterfeiting. Although developers patched the bug on June 1, Zcash’s privacy architecture prevented any determination of whether the flaw had been exploited, necessitating the Ironwood proposal to eliminate that ambiguity permanently.
“Ironwood’s prompt and safe activation on Zcash mainnet is extremely important to our users, in addition to the formal verification work we’re doing in parallel to provide reassurance that there aren’t any supply integrity concerns,” Zcash developer Sean Bowe posted on X Thursday. He noted that sufficient hash rate is signaling technical readiness for the mainnet upgrade, but acknowledged concern that some wallets may not be prepared in time. Bowe argued this does not justify delaying Ironwood, given adequate alternatives and sufficient testnet time for those who need it.
Jason McGee of Shielded Labs outlined two parallel development tracks: the Ironwood (NU6.3) network upgrade itself, and the broader migration of the Zcash ecosystem from the legacy Zcashd client to the new Z3 stack—which comprises the Zebra full node, the Zaino indexing service, and the Zallet wallet. McGee stated development is on schedule, with testnet activation of the new consensus rules expected shortly.
“The current goal is to complete both efforts by late July,” McGee wrote. “With regard to Ironwood, the teams at Project Tachyon, Valar Group, ZODL, the Zcash Foundation, and Shielded Labs have been working hard and have made significant progress over the past several weeks.”
Work continues on formal verification of the new circuit, with the goal of completing a proof of soundness before Ironwood activates. However, McGee identified the larger challenge as preparing infrastructure providers for the software transition. Key Z3 components, including Zallet and Zaino, remain under development, leaving exchanges, mining pools, and wallet providers with a compressed window to deploy and test before activation.
“The consistent feedback we’ve received is that completing both the Ironwood upgrade and the migration to Z3 on the current timeline will be challenging,” McGee wrote, noting that a recent questionnaire showed some respondents ready while others requested additional time.
Several risk-mitigation options are under consideration, including delaying Ironwood, conducting independent third-party security audits prior to deployment, or temporarily supporting Ironwood through the legacy Zcashd client while partners complete their migration.
“Ultimately, we all share the same goal to activate Ironwood as quickly as possible while making sure our partners can safely migrate away from Zcashd,” McGee concluded. “We think the focus over the coming weeks should be on making that transition as smooth and secure as possible.”
