Inside the Race to Fix Zcash's Shielded Pool Vulnerability | Markets Outlook

A critical vulnerability discovered in the Zcash Orchard shielded pool had existed in the codebase for approximately four years and survived multiple audits by cryptographers and third-party reviewers before being found by security researcher Taylor Ornby. Ornby used a combination of deep protocol expertise and Claude Opus 4.8, an AI tool released around the time of discovery, to identify the flaw. The bug theoretically allowed a malicious actor to create additional Zcash within the shielded pool, raising the possibility of undetected inflation.

There is no way to definitively confirm whether the vulnerability was exploited before discovery, though no unusual activity patterns consistent with exploitation have been observed. Zcash's turnstile feature, which limits and monitors total supply, provides some protection against undetected inflation, but the absence of evidence is not a guarantee the bug was never used.

After discovery, notification was handled via Signal under strict protocols limiting who was read in and what details they received. Otto, CEO of Zcash Development Labs and a former ECC team member, was notified, and three members of the core team carried out remediation. A soft fork was deployed approximately two days after discovery, followed by a hard fork roughly 24 hours later to fully close the vulnerability. The speed and containment of the response were presented as evidence of a mature security process.

The Orchard pool is governed by a circuit, a rulebook controlling how transactions are validated within the protocol. Historically this rulebook was hand-checked by cryptographers, a process that proved insufficient given the four-year window during which the bug went undetected. AI tools now make formal verification feasible, allowing computers to confirm that a circuit does exactly what it is intended to do. Following the disclosure, multiple independent groups began formally verifying the Orchard circuit, with many also using AI to search for additional issues.

Zcash's planned update called Ironwood is targeting a mid-to-late July release and includes a formally verified Orchard pool as a direct response to the incident. A longer-term project called Tachyon is also in development and will feature a simplified circuit rulebook designed to reduce vulnerability risk, with a release expected some months after Ironwood. The two-stage roadmap reflects both the urgency of closing the current gap and the longer effort required to redesign the underlying architecture.

Josh Svihardt argued that targeted audits by people with deep knowledge of the underlying protocol are more effective than broad bug bounty programs relying on random participants. He also stated that formal verification should now be considered standard practice across the industry given the availability of AI tools, and expressed concern that many protocols lack security processes as rigorous as Zcash's and may be unable to effectively remediate and fully disclose incidents when they occur. The implication is that the Zcash incident, while serious, exposed a gap in industry-wide security norms rather than a unique failure specific to Zcash.

On market context, swap data shows the top two assets being exchanged into Zcash are USDT and USDC, with Bitcoin ranking third. Svihardt noted that Zcash has existed since 2016 with a proof-of-work launch and fair distribution, and argued that its roughly ten-year price discovery history cannot be replicated by deploying similar technology on a newer chain, positioning longevity as a competitive differentiator that is independent of the vulnerability episode.