David Schwartz Ripple says ZEC holders who skip Ironwood migration face no loss if no exploit occurred, as the Zcash community debates a four-year supply blindspot.
David Schwartz Ripple’s former CTO and current CTO Emeritus, entered the Zcash Orchard vulnerability debate on June 7 with a specific claim: holders who do not migrate will not lose their ZEC. The thread he walked into had been running for three days.
The question sitting at the top of that exchange came from @satorinakamoto on X: how does Zcash prove the exploit never happened without implying a backdoor exists? Nobody answered that cleanly.
Four Years, One Bug, and an AI That Found It First
The vulnerability had been sitting inside the Orchard circuit since May 2022. Taylor Hornby found it on May 29, 2026, while running a protocol audit for Shielded Labs. He used Anthropic’s Opus 4.8, released a day earlier, as part of a targeted review of the circuit. Hornby disclosed the flaw to ZODL engineers that same evening, according to the original forum post authored by Zooko Wilcox, Jason McGee, and Hornby himself.
Hornby wrote a working exploit and tested it in a local regtest environment. Unlimited, undetectable counterfeit ZEC. That was the result. He did not run it on mainnet. Per the post, ZODL coordinated an emergency response and patched the flaw by June 2.
Shielded Labs acknowledged no one can cryptographically prove whether exploitation occurred before the fix. That uncertainty is the whole problem. The team said it anyway, which was the responsible thing and also the thing that kept the forum busy for days.
Who Owns What in a Pool With No Memory
Forum user scalar noted the real circulating supply sits at roughly 16.75 million ZEC, per on-chain data. Exchange-held coins mostly never touched the Orchard pool. The exposure, if any, belongs to holders who kept funds in Orchard specifically.
BTC2Zconversion argued the only honest audit would require every major exchange to publicly report their ZEC holdings, combined with cold wallet disclosures. That figure could then be reconciled against the known supply. The same user said plainly this will not happen. Supercut suggested AI tools should be tracking nullifiers for unusual patterns since the vulnerability window opened.
Shawn, lead moderator on the forum, corrected one widely repeated claim. Counterfeit ZEC cannot be identified by the network. Four point eight million coins went into the Orchard pool. Four point eight million can come out. BTC2Zconversion read that and replied with a single line: so last one out is a rotten egg.
Schwartz: Deprecated Is Not Dead
Writing as @JoelKatz on X, David Schwartz said ZEC left behind in the deprecated Orchard pool after Ironwood goes live will remain accessible. Safe, he said. Just lonely. The Ironwood upgrade itself is designed to let the network verify circulating supply integrity through a new shielded pool with turnstile accounting applied to all Orchard coins.
@CatOfLongTails on X offered a behavioral version of proof: if the deprecated pool retains leftover funds after migration, that is a practical signal nobody drained it. Not a proof. A signal.
Community member Happydao launched a public Orchard Integrity Monitor two days ago tracking value pool balances, supply signals, and post-patch metrics. It does not prove anything. Feedback, per the post, is welcome.
The former Ripple executive has been active on crypto policy in recent months. His comments on the CLARITY Act drew parallel attention from the broader blockchain space earlier this year.
Leave a Reply
You must be logged in to post a comment.