Zcash’s ZEC slid roughly 45% on June 5, 2026, after protocol founder Zooko Wilcox and other ecosystem figures publicly described a critical flaw tied to the network’s Orchard shielded pool. The headline threat was simple. If the bug had been usable on mainnet before the fix, an attacker could have created counterfeit ZEC without detection.
Because Orchard is a shielded pool, Zcash’s privacy design also blocks the clean forensic answer. The disclosure says there is no cryptographic way to prove whether counterfeiting happened before the patch. That uncertainty is the kind of problem markets hate, even when the fix is already in.
What Zooko and the researchers said was broken
In a Twitter post dated June 4, 2026, Zooko Wilcox described a vulnerability tied to the Orchard circuit. According to the disclosure summarized by Crypto Potato, researchers had recently found and patched a flaw that could have allowed unlimited counterfeit ZEC creation inside Orchard while still producing proofs that looked valid.
The reported cause was an “under-constrained” element in the Orchard circuit. In proof systems, circuits are mathematical checks that validate private transactions without exposing sensitive details. An under-constrained circuit allegedly “did not fully check something it was supposed to be checking.” In this case, the flaw enabled insertion of false inputs into elliptic curve multiplication while the resulting proof still appeared valid.
The disclosure also says the researcher reportedly built a complete exploit and tested it locally. In that environment, the exploit generated virtually unlimited undetectable counterfeit ZEC. The authors further acknowledge that if the same tool had reached mainnet before the fix, it could have minted directly in real Zcash wallets.
Timeline: discovery, fix, and the window of exposure
Crypto Potato’s account places the discovery on May 29, 2026. Security researcher Taylor Hornby found the vulnerability while reviewing the Orchard circuit.
Hornby was hired in April 2026 by Shielded Labs to conduct ongoing security research on Zcash. The disclosure ties the discovery to targeted work rather than a random find. Hornby used Anthropic’s Opus 4.8 model as part of a targeted audit of the Orchard circuit after Opus 4.8 was released on May 28, 2026.
The disclosure says Hornby then disclosed the issue to the Zcash Open Development Lab (ZODL). ZODL coordinated an emergency response across the Zcash ecosystem, completing the fix by June 2, 2026. That closes the risk window, at least after the patch went in.
What we cannot time is harm. Because the relevant signals are hidden by design, Crypto Potato reports the authors concluded there is no definitive cryptographic method to determine whether the counterfeit-capability was exploited before patching.
Why privacy turns a bug into an evidence problem
On a transparent public blockchain, investigators can often look for abnormal coin-creation patterns or suspicious spending behavior. In Orchard, Crypto Potato says the protocol hides the details that would help prove what happened.
Orchard activated in May 2022. The disclosure therefore implies a long exposure period in theory. Crypto Potato states that the bug “could” have been present for over four years. But the key point is not that counterfeiting occurred. It is that Zcash’s privacy features make it impossible to prove the negative.
The authors also argue prior exploitation was unlikely. Their reasons in Crypto Potato’s summary are:
- Orchard’s vulnerability reportedly went unnoticed for years despite scrutiny by security engineers and cryptographers.
- Hornby was specifically onboarded to search for deep protocol vulnerabilities, and the discovery was tied to focused work.
- The fix arrived within days of discovery.
ZEC market reaction
The market reaction arrived fast. Crypto Potato reports ZEC fell from above $600 to around $300 within hours on June 5, 2026, based on the included CoinGecko chart.
The correlation matches the disclosure moment. Crypto Potato attributes the crash to Wilcox’s public explanation of a massive vulnerability that could have enabled counterfeit minting.
| Item | Detail (per Crypto Potato) |
|---|---|
| Asset moved | ZEC |
| Reported intraday drop | ~45% |
| Price reference | Above $600 to ~ $300 in hours |
| Discovery date | May 29, 2026 |
| Fix completed | June 2, 2026 |
| Vulnerable component | Orchard shielded pool circuit |
| Technical root cause | “Under-constrained” check enabling false inputs to elliptic curve multiplication |
| Proof / forensics limitation | Privacy prevents cryptographic proof of whether exploitation happened before patch |
What comes next: a supply-integrity upgrade
The disclosure does not stop at patching. Crypto Potato says Shielded Labs is working with other Zcash developers on a possible network upgrade to let users more reliably verify the integrity of the ZEC supply.
The proposed direction described by Crypto Potato involves creating a new shielded pool and using “turnstile accounting” for coins leaving Orchard. The goal is a controlled migration path. Coins moving from the old pool to the new one would follow rules designed to ensure more ZEC cannot leave than legitimately entered.
Crypto Potato also notes such an upgrade would not happen automatically. It would require community support through the normal governance process.
AI’s role, minus the hype
The Orchard incident also put AI-assisted tooling in the spotlight. Hornby used Anthropic’s Opus 4.8 model during the targeted audit that led to the finding, Crypto Potato says.
The disclosure is careful on attribution. It does not claim AI “found the bug on its own.” Instead, it frames the process as an experienced researcher applying advanced tools plus expert analysis in a high-stakes cryptographic setting.
Crypto Potato reports Shielded Labs is accelerating proactive research of that kind.
The unanswered question markets can’t shrug off
A patched vulnerability is a win for security teams. But this one lands in a different bucket because the disclosure says there is no cryptographic way to confirm whether exploitation happened before the fix, thanks to privacy.
Zcash now has a choice to make visible to users. It can keep relying on patched code and trust-based assessments. Or it can pursue the proposed integrity-verification upgrade described by Crypto Potato. Either way, the core lesson this incident underlines is painfully concrete. In privacy-first systems, “we fixed it” does not automatically translate to “we know everything that happened.”