Zcash fixed a bug that could hide fake coins. The fix is a gate, not an audit.
Zero-knowledge privacy means you can't audit Zcash's pool for hidden inflation. The Ironwood fork builds a gate instead.
CryptoVibe Desk · zcash · zero-knowledge · protocol
- →Shielded Labs researcher Taylor Hornby found a bug in Zcash's Orchard pool that could allow hidden coin minting.
- →Zcash cannot audit the private pool after the fact, so Ironwood adds an exit cap on July 28.
- →Watch whether another shielded-pool chain copies the turnstile design within 12 months of Ironwood.
- Orchard pool → Zcash's private transaction layer where coin balances are hidden with advanced cryptography.
- zero-knowledge proof → A math technique that proves a transaction is valid without revealing amounts or identities.
- turnstile → A cryptographic gate that counts coins moving between pools and blocks excess withdrawals.
- hard fork → A protocol upgrade that changes the rules, so nodes must update to stay compatible.
A bug in Zcash's Orchard pool could hide fake coins.
Shielded Labs researcher Taylor Hornby found the flaw inside Orchard's issuance logic. U.Today says there is no evidence anyone used it. That's the catch: no evidence is not proof of a clean pool. In a zero-knowledge system, hidden inflation can stay hidden.
Ironwood activates on July 28 at block 3,428,143, according to U.Today. The hard fork does not try to prove the old pool is clean. Instead, a turnstile sits at the exit and enforces one rule: no more ZEC can leave than legitimately entered. Fake ZEC, if any exists, stays trapped.
The tradeoff is simple. Zcash gets supply checks without exposing private transactions. What it loses is only coins above the historical cap, which should not exist anyway. Legitimate holders move through the gate.
This is a checksum problem, not a proof-system failure. Orchard's zero-knowledge proofs still protect transaction privacy. Hornby's bug hit issuance logic, not the privacy layer. Your transaction privacy is intact. The supply accounting needed a gate.
If you hold ZEC in an Orchard wallet, expect your balance to look unavailable during migration. That pause is normal. Update wallet software before July 28. Exchanges and swap services may also pause ZEC deposits and withdrawals around activation.
Every shielded-pool chain now has a design reference. The turnstile shows how to cap supply without opening private balances. Read the Ironwood spec, not the announcement thread.
Zcash just gave shielded-pool projects a sharper test: either build an exit gate for hidden-issuance bugs, or admit supply privacy still lacks a clean recovery path.
Watch for a second shielded-pool chain to announce a turnstile-style supply safeguard within 12 months of Ironwood's July 28 activation. That would confirm this as a design standard, not a one-off Zcash fix.
Primary links and supporting reads used by the desk for this story.
Forward this.
