Opus 4.8 found a 4-year counterfeiting bug in Zcash that cryptographers missed, and ZEC dropped 31%

Security engineer Taylor Hornby, using a custom AI auditing framework paired with Anthropic's Opus 4.8 (released May 28), found a critical flaw in Zcash's Orchard protocol on May 29 that could have minted unlimited, undetectable counterfeit ZEC (Unchained). The bug had been live since Orchard activated in May 2022. Four years. An emergency two-phase network upgrade finished the fix June 2. ZEC fell about 31% on disclosure. And because of Zcash's own privacy design, it's cryptographically impossible to know whether the flaw was ever exploited. The story hit 783 points on Hacker News.

This is the one that rearranged my priors. Orchard is shielded-pool cryptography, the kind of code that gets the most expert eyes per line of anything in software. Professional cryptographers, formal review, years of scrutiny, real money on the line. And a critical unlimited-counterfeiting bug sat there since 2022 until a human pointed a frontier model at it.

It doesn't stand alone either. A developer reported Opus 4.8 one-shot a formally verified polygon-intersection proof that earlier models couldn't produce (GitHub/HN). Goedel-Architect is an agentic framework doing Lean 4 theorem proving via blueprint decomposition (arXiv). Three separate data points, same week, all pointing at a step change in machine-checkable, formal-methods, deep-correctness work with the late-May Opus release. The capability didn't creep. It jumped.

Be precise about what this is and isn't. It's not "AI replaces auditors." A skilled human built the framework, aimed it, and validated the finding. The model didn't wake up and decide to audit Zcash. But the assumption that adversarial review is a purely human ceiling, that enough expert eyes eventually catch everything, just took real damage. If a four-year-old bug in the most-scrutinized cryptography in crypto fell to one engineer plus Opus 4.8, what's sitting in your codebase that's had far fewer eyes?

What to do about it: run an AI-assisted audit pass on your security-critical code. Not as a replacement for review, as a second adversary with a different failure profile than a human reviewer. Point a frontier model specifically at invariants, auth boundaries, and anything handling money or access. The Zcash result says the floor on what this catches is higher than you think.