Zcash is moving toward a mid-to-late July activation target for its Ironwood upgrade, a network change intended to restore stronger confidence around the Orchard shielded pool after a critical counterfeiting vulnerability was remediated. The timeline was discussed by Josh Swihart, founder of ZODL, in an interview focused on Ironwood’s roadmap, software coordination, and the migration away from the legacy Zcashd node.
Zcash’s Ironwood Upgrade Targets July Activation
Swihart said Ironwood work is advancing faster than expected, with testing already underway and formal verification moving ahead. “Yeah, the test that’s already up, formal verification is progressing well. I think everything’s progressing faster maybe than we anticipated,” he said. The target, he added, is “mid to late July for Ironwood activation,” aligning with the current end-of-service window for Zcashd.
Ironwood became urgent after the discovery of a critical vulnerability in Orchard, Zcash’s main shielded pool for private transactions. The issue was not a break in Zcash’s privacy model itself, but a soundness flaw in the zk-SNARK circuit logic used by Orchard to prove shielded transaction validity. Shielded Labs described the flaw as an under-constrained element in the Orchard circuit, where false inputs could pass a multiplication check, potentially allowing counterfeit ZEC to be created inside the shielded pool without that supply being visible on-chain.
The vulnerability existed from Orchard’s activation in May 2022 until an emergency fix was deployed on June 1, 2026. The fix stopped future exploitation of the known bug, but it did not fully eliminate the confidence problem because there is no cryptographic way to prove whether counterfeit notes were created before remediation. Shielded Labs has said prior exploitation appears unlikely, but Ironwood is designed to reduce reliance on that trust assumption by moving activity into a fresh shielded pool based on the fixed Orchard protocol.
.@jswihart on the road to Ironwood:
“The testnet’s already up, formal verification is progressing well, everything’s moving faster than we anticipated. Target is mid-to-late July for Ironwood activation.”
Zcash is shipping faster than anyone expected. pic.twitter.com/1GXfTcbV4i
— Cypherpunk ($CYPH) (@cypherpunk) June 20, 2026
ZebraD Migration Becomes Key Coordination Test
The upgrade also creates a significant operational coordination challenge because Zcashd, the legacy consensus node derived from Bitcoin’s codebase, is being retired as part of the process. “So for Zcashers, they know there’s Zcashd, which is the legacy consensus node that was, you know, the code for Bitcoin that will be retired as part of this process,” Swihart said. “And so people that are using that node are going to have to move to a new Rust-based consensus node called ZebraD.”
Swihart framed that migration as one of the larger practical risks around the activation schedule, not because the work is conceptually unclear, but because the ecosystem must coordinate new software adoption across node operators and infrastructure providers. “And so I actually think that coordination problem is probably the bigger problem. Not problem per se, but yeah, I mean, it’s just a lot of work,” he said. The timing matters because the Zcashd end-of-life window and Ironwood activation target are closely connected.
Ironwood’s technical purpose is to create a new shielded pool while closing the old Orchard pool to new outputs. Funds moving between shielded and transparent contexts pass through Zcash’s accounting “turnstile,” where aggregate inflows and outflows are publicly tallied even though individual shielded transactions remain private. By using that mechanism, Ironwood can cap how much ZEC exits the old Orchard pool and enters the new one, helping establish that no more ZEC leaves Orchard than legitimately entered it.
For Zcash, Ironwood is both a cryptographic remediation milestone and a live coordination test. Formal verification is meant to reduce the chance of another subtle circuit-level soundness failure, while the ZebraD migration requires infrastructure participants to complete a timely software transition. If the mid-to-late July activation target holds, the upgrade will mark the next step in Zcash’s effort to move beyond the Orchard vulnerability and rebuild verifiable confidence in its shielded accounting.
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.