Zcash Orchard Flaw Patched by Emergency Fork; Shielded Labs Seeks Supply Proof Upgrade
SecurityLayer 1
Neutral

Zcash Orchard Flaw Patched by Emergency Fork; Shielded Labs Seeks Supply Proof Upgrade

Zcash activated an emergency soft fork and then the NU6.2 hard fork in early June to fix a soundness bug in the Orchard privacy pool. Shielded Labs now proposes a further upgrade so anyone can verify the supply is intact.

Nov 1, 2026, 09:02 AMUpdated Nov 3, 2026, 05:05 AM4 min read

Written by CoinArticle’s AI Newsroom · from 4 cited sources. How we work

Story Updates

  • Updated Nov 3, 2026, 05:05 AM: Zebra 5.0.0 release details, node upgrade guidance, and Foundation statement on no unauthorized value creation added.
  • Updated Nov 2, 2026, 10:02 AM: Zcash Foundation and Helius/CipherScan reports add the Foundation's double-spend framing and clarify the post-upgrade explorer disruption.

The Flaw and the Emergency Response

Zcash activated an emergency soft fork at 02:00 UTC on June 2, at block 3,363,426, temporarily rejecting transactions and blocks containing Orchard actions. The NU6.2 hard fork followed on June 3 at 00:05 EDT, at block 3,364,600, re-enabling Orchard with a corrected circuit. The Zcash Foundation said the hard fork was required because the circuit fix needs a new pinned verifying key, and it has released Zebra 4.5.3 and Zebra 5.0.0 to implement the changes.

Taylor Hornby, a security researcher working for Shielded Labs, found the bug on May 29 during a protocol audit and disclosed it the same day. ZODL engineers Daira-Emma Hopwood, Kris Nuttycombe and Jack Grigg confirmed the issue within hours. The Foundation said private coordination with miners and exchanges began May 31 to reduce the chance of exploitation before public disclosure. The first soft fork attempt ran into patch deployment problems, and a revised release activated on June 2.

The flaw was a soundness bug in the zero-knowledge proof circuit underlying Orchard, the newest shielded pool, which launched with NU5 in 2022 and uses Halo 2. The proof system could accept a statement it should have rejected. The Foundation said the practical risk was invalid state changes inside Orchard and possible double-spending within that pool. Affected code included older halo2_gadgets, orchard and zcash_primitives releases, plus zcashd versions 5.0.0 through 6.12.3.

Shielded Labs has said that, applied to mainnet, the exploit could have generated unlimited ZEC within Orchard without detection. The Foundation's framing and Shielded Labs' framing differ on that scope.

The AI Attribution Question

Shielded Labs says Hornby used Anthropic's Opus 4.8, released May 28, together with a custom AI harness and prompts, to produce a complete local exploit in a regtest environment. Zcash has not independently verified the specific role AI played in the research. The attribution is the developer's claim, not a confirmed finding.

The case fits a broader pattern. In February 2026, security firm Octane disclosed that its AI found a high-severity bug in Nethermind, an Ethereum execution client, that could have halted local block production for roughly 38% of Ethereum validators. That bug was patched before exploitation. A January 2026 arXiv paper reported a 63% success rate for AI-agent exploit generation on a smart contract benchmark, work focused on the application layer rather than base-layer code.

Supply Assurance and Where the Two Positions Diverge

The Foundation's position is that there is no evidence of mainnet exploitation, that there is "no evidence of unauthorized value creation," and that the 21 million ZEC cap remains protected by the turnstile mechanism tracking value moving between pools. Shielded Labs takes a harder line. It argues that Orchard's privacy properties make it cryptographically difficult to prove the supply was never tampered with, and it has proposed a further upgrade that would route coins through turnstile accounting so anyone can verify integrity directly.

The disagreement is over what can be shown, not whether the bug was fixed. Both sides accept the emergency patch closed the known flaw. They differ on whether past issuance can be independently proven sound.

Upgrade Mechanics and Node Operator Action

Node operators face the main near-term task of upgrading to Zebra 5.0.0 rather than relying on older releases. Operators that remained on an incorrect fork after NU6.2 may need to resync from scratch or restore from a backup taken before activation. The Foundation said Sapling and transparent transactions continued operating normally while Orchard actions were paused, and that user privacy was not harmed. The release also marks the second security-driven protocol upgrade in Zcash history since 2016.

Network Status After the Upgrade

Following NU6.2 activation, reports circulated on social media that the network had stopped producing blocks for more than four hours. Helius CEO Mert Mumtaz said the network was never down and that the affected explorer apps were connected to a bad node. Zcash explorer CipherScan said its nodes were still upgrading to support NU6.2, so it showed stale or missing data during the transition. The disruption was in block-reading infrastructure rather than the chain itself.

Market Reaction and Shielded Usage

ZEC traded as high as $611 intraday before the disclosure and then fell sharply, settling near $421. Market commentary framed the move as a repricing between "patched" and "proven clean" rather than a verdict on the network's technology. Separate reporting on the later upgrade describes ZEC holding around $600, a figure that conflicts with the lower settlement level and should be read with that uncertainty in mind.

The disclosure came as shielded use was rising. One recent report said about 30% of ZEC supply had moved into shielded pools, with Orchard holding 4.2 million ZEC and most of the recent growth.

What to Watch

The open questions are whether the proposed turnstile-based upgrade gains the coordinated sign-off from miners, exchanges, wallet providers and infrastructure operators that a consensus change requires, and whether an independent audit of historical Orchard issuance is published. The compressed timeline, under five days from discovery to hard-fork activation, is itself a test of the network's coordination process that observers will likely cite in future assessments.

Why It Matters

For Traders

ZEC has repriced sharply around the disclosure, and any vote or audit on the proposed supply-proof upgrade could move the price again within days.

For Investors

The gap between a patched bug and a provably sound supply is a structural question for privacy coins, and the turnstile proposal will shape how that risk is weighed.

For Builders

Any protocol relying on zero-knowledge proof circuits should review verifying key management and expect AI-assisted review to surface soundness bugs quickly.

This article is for information only and is not financial advice. Read the full disclaimer.

Related Articles

Latest News