Zcash drops 40% as Grayscale CLO questions Polymarket exploit odds

Grayscale's chief legal officer says on-chain activity from Zcash's shielded users may reveal more about exploit risk than Polymarket's prediction market.

Zcash fell 40% to below $350 as Grayscale Chief Legal Officer Craig Salm said on-chain shielded-user data beats Polymarket for exploit-risk signals.

"The Polymarket contract is interesting, but the real signal is whether shielded users continue transacting on Orchard," Salm said in a post on X. "If they stay, that's the strongest vote of confidence available."

Polymarket opened a market on June 8 asking whether the Orchard pool vulnerability, disclosed on June 4, was exploited on mainnet. ZEC has lost more than $3 billion in market value since the disclosure, with the token falling from above $600 to below $350. Arthur Hayes, co-founder of BitMEX, said his fund Maelstrom sold its entire ZEC position, calling the "Holy Trinity" trade dead.

The question of whether the vulnerability was exploited carries existential weight for Zcash. If confirmed, it would mark the first known undetectable counterfeiting event in a major privacy-focused blockchain, potentially crippling trust in the network's shielded pools. The next signal comes from on-chain activity in the days ahead.

The Orchard vulnerability and the uncertainty problem

The flaw, discovered on May 29 by Zcash researcher Taylor Hornby during an audit commissioned by Shielded Labs, existed in the Orchard zero-knowledge proof circuit. A soundness vulnerability in the halo2_gadgets component could have allowed the shielded pool to accept invalid state transitions, potentially enabling double-spending within Orchard. The network's turnstile mechanism prevented total supply inflation beyond the shielded pool.

Zcash developers deployed an emergency soft fork on June 2 through Zebra 4.5.3, temporarily suspending Orchard transactions, followed by a hard fork upgrade, NU6.2, on June 3 that restored functionality with a corrected circuit. The Zcash Foundation said there was no evidence of exploitation and no unauthorized value creation was detected.

But the disclosure from Zooko Wilcox, Jason McGee and Hornby on June 4 introduced a critical caveat: because of Orchard's privacy properties, there is no cryptographic way to prove whether the vulnerability was exploited while it existed. That distinction drove Hayes to exit. "While I think it's extremely unlikely of any minting, it cannot be formally cryptographically proved impossible," he wrote.

What on-chain activity could reveal

Salm's argument rests on a behavioral signal. If Zcash's privacy-conscious user base continues to route transactions through the Orchard pool after the fix, it suggests those closest to the protocol — and most exposed to any exploit risk — have confidence the vulnerability was not exploited. A mass exodus from Orchard to transparent addresses or Sapling would imply the opposite.

More than 4.5 million ZEC were subject to operational limits during the stabilization phase, according to estimates from Shielded Labs. Transparent transactions and Sapling-based transactions continued to function normally throughout the event, giving users alternatives if they chose to avoid Orchard.

The Polymarket contract, by contrast, relies on a binary outcome that may never be definitively resolved. Privacy-preserving systems by design obscure transaction history, meaning no external auditor can produce a cryptographic proof of innocence or guilt. The market's odds will reflect information asymmetry — those closest to the investigation versus the broader public.

Zcash has managed serious protocol flaws before. An earlier inflation risk in the Sprout pool was fixed without any loss of funds. But the Orchard incident is the first where the network's privacy properties prevent a definitive post-mortem, leaving residual uncertainty that markets have already priced in through a 40 percent selloff.

This article is for informational purposes only and does not constitute investment advice.