Zcash Crashes More Than 50% After a Four-Year-Old Counterfeiting Vulnerability Goes Public
Zcash fell more than 50% on June 5 after Shielded Labs, a nonprofit developer on the protocol, disclosed a critical vulnerability that had existed in the network's Orchard shielded pool since May 2022. The bug was patched before the public announcement, but the disclosure itself triggered the selloff. The problem is not just that the flaw existed. It is that Zcash's own privacy design makes it impossible to prove with certainty whether anyone used it first.
WHAT THE BUG WAS
The vulnerability, present since Orchard's activation in May 2022, was discovered on May 29 by security engineer Taylor Hornby using Anthropic's Claude Opus 4.8 AI model and patched in an emergency fix by June 1. The flaw was a soundness bug in the implementation of the Orchard zero-knowledge proof circuit. In a zero-knowledge proof system, soundness means the protocol should only accept valid state transitions. This vulnerability broke that property: a successful exploit could have allowed an attacker to forge transactions and double-spend funds within the Orchard pool.
Shielded Labs said Hornby successfully developed a working exploit and demonstrated in a local testing environment that it could generate "unlimited, undetectable counterfeit ZEC." It could not, however, inflate the total ZEC supply. Zcash's turnstile mechanism, which tracks and enforces balance invariants across all value pools, provided a verifiable ground truth that the supply cap remained intact throughout the incident.
The Orchard pool was introduced with NU5 in May 2022 as the centerpiece of Zcash's privacy architecture. Built on the Halo 2 proving system, it was the first Zcash pool to require no trusted setup. The bug had existed in the codebase since that launch, a four-year window during which it went undetected.
WHY THE MARKET SOLD REGARDLESS
The technical response was swift. It involved two key releases: Zebra 4.5.3 for an emergency soft fork that temporarily disabled Orchard actions at a specific block height, followed by Zebra 5.0.0 activating the NU6.2 hard fork to restore functionality with the corrected circuit. The Zcash Foundation said there was no evidence the bug was exploited, no unauthorized value creation, and no impact on user privacy.
The market's response to that assurance was a 50%-plus collapse. The reason is embedded in the assurance itself. Shielded Labs says there is no cryptographic way to know whether the flaw was exploited before the fix. The Zcash team can say exploitation is unlikely. It cannot prove it did not happen. For a privacy coin, that distinction is load-bearing: the entire value proposition rests on cryptographic certainty, and the bug produced a window where that certainty was absent.
Arthur Hayes, the chief investment officer of Maelstrom, said he sold his entire Zcash position as a result. Hayes had previously described ZEC as part of a core trade thesis. His exit was public and amplified the selling pressure already hitting the token.
THE AUDITABILITY PROBLEM
Bitcoin's supply is fully auditable by anyone running a node. Every coin ever created can be traced from its coinbase transaction. The 21 million cap is not a trust-me claim; it is verifiable independently, in real time, by any participant in the network. That auditability is a design choice, not an oversight.
Zcash made the opposite design choice for its shielded pools. Privacy is the point of the product, and shielded transactions hide sender, receiver, and amount. The same feature that protects user privacy also prevents the network from proving its own supply integrity after an incident like this one. Shielded Labs is proposing a network upgrade with new accounting measures and expanded security efforts to restore confidence in ZEC's supply integrity. The proposal would enforce turnstile accounting on all Orchard tokens going forward, but it cannot retroactively audit the four years the bug was live.
This is not Zcash's first brush with a critical cryptographic flaw. In 2019, the team disclosed a counterfeiting vulnerability in the older Sprout shielded pool that had gone undetected for years. That bug was also never known to have been exploited. Two critical counterfeiting vulnerabilities across two different shielded pools, in the same protocol, discovered years apart. The pattern is the argument.
WHAT THIS CONFIRMS ABOUT BITCOIN
Privacy is a genuine and important problem in Bitcoin. Transactions on the base layer are pseudonymous, not anonymous, and the surveillance risk is real. The correct answer to that problem, from a Bitcoin-first view, is solutions that preserve base-layer auditability while adding privacy at higher layers, not a redesigned base layer where the supply cannot be verified.
Zcash was built on the premise that Bitcoin's transparency was the flaw. The Orchard vulnerability demonstrates why transparency at the base layer is a feature. A supply you cannot audit is a supply you cannot trust. The bug is patched. Whether the damage to trust in Zcash's supply integrity is also patchable is a different question, and the $118 million in forced liquidations on June 5 is the market's initial answer.
