Skip to main content
Sign in

Audit log

Every state-changing event for Zcash Orchard Counterfeit Vulnerability: moderation decisions on community submissions, plus corrections and updates from the news pipeline. URL-based decisions carry three independent witnesses — the original source, an Internet Archive snapshot taken at submission time, and a Solana memo signed by our publicly-disclosed publisher key.

  1. #1publishby system:backfill
    2026-06-17 23:04:46Z
    Score: ?? (no score change)
    anchoranchored
    chain
    mainnet-betaslot 427,166,199
    sig
    3fqHU73euE4b…d7UFvDfnexplorer ↗
    hash
    6dAzdpFQiXDN…xKactgd7sha256 → base58
    verifying row…full verify ↗
    canonical bytes (24258 B) ▸
    {"actor":"system:backfill","investigation_id":"f187a829-54e4-4673-b2b7-6c4dea8103c9","kind":"publish","page_slug":"zcash-orchard-counterfeit-vulnerability","published_at":"2026-06-17T23:04:46.349Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"Zcash Orchard Counterfeit Vulnerability","sections":[{"content":"The vulnerability was a soundness bug in the Orchard zero-knowledge proof circuit, specifically in the halo2_gadgets crate used by Zcash. The flaw consisted of an under-constrained elliptic curve multiplication gadget — two lines of code — that allowed mathematically invalid inputs to pass a verification check that was designed to reject them. Because Orchard uses zero-knowledge proofs to conceal transaction details, any counterfeit ZEC created through this flaw would have been indistinguishable from legitimately issued coins on the public ledger. Affected software versions included halo2_gadgets before v0.5.0, orchard before v0.14.0, and zcashd versions v5.0.0 through v6.12.3. Notably, the flaw could not inflate the visible total supply, but could allow value to be created inside the shielded pool without public on-chain record. Sapling and transparent transaction pools were not affected.","heading":"Vulnerability Overview","severity":"critical","sources":[{"credibility":2,"name":"Decrypt: ZEC Crashes 38% as Zcash Discloses 'Critical Counterfeiting Vulnerability'","type":"news_article","url":"https://decrypt.co/370105/zec-crashes-38-as-zcash-discloses-critical-counterfeiting-vulnerability"},{"credibility":2,"name":"The Block: Security researcher finds Zcash vulnerability allowing 'unlimited' counterfeit minting","type":"news_article","url":"https://www.theblock.co/post/403698/zcash-vulnerability-zec-drops"},{"credibility":1,"name":"Shielded Labs: The Orchard Counterfeiting Vulnerability","type":"official","url":"https://shieldedlabs.net/the-orchard-counterfeiting-vulnerability/"},{"credibility":1,"name":"Zcash Community Forum: The Orchard Counterfeiting Vulnerability and Next Steps","type":"official","url":"https://forum.zcashcommunity.com/t/the-orchard-counterfeiting-vulnerability-and-next-steps/56015"}]},{"content":"Taylor Hornby, an independent security engineer engaged by Shielded Labs in April 2026 specifically to identify protocol-level vulnerabilities before malicious actors could, discovered the bug on May 29, 2026. Hornby used a custom AI-assisted auditing framework built around Anthropic's Claude Opus 4.8 model, which had been publicly released on May 28, 2026 — the day before the discovery. Hornby developed a working proof-of-concept exploit that generated unlimited undetectable counterfeit ZEC in a local test environment. Upon discovery, Hornby immediately disclosed the vulnerability to the Zcash Open Development Lab (ZODL), which coordinated an emergency patch. The public disclosure followed on June 5, 2026 after the patch had been deployed. The vulnerability had been present since Orchard's mainnet activation in May 2022, an undetected window of approximately four years.","heading":"Discovery and Disclosure Timeline","severity":"high","sources":[{"credibility":1,"name":"CoinDesk: Zcash plummets 38% as Shielded Labs reveals a major bug that went undetected for four years","type":"news_article","url":"https://www.coindesk.com/markets/2026/06/05/zcash-plummets-30-as-developer-reveals-a-major-bug-that-went-undetected-for-four-years"},{"credibility":2,"name":"Unchained Crypto: AI-Assisted Audit Uncovers Critical Zcash Orchard Vulnerability","type":"news_article","url":"https://unchainedcrypto.com/ai-assisted-audit-uncovers-critical-zcash-orchard-vulnerability-that-could-have-minted-unlimited-counterfeit-zec/"},{"credibility":2,"name":"BeInCrypto: An Opus 4.8 Audit Uncovered Zcash's Bug","type":"news_article","url":"https://beincrypto.com/zcash-zec-orchard-counterfeiting-bug/"},{"credibility":2,"name":"Blockhead: Claude AI Finds Critical Vulnerability in Zcash","type":"news_article","url":"https://www.blockhead.co/2026/06/05/zcash-founder-discloses-critical-orchard-forgery-flaw-fixed-by-emergency-hard-fork/"}]},{"content":"ZODL coordinated a rapid emergency response. On June 1, 2026, at approximately 22:30 EDT, the Zcash network activated a temporary protocol-level disable of all Orchard-containing transactions, requiring miners to halt Orchard transaction processing. The patch activated at mainnet block height 3,363,426 at approximately 02:00 UTC on June 2. ZODL released zcashd v6.12.5, which addressed the consensus vulnerability. The upgrade produced observable network instability, including a reported 25-block fork and 37 total orphaned blocks during the switchover. Service providers including Cake Wallet temporarily suspended ZEC functionality. On June 3, a full hard fork network upgrade (NU6.2) completed, re-enabling Orchard with the corrected circuit. ZODL stated that no known exploitation occurred before the intervention and that all user funds remained secure.","heading":"Emergency Patch and Network Response","severity":"high","sources":[{"credibility":2,"name":"CryptoTimes: Zcash Executes Emergency Fork After Critical Orchard Vulnerability Discovery","type":"news_article","url":"https://www.cryptotimes.io/2026/06/02/zcash-executes-emergency-fork-after-critical-orchard-vulnerability-discovery/"},{"credibility":1,"name":"Zcash Community Forum: The Orchard Counterfeiting Vulnerability and Next Steps","type":"official","url":"https://forum.zcashcommunity.com/t/the-orchard-counterfeiting-vulnerability-and-next-steps/56015"},{"credibility":2,"name":"Crypto Economy: Zcash Pushes Emergency Update to Patch Orchard Bug, Network Briefly Unstable","type":"news_article","url":"https://crypto-economy.com/zcash-pushes-emergency-update-to-patch-orchard-bug-network-briefly-unstable/"},{"credibility":2,"name":"KuCoin: Zcash Deploys Emergency Update to Fix Orchard Bug","type":"news_article","url":"https://www.kucoin.com/news/flash/zcash-deploys-emergency-update-to-fix-orchard-bug-network-experiences-brief-instability"}]},{"content":"The most consequential aspect of this incident is an acknowledged permanent uncertainty. Shielded Labs stated explicitly: 'due to the privacy properties of Orchard and the nature of the bug, there is no definitive way to determine using only cryptography whether such exploitation occurred.' This is a structural characteristic of Zcash's design: because Orchard hides balances and transaction details by design, counterfeit ZEC created through this flaw would be cryptographically indistinguishable from legitimate ZEC. The four-year exposure window (May 2022 to June 1, 2026) means that if any actor had independently discovered the vulnerability, activity would leave no attributable on-chain signature. Shielded Labs assessed exploitation as 'unlikely' on grounds that the vulnerability evaded years of scrutiny by expert cryptographers and was found only through deliberate, targeted AI-assisted review — but this assessment is probabilistic, not verifiable. The proposed Ironwood upgrade (see below) is designed to make this uncertainty partially resolvable by tracking migration flows through a turnstile mechanism.","heading":"Exploitation Uncertainty — Cannot Be Ruled Out Cryptographically","severity":"critical","sources":[{"credibility":1,"name":"Shielded Labs: The Orchard Counterfeiting Vulnerability","type":"official","url":"https://shieldedlabs.net/the-orchard-counterfeiting-vulnerability/"},{"credibility":1,"name":"CoinDesk: Zcash plummets 38% as Shielded Labs reveals a major bug that went undetected for four years","type":"news_article","url":"https://www.coindesk.com/markets/2026/06/05/zcash-plummets-30-as-developer-reveals-a-major-bug-that-went-undetected-for-four-years"},{"credibility":1,"name":"Bloomberg: Crypto Token's 50% Wipeout Shows Scale of AI-Hacking Threat","type":"news_article","url":"https://www.bloomberg.com/news/articles/2026-06-14/crypto-token-s-50-wipeout-shows-magnitude-of-ai-hacking-threat"}]},{"content":"ZEC fell from approximately $635 on June 4, 2026 to a low of approximately $309 on June 5 — a decline of approximately 51% from peak to trough in under 48 hours. On a 24-hour basis, CoinDesk and Decrypt reported a 38% decline. Arthur Hayes, former BitMEX CEO and chief investment officer of Maelstrom Fund, publicly disclosed that he liquidated his entire ZEC position following the disclosure, stating that Zcash's privacy thesis 'demands perfection' and that the inability to cryptographically confirm whether the flaw was exploited made continued holding untenable. One large investor reportedly lost more than half the value of an approximately $174 million ZEC position. A large on-chain withdrawal of approximately 202,000 ZEC from the Orchard pool coincided with the incident, according to Crypto Briefing. Following the June 8 Ironwood upgrade proposal, ZEC rebounded approximately 45% from its post-disclosure low near $300, but remained down approximately 22% for the week.","heading":"Market Impact","severity":"high","sources":[{"credibility":1,"name":"CoinDesk: Arthur Hayes dumps Zcash holdings after Orchard Pool vulnerability revealed","type":"news_article","url":"https://www.coindesk.com/markets/2026/06/05/arthur-hayes-dumps-zcash-holdings-after-orchard-pool-vulnerability-revealed"},{"credibility":2,"name":"Decrypt: ZEC Crashes 38% as Zcash Discloses 'Critical Counterfeiting Vulnerability'","type":"news_article","url":"https://decrypt.co/370105/zec-crashes-38-as-zcash-discloses-critical-counterfeiting-vulnerability"},{"credibility":2,"name":"Crypto Briefing: Zcash's Orchard pool sees 1% withdrawal as counterfeiting bug shakes investor confidence","type":"news_article","url":"https://cryptobriefing.com/zcash-orchard-pool-withdrawal-counterfeiting-bug/"},{"credibility":2,"name":"BitMEX Blog: Why Zcash Crashed Nearly 50% in 48 Hours","type":"news_article","url":"https://www.bitmex.com/blog/zec-crash-2026"},{"credibility":1,"name":"CoinDesk: Zcash bounces 45% as developers propose new Ironwood upgrade","type":"news_article","url":"https://www.coindesk.com/markets/2026/06/08/zcash-bounces-45-as-developers-propose-new-ironwood-upgrade"}]},{"content":"Following the disclosure, Zcash developers proposed the Ironwood network upgrade, targeted for late July 2026, as a structural solution to supply integrity uncertainty. Ironwood creates a new shielded pool using the corrected Orchard circuit, while blocking new deposits into the original Orchard pool and permitting only outbound migration. Funds exiting the old Orchard pool pass through a turnstile mechanism — Zcash's on-chain accounting system that tracks cumulative inflows and outflows per pool and rejects any transaction attempting to move more ZEC than legitimately entered. If all legitimate funds successfully migrate through the turnstile without rejection, and the original Orchard pool is emptied, this would constitute strong evidence that the vulnerability was never exploited. The upgrade is additionally backed by formal circuit verification, independent audits, and continued AI-assisted security review. However, developers acknowledged that build and coordination timelines may extend beyond the target date.","heading":"Ironwood Upgrade — Proposed Remediation","severity":"medium","sources":[{"credibility":1,"name":"CoinDesk: Zcash bounces 45% as developers propose new Ironwood upgrade","type":"news_article","url":"https://www.coindesk.com/markets/2026/06/08/zcash-bounces-45-as-developers-propose-new-ironwood-upgrade"},{"credibility":2,"name":"CryptoTimes: Zcash Orchard Vulnerability: Zooko Explains Why Ironwood Matters","type":"news_article","url":"https://www.cryptotimes.io/2026/06/15/how-zcashs-ironwood-turnstiles-will-trap-counterfeit-coins/"},{"credibility":2,"name":"CryptoNews: Zcash Ironwood Upgrade Finalizes to Patch Orchard Pool Flaw, Targets July","type":"news_article","url":"https://cryptonews.com/news/zcash-ironwood-upgrade-orchard-pool-flaw-july/"},{"credibility":2,"name":"KuCoin: Zcash to Launch Ironwood Upgrade at End of July 2026","type":"news_article","url":"https://www.kucoin.com/blog/en-zcash-to-launch-ironwood-upgrade-at-end-of-july-2026-enhanced-privacy-and-transparency"}]},{"content":"The incident exposed a fundamental tension in shielded cryptocurrency design. Zcash's Orchard pool uses zero-knowledge proofs to guarantee transaction privacy — the same property that makes it impossible to audit the pool's internal state for anomalies. Bitcoin's and Ethereum's transparent ledgers allow anyone to verify total supply at any time; Zcash's shielded pools do not. Arthur Hayes articulated this tension upon his exit, noting that privacy-first systems demand architectural perfection because any flaw that permits value creation inside a shielded pool is inherently undetectable ex-post. Ripple CTO David Schwartz commented publicly that Zcash appeared safe, while acknowledging the counterfeit minting scenario could not be conclusively disproven. The Bloomberg article on this incident characterized it as illustrating the broader 'scale of AI-hacking threat' to cryptographic systems, noting that AI-assisted auditing is a double-edged capability that can be used by white hats and malicious actors alike.","heading":"Structural Risk: Privacy Architecture vs. Supply Auditability","severity":"high","sources":[{"credibility":1,"name":"Bloomberg: Crypto Token's 50% Wipeout Shows Scale of AI-Hacking Threat","type":"news_article","url":"https://www.bloomberg.com/news/articles/2026-06-14/crypto-token-s-50-wipeout-shows-magnitude-of-ai-hacking-threat"},{"credibility":2,"name":"CryptoNews: Ripple CTO Says Zcash is Safe: But Fake ZEC Bug Not Disproven","type":"news_article","url":"https://cryptonews.com/news/david-schwartz-ripple-zcash-orchard-vulnerability/"},{"credibility":1,"name":"CoinDesk: Arthur Hayes dumps Zcash holdings after Orchard Pool vulnerability revealed","type":"news_article","url":"https://www.coindesk.com/markets/2026/06/05/arthur-hayes-dumps-zcash-holdings-after-orchard-pool-vulnerability-revealed"}]},{"content":"The SEC had previously investigated the Zcash Foundation, closing that investigation in January 2026 without enforcement action — removing a major regulatory overhang several months before this vulnerability event. No specific regulatory response to the Orchard vulnerability disclosure has been reported as of the investigation date (June 17, 2026). The incident does not involve allegations of fraud by Zcash developers; rather, it represents a cryptographic implementation flaw subsequently patched. No law enforcement or regulatory action specific to this vulnerability has been identified in available sources.","heading":"Regulatory Background","severity":"low","sources":[{"credibility":2,"name":"CryptoTimes: Zcash Executes Emergency Fork After Critical Orchard Vulnerability Discovery","type":"news_article","url":"https://www.cryptotimes.io/2026/06/02/zcash-executes-emergency-fork-after-critical-orchard-vulnerability-discovery/"}]}],"sources_used":[{"credibility":1,"name":"Shielded Labs: The Orchard Counterfeiting Vulnerability","type":"official","url":"https://shieldedlabs.net/the-orchard-counterfeiting-vulnerability/"},{"credibility":1,"name":"Zcash Community Forum: The Orchard Counterfeiting Vulnerability and Next Steps","type":"official","url":"https://forum.zcashcommunity.com/t/the-orchard-counterfeiting-vulnerability-and-next-steps/56015"},{"credibility":1,"name":"CoinDesk: Zcash plummets 38% as Shielded Labs reveals a major bug that went undetected for four years","type":"news_article","url":"https://www.coindesk.com/markets/2026/06/05/zcash-plummets-30-as-developer-reveals-a-major-bug-that-went-undetected-for-four-years"},{"credibility":1,"name":"CoinDesk: Arthur Hayes dumps Zcash holdings after Orchard Pool vulnerability revealed","type":"news_article","url":"https://www.coindesk.com/markets/2026/06/05/arthur-hayes-dumps-zcash-holdings-after-orchard-pool-vulnerability-revealed"},{"credibility":1,"name":"CoinDesk: Zcash bounces 45% as developers propose new Ironwood upgrade","type":"news_article","url":"https://www.coindesk.com/markets/2026/06/08/zcash-bounces-45-as-developers-propose-new-ironwood-upgrade"},{"credibility":1,"name":"Bloomberg: Crypto Token's 50% Wipeout Shows Scale of AI-Hacking Threat","type":"news_article","url":"https://www.bloomberg.com/news/articles/2026-06-14/crypto-token-s-50-wipeout-shows-magnitude-of-ai-hacking-threat"},{"credibility":2,"name":"Decrypt: ZEC Crashes 38% as Zcash Discloses 'Critical Counterfeiting Vulnerability'","type":"news_article","url":"https://decrypt.co/370105/zec-crashes-38-as-zcash-discloses-critical-counterfeiting-vulnerability"},{"credibility":2,"name":"Unchained Crypto: AI-Assisted Audit Uncovers Critical Zcash Orchard Vulnerability","type":"news_article","url":"https://unchainedcrypto.com/ai-assisted-audit-uncovers-critical-zcash-orchard-vulnerability-that-could-have-minted-unlimited-counterfeit-zec/"},{"credibility":2,"name":"The Block: Security researcher finds Zcash vulnerability allowing 'unlimited' counterfeit minting","type":"news_article","url":"https://www.theblock.co/post/403698/zcash-vulnerability-zec-drops"},{"credibility":2,"name":"Crypto Briefing: Zcash plunges 38% after critical counterfeiting vulnerability disclosure","type":"news_article","url":"https://cryptobriefing.com/zcash-plunges-counterfeiting-vulnerability/"},{"credibility":2,"name":"Crypto Briefing: Zcash's Orchard pool sees 1% withdrawal as counterfeiting bug shakes investor confidence","type":"news_article","url":"https://cryptobriefing.com/zcash-orchard-pool-withdrawal-counterfeiting-bug/"},{"credibility":2,"name":"CryptoTimes: Zcash Executes Emergency Fork After Critical Orchard Vulnerability Discovery","type":"news_article","url":"https://www.cryptotimes.io/2026/06/02/zcash-executes-emergency-fork-after-critical-orchard-vulnerability-discovery/"},{"credibility":2,"name":"CryptoTimes: Zcash Orchard Vulnerability: Zooko Explains Why Ironwood Matters","type":"news_article","url":"https://www.cryptotimes.io/2026/06/15/how-zcashs-ironwood-turnstiles-will-trap-counterfeit-coins/"},{"credibility":2,"name":"Crypto Economy: Zcash Pushes Emergency Update to Patch Orchard Bug, Network Briefly Unstable","type":"news_article","url":"https://crypto-economy.com/zcash-pushes-emergency-update-to-patch-orchard-bug-network-briefly-unstable/"},{"credibility":2,"name":"CryptoNews: Zcash Ironwood Upgrade Finalizes to Patch Orchard Pool Flaw, Targets July","type":"news_article","url":"https://cryptonews.com/news/zcash-ironwood-upgrade-orchard-pool-flaw-july/"},{"credibility":2,"name":"CryptoNews: Ripple CTO Says Zcash is Safe: But Fake ZEC Bug Not Disproven","type":"news_article","url":"https://cryptonews.com/news/david-schwartz-ripple-zcash-orchard-vulnerability/"},{"credibility":2,"name":"BeInCrypto: An Opus 4.8 Audit Uncovered Zcash's Bug","type":"news_article","url":"https://beincrypto.com/zcash-zec-orchard-counterfeiting-bug/"},{"credibility":2,"name":"BitMEX Blog: Why Zcash Crashed Nearly 50% in 48 Hours","type":"news_article","url":"https://www.bitmex.com/blog/zec-crash-2026"},{"credibility":2,"name":"KuCoin: Zcash to Launch Ironwood Upgrade at End of July 2026","type":"news_article","url":"https://www.kucoin.com/blog/en-zcash-to-launch-ironwood-upgrade-at-end-of-july-2026-enhanced-privacy-and-transparency"},{"credibility":2,"name":"Blockhead: Claude AI Finds Critical Vulnerability in Zcash","type":"news_article","url":"https://www.blockhead.co/2026/06/05/zcash-founder-discloses-critical-orchard-forgery-flaw-fixed-by-emergency-hard-fork/"}],"summary":"On June 5, 2026, Shielded Labs publicly disclosed a critical four-year-old soundness bug in Zcash's Orchard shielded pool that, if exploited, could have allowed unlimited undetectable counterfeit ZEC minting. The vulnerability was discovered on May 29, 2026 by security researcher Taylor Hornby using AI-assisted auditing tools, silently patched via emergency hard fork on June 2, and cannot be definitively ruled out as having been exploited due to Orchard's inherent privacy architecture. ZEC fell approximately 38–50% in the 48 hours following public disclosure.","timeline":[{"date":"2022-05-01","event":"Zcash Orchard shielded pool activates on mainnet. The soundness vulnerability in the halo2_gadgets elliptic curve multiplication circuit is present from launch.","source":"Shielded Labs disclosure","source_url":"https://shieldedlabs.net/the-orchard-counterfeiting-vulnerability/"},{"date":"2026-01-01","event":"SEC closes investigation into Zcash Foundation without enforcement action, removing a significant regulatory overhang.","source":"CryptoTimes","source_url":"https://www.cryptotimes.io/2026/06/02/zcash-executes-emergency-fork-after-critical-orchard-vulnerability-discovery/"},{"date":"2026-04-01","event":"Shielded Labs engages security engineer Taylor Hornby for a targeted protocol security review of Zcash.","source":"CoinDesk","source_url":"https://www.coindesk.com/markets/2026/06/05/zcash-plummets-30-as-developer-reveals-a-major-bug-that-went-undetected-for-four-years"},{"date":"2026-05-28","event":"Anthropic releases Claude Opus 4.8, the AI model that Hornby would use the following day to identify the Orchard vulnerability.","source":"BeInCrypto","source_url":"https://beincrypto.com/zcash-zec-orchard-counterfeiting-bug/"},{"date":"2026-05-29","event":"Taylor Hornby discovers the critical soundness vulnerability in the Orchard ZK proof circuit using AI-assisted auditing tools. He develops a working proof-of-concept exploit generating unlimited undetectable counterfeit ZEC in a test environment. Hornby immediately discloses to ZODL.","source":"CoinDesk","source_url":"https://www.coindesk.com/markets/2026/06/05/zcash-plummets-30-as-developer-reveals-a-major-bug-that-went-undetected-for-four-years"},{"date":"2026-06-01","event":"Emergency protocol patch activates at 22:30 EDT, disabling all Orchard-containing transactions at mainnet block height 3,363,426. ZODL releases zcashd v6.12.5.","source":"CryptoTimes","source_url":"https://www.cryptotimes.io/2026/06/02/zcash-executes-emergency-fork-after-critical-orchard-vulnerability-discovery/"},{"date":"2026-06-03","event":"Hard fork network upgrade NU6.2 completes, re-enabling Orchard with the corrected circuit. Network experiences brief instability including a 25-block fork and 37 orphaned blocks during the switchover.","source":"Crypto Economy","source_url":"https://crypto-economy.com/zcash-pushes-emergency-update-to-patch-orchard-bug-network-briefly-unstable/"},{"date":"2026-06-04","event":"ZEC trades at a high of approximately $635.","source":"Decrypt","source_url":"https://decrypt.co/370105/zec-crashes-38-as-zcash-discloses-critical-counterfeiting-vulnerability"},{"date":"2026-06-05","event":"Shielded Labs publicly discloses the vulnerability. ZEC falls approximately 38% in 24 hours to approximately $309, a decline of approximately 51% from the June 4 high. Arthur Hayes publicly liquidates his entire ZEC position.","source":"CoinDesk","source_url":"https://www.coindesk.com/markets/2026/06/05/arthur-hayes-dumps-zcash-holdings-after-orchard-pool-vulnerability-revealed"},{"date":"2026-06-08","event":"Zcash developers propose the Ironwood network upgrade as a structural solution to supply integrity uncertainty. ZEC rebounds approximately 45% from post-disclosure lows.","source":"CoinDesk","source_url":"https://www.coindesk.com/markets/2026/06/08/zcash-bounces-45-as-developers-propose-new-ironwood-upgrade"},{"date":"2026-06-14","event":"Bloomberg publishes analysis characterizing the incident as illustrating the broad 'scale of AI-hacking threat' to cryptographic systems.","source":"Bloomberg","source_url":"https://www.bloomberg.com/news/articles/2026-06-14/crypto-token-s-50-wipeout-shows-magnitude-of-ai-hacking-threat"},{"date":"2026-06-15","event":"Zcash founder Zooko publishes explanation of how Ironwood's turnstile mechanism will function as a live supply audit during pool migration.","source":"CryptoTimes","source_url":"https://www.cryptotimes.io/2026/06/15/how-zcashs-ironwood-turnstiles-will-trap-counterfeit-coins/"}]},"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision e6e4bc32-d32a-4276-99c4-a2c3d8a1acc1
How verification works. The “Row integrity” check above is computed in your browser — your machine recomputes the SHA-256 of the canonical bytes and compares against the stored hash. No avoid.net server can fake that check. The “full verify” link goes one level deeper: your browser fetches the on-chain transaction from a Solana RPC node and confirms the same hash is in the memo. If you don’t want to trust either avoid.net or the public RPC, run the CLI verifier on your own machine — python -m src.verify_decision <event_id>.