Zcash’s long‑promised Ironwood upgrade is edging closer to activation — first on testnet — as developers rush to shore up confidence after a high‑profile supply integrity scare that wiped out more than half of ZEC’s market value in days.
What’s happening
- Ironwood, announced in June, adds a new shielded pool and an on‑chain accounting system designed to let anyone cryptographically verify Zcash’s circulating supply while keeping transaction details private. The upgrade is meant to remove the lingering uncertainty left by a four‑year‑old flaw in the Orchard shielded pool that was disclosed in May.
- The Orchard bug, discovered by security researcher Taylor Hornby (who used Anthropic’s Claude Opus 4.8 during the investigation), was patched on June 1. But because Zcash’s privacy technology prevented a definitive cryptographic audit of past transactions, developers could not prove whether counterfeit ZEC had ever been created — sparking panic and a rapid price collapse from above $600 to around $300 in two days. ZEC has since recovered roughly half that loss and was trading near $457, data from CoinGecko shows.
Progress and timeline
- Developers say Ironwood is approaching testnet activation. Zcash co‑founder Zooko Wilcox noted Shielded Labs’ focus on security and on a new “Zero” project to help enterprise users — exchanges, mining pools and wallets — transition safely to Ironwood.
- Zcash developer Sean Bowe wrote that “sufficient hash rate is signaling technical readiness for the mainnet upgrade,” and stressed that formal verification work is running in parallel to reassure users about supply integrity. His main concern: some wallets may not be ready in time — but he argued that available alternatives and testnet time mean this shouldn’t delay Ironwood.
- Jason McGee of Shielded Labs said teams are running two parallel efforts: activating Ironwood (NU6.3) and migrating the ecosystem from legacy zcashd to the new Z3 stack (Zebra full node, Zaino indexing service, and Zallet wallet). Testnet activation is expected “shortly,” with the current goal to complete both efforts by late July.
Technical safeguards and risks
- Developers are pursuing formal verification of the new circuit and aim to complete a proof of soundness before Ironwood goes live.
- The bigger operational risk is partner readiness: key Z3 components like Zallet and Zaino are still being developed, and exchanges, pools and wallet providers must deploy and test updates. Feedback from ecosystem participants is mixed — some will be ready, others asked for more time.
- To reduce deployment risk, teams are evaluating options such as delaying Ironwood, commissioning independent third‑party security audits, or temporarily supporting Ironwood through zcashd while partners finish migration. The shared priority remains rapid activation while ensuring a secure, smooth transition.
Why it matters
Ironwood is the protocol-level fix aimed at restoring trust in Zcash’s supply integrity without sacrificing privacy — a must after the Orchard disclosure rattled users and markets. If the upgrade and the Z3 migration succeed on schedule, Zcash could close this chapter and give exchanges, custodians and users a concrete way to verify circulating supply going forward.
What to watch
- Official testnet activation and results
- The completion of formal verification / proof of soundness
- Responses from major exchanges, mining pools and wallet providers about their readiness
- Any decision to delay or phase the upgrade to lessen operational risk
Developers say they’re focused on activating Ironwood quickly but safely — a balancing act that will determine whether Zcash can fully restore confidence after one of the protocol’s most consequential security scares.
Read more AI-generated news on: undefined/news
