Zcash Orchard flaw prompts emergency fix and Ironwood supply-verification proposal

Zcash Orchard flaw prompts emergency fix and Ironwood supply-verification proposal

Developers completed Ironwood consensus changes for a planned July activation after patching the Orchard counterfeit-coin bug, with the upgrade set to replace the old pool and add supply-verification controls.

RUNE
ZEC

Fact Check
The claim accurately summarizes a well-documented event: a severe Orchard ZK-circuit vulnerability was discovered May 29, 2026 by Taylor Hornby using AI-assisted auditing, patched via emergency soft fork and NU6.2 hard fork (June 1-3), and publicly disclosed around June 4-5. ZEC fell up to 57% intraday and Hyperliquid OI dropped 51.6%, while Shielded Labs proposed strengthened formal verification and NU7 supply-integrity 'gate audit' checks.
Summary

After an emergency soft fork and the NU6.2 hard fork on June 3 fixed a severe vulnerability in Zcash’s Orchard shielded pool, developers proposed and then completed the consensus changes for the Ironwood upgrade, which is targeted for activation in July. The flaw, disclosed by Shielded Labs, could theoretically have allowed unlimited counterfeit ZEC inside private Orchard transactions, though the group said exploitation was unlikely and there is still no proof whether fake ZEC was ever created or withdrawn into wider circulation. Ironwood is designed to let node operators verify supply against Zcash’s expected mining schedule while replacing the old Orchard pool with a new privacy pool that uses turnstile accounting and a flag mechanism to restrict deposits into the old pool. ZEC partially rebounded after an initial plunge of more than 50% but remained down about 21% to 22% for the week, while ThorChain delayed its planned ZEC integration and Arthur Hayes said he sold his entire position.

Terms & Concepts
  • Orchard shielded pool: Zcash’s main privacy-preserving transaction pool, where transfers are hidden from public view.
  • turnstile accounting: A supply-checking mechanism designed to ensure assets entering and leaving a shielded pool remain consistent.
  • consensus rule changes: Protocol updates that alter how the network validates transactions and blocks.