Skip to content

ZK Cryptocurrency Attack Surface Analysis — Structured Report

Authorized Security Research | Generated 2026-06-05


SECTION 1: Privacy Coins Using ZK Circuits (zk-SNARKs, Bulletproofs, etc.)

Projects with shielded transaction pools using zero-knowledge proofs. Primary risks: under-constrained circuits enabling counterfeit coins, supply-integrity violations, and privacy-set deanonymization.

1A. Direct Zcash Forks (Inherit Zcash Circuit Design)

These projects forked Zcash source code at various upgrade milestones. They directly inherit Zcash's zk-SNARK proving system (Groth16, Sprout/Sapling/Orchard circuits) and carry the same structural risk profile for under-constrained circuit bugs.

#ProjectTickerFork LineageZK TechShielded PoolGitHub / SourceAudits / Formal VerificationMC TierLaunchedKnown Vulns / Notes
1ZcashZECBitcoin-core (original)zk-SNARKs (Groth16, Halo 2, Orchard)Shielded pool (z-addr), opt-ingithub.com/zcash/zcashNCC, Least Authority, Trail of Bits; Formal spec (Zcash Protocol Spec)Top 20 (~$6.6B)20162019 "Infinite Counterfeit" bug — under-constrained Sprout circuit allowed counterfeit ZEC. Fixed. Orchard Halo 2 circuit formally verified.
2Horizen (ex-ZenCash)ZENZcash forkzk-SNARKs (Groth16, Sprout/Sapling)Shielded pool (z-addr)github.com/HorizenOfficial/zenHorizen audits (partially documented); zkVerify sidechain launched 2024Top 100 (~$89M)2017Pivoted from privacy coin to ZK-proof verification L1 (zkVerify). Shielded pool still present but deprioritized. NEARLY EMPTY shielded pool = low anonymity set.
3KomodoKMDZcash fork (via ZClassic)zk-SNARKs (Groth16, Sapling)Shielded pool (z-addr), opt-ingithub.com/KomodoPlatform/komodoLimited public auditsMicro (~$694K)2016 (ICO)dPoW security model. Shielded pool nearly unused. AtomicDEX-focused.
4Pirate ChainARRRKomodo/Zcash forkzk-SNARKs (Groth16, Sapling)Shielded-only (z-addr mandatory)github.com/PirateNetwork/pirateCommunity-reviewed; no major firm auditsTop 500 (~$69M)2018HIGH PRIORITY: Shielded-only means ALL supply is in shielded pool. Any counterfeit coins are un-auditable by design. Largest anonymity set among Zcash forks.
5ZClassicZCLZcash fork (pre-Sapling, pre-dev-fund)zk-SNARKs (Groth16, Sprout only?)Shielded pool (z-addr)github.com/zclassicdev/zclassicNo modern auditsSub-2000 (~$3.5M)2016Forked BEFORE Sapling upgrade. May not have Orchard circuit fixes. Stale codebase — last major update years ago. AT RISK of known circuit bugs.
6YcashYECZcash fork (post-Sapling, pre-Canopy)zk-SNARKs (Groth16, Sapling)Shielded pool (z-addr)github.com/ycashfoundation/ycashInherits Zcash audits; no independent auditsSub-2000 (~$3.9M)2019Forked to preserve 90% mining reward. May lag upstream Orchard/Halo updates.
7HushHUSHZcash forkzk-SNARKs (Groth16, Sapling)Shielded pool (z-addr)github.com/MyHush/hushCommunity auditedSub-3000 (~$519K)2017Multi-chain clone (HUSH, HSC, SDL). VERY low usage.
8BitcoinZBTCZZcash forkzk-SNARKs (Groth16, Sprout)Shielded pool (z-addr)github.com/btcz/bitcoinzNo known professional auditsSub-3000 (~$352K)2017GPU-mining focused. Sprout-era circuits likely. AT RISK of known Sprout bugs.
9ZeroZERZcash forkzk-SNARKs (Groth16)Shielded pool (z-addr)github.com/zerocurrencycoin/zeroNo known auditsSub-4000 (~$289K)2017Dead/minimal activity.
10GhostGHOSTZcash codebase (via PIVX?)zk-SNARKs (Sapling)Shielded poolgithub.com/ghostbypivx/ghostNo known auditsSub-3000 (~$587K)2020John McAfee-linked project. Disputed legitimacy.

1B. Other Privacy Coins Using ZK Circuits (Non-Zcash Fork)

#ProjectTickerChain LineageZK TechShielded PoolGitHub / SourceAudits / Formal VerificationMC TierLaunchedKnown Vulns / Notes
11MoneroXMRCryptoNote (Bytecoin fork)Bulletproofs + RingCT + stealth addressesMandatory privacy (ring signatures + RingCT + stealth addresses)github.com/monero-project/moneroMultiple academic audits; Kudelski, Quarkslab, Trail of BitsTop 20 (~$6.15B)2014Not zk-SNARK — Bulletproofs are range proofs, not circuit-based. No counterfeit coin risk from circuit bugs. Risk is deanonymization via ring signature analysis (FloodXMR, EAE attacks).
12Firo (ex-Zcoin)FIROOwn chain (Zerocoin -> Sigma -> Lelantus -> Lelantus Spark)Sigma protocol (ZK proofs, no trusted setup); Lelantus SparkLelantus Spark shielded poolgithub.com/firoorg/firoTrail of Bits (Lelantus Spark audit 2022); Least Authority;Sub-1000 (~$14M)20162017 Zerocoin bug — typo allowed minting 370K fake XZC ($440K stolen). 2018 Zerocoin cryptographic flaw (RSA accumulator attack). Switched from Zerocoin to Sigma (2019) to Lelantus Spark.
13PIVXPIVXDash fork (hybrid: Dash MN + Zcash Sapling zk-SNARKs)zk-SNARKs (Groth16, Sapling circuit)SHIELD (Sapling z-addr)github.com/PIVX-Project/PIVXLeast Authority (Sapling integration audit)Sub-1500 (~$5.5M)2016Hybrid transparent/shielded. Backported Zcash Sapling circuits. Inherits Zcash circuit risks.
14Dusk NetworkDUSKOwn L1zk-SNARKs (PLONK — self-designed "PlonKup")Phoenix shielded TXgithub.com/dusk-networkMultiple audits (ABDK, etc.)Top 500 (~$57M)2019 (testnet)Custom ZK circuit (PlonKup). HIGH PRIORITY: Novel self-designed circuits = higher under-constraint risk than battle-tested Groth16/Sapling.
15Mina ProtocolMINAOwn L1Recursive zk-SNARKs (Kimchi/Pickles — O(1) blockchain)All transactions ZK by defaultgithub.com/MinaProtocol/minaMultiple audits (O(1) Labs); Formal verification (Kimchi circuit)Top 500 (~$59M)2021SUPPLY INTEGRITY RISK: Entire chain is a single recursive ZK proof. Bug in recursive circuit = undetectable state corruption. No historical tracking like Bitcoin.
16AleoALEOOwn L1zk-SNARKs (Varuna/Marlin — R1CS-based)All TX private by default (Leo programs)github.com/AleoHQ/snarkOSTrail of Bits, NCC Group, Zellic (2023-2024)Top 500 (~$40M)2024 (mainnet)Leo language for private smart contracts. CUSTOM CIRCUIT RISK — each Leo program generates new R1CS constraints.
17MidnightNIGHTCardano sidechainzk-SNARKs (specific scheme TBD)Private smart contractsNot yet open source (testnet 2024-2025)Unknown; IOG-developedTop 100 (~$558M)2025 (anticipated)IOG/Cardano ecosystem. Circuit design not yet public.
18Iron FishIRONOwn L1zk-SNARKs (Groth16)All TX shielded by defaultgithub.com/iron-fish/ironfishTrail of Bits (2023)Sub-1400 (~$6.4M)2023Full-privacy L1. Uses Groth16 circuits for shielded TX.
19MobileCoinMOBStellar forkzk-SNARKs (Bulletproofs + RingCT adapted)Shielded TX via Fog ledgergithub.com/mobilecoinfoundation/mobilecoinNCC Group, Trail of BitsNo data2020Signal integration. Fog architecture for private payments.
20BeamBEAMOwn chain (MimbleWimble + Lelantus-MW)MimbleWimble + Lelantus-MW (Bulletproofs+)Lelantus-MW shielded poolgithub.com/BeamMW/beamTrail of Bits, Least AuthoritySub-1800 (~$3.2M)2019MW is not circuit-based in ZK sense. Lelantus-MW adds ZK layer.
21GrinGRINOwn chain (MimbleWimble)MimbleWimble (Pedersen commitments + Bulletproofs)Cut-through transactions (not pool-based)github.com/mimblewimble/grinCoinspect, QuarkslabSub-1300 (~$6.7M)2019No shielded pool — MW aggregates TX, doesn't pool them. Coinbase halted GRIN transfers after 51% attacks.

SECTION 2: ZK-Rollup L2 Projects (Ethereum & Beyond)

These projects use ZK validity proofs to batch L2 state transitions on L1. Under-constrained ZK circuits could enable invalid state transitions, fund theft, or counterfeit asset minting on the rollup.

2A. General-Purpose zkEVMs (Validity Proofs)

#ProjectTickerChainZK TechProof SystemGitHub / SourceAudits / Formal VerificationMC TierLaunchedKnown Vulns / Notes
22Polygon zkEVMPOL (ex-MATIC)Ethereum L2zk-SNARKs (STARK-to-SNARK wrapper: PIL + eSTARK -> Groth16)zkEVM circuit (full EVM opcode ZK)github.com/0xPolygonHermez/zkevm-proverHexens, Spearbit; Formal verification ongoingTop 100 (~$894M)2023HIGH PRIORITY: Full EVM equivalence in ZK is extremely complex. Over 100+ EVM opcodes each with ZK constraints. Polygon zkEVM has an adversarial testing program.
23zkSync EraZKEthereum L2zk-SNARKs (PLONK-based, Boojum proof system)zkEVM circuit (custom zkVM)github.com/matter-labs/zksync-eraOpenZeppelin, Certora (formal verification of core circuits)Top 500 (~$106M)2023Custom zkVM (not EVM bytecode compatible at circuit level). Boojum is a STARK-based prover with PLONK wrapping.
24LineaLINEAEthereum L2zk-SNARKs (PLONK-based, Vortex prover)zkEVM circuit (Consensys)github.com/Consensys/linea-monorepoInternal Consensys audits; public audit reports partialTop 500 (~$80M)2023Consensys-built. Closed-source prover initially; opening gradually.
25Scroll(no token at time of data)Ethereum L2zk-SNARKs (Halo 2 — same as Zcash Orchard)zkEVM circuitgithub.com/scroll-tech/scroll-proverTrail of Bits, OpenZeppelin; Formal verification of critical pathsN/A2023USES HALO 2 (Zcash Orchard proof system!). Directly inherits Halo 2 circuit design patterns. Scroll team contributes to Halo 2 upstream.
26TaikoTAIKOEthereum L2zk-SNARKs (multi-proof: RISC Zero STARK + SGX TEE)Based ZK-rollup (Ethereum sequencing)github.com/taikoxyz/taiko-monoTrail of Bits, Quantstamp, Code4renaSub-900 (~$17M)2024Multi-proof architecture (ZK + SGX). "Based" rollup — uses Ethereum validators for sequencing.
27LoopringLRCEthereum L2 (app-specific)zk-SNARKs (Groth16)DEX circuit (order-book matching)github.com/Loopring/protocolsLeast Authority, Trail of BitsSub-900 (~$17M)2019Oldest production ZK-rollup DEX. Battle-tested circuits but older Groth16 setup.
28AztecAZTECEthereum L2 (privacy)zk-SNARKs (UltraPLONK/Honk, custom Noir DSL)Private L2 (UTXO model with ZK)github.com/AztecProtocol/aztec-packagesTrail of Bits, NCC Group; Multiple Zellic auditsTop 500 (~$54M)2025 (testnet)HIGH PRIORITY: Noir DSL for private smart contracts. Each Noir program compiles to ZK constraints. User-written circuits = massive untested attack surface. UTXO privacy model.
29Manta NetworkMANTAPolkadot + Ethereum L2zk-SNARKs (Groth16)MantaPay (shielded pool on Polkadot); Manta Pacific (Celestia DA)github.com/Manta-NetworkVeridise, Trail of BitsTop 500 (~$38M)2023Forked Zcash Sapling circuits for MantaPay. Inherits Zcash circuit risks.
30Hermez NetworkHEZEthereum L2 (acquired by Polygon)zk-SNARKs (original Hermez prover -> Polygon zkEVM)Payment networkgithub.com/hermeznetworkPre-acquisition auditsTop 600 (~$34M)2021Acquired by Polygon to form Polygon zkEVM. Legacy token.

2B. StarkNet / STARK-Based Projects

#ProjectTickerChainZK TechProof SystemGitHub / SourceAudits / Formal VerificationMC TierLaunchedKnown Vulns / Notes
31StarkNetSTRKEthereum L2zk-STARKs (Cairo VM)STARK prover/verifier (Stone/Stwo)github.com/starkware-libs/cairoMultiple audits; Formal verification of Cairo core; Ethereum Foundation grantsTop 200 (~$219M)2022STARKs are quantum-resistant but larger proofs. Cairo VM is a custom non-EVM architecture. Different bug class than SNARKs (no trusted setup, different constraint risks).
32Immutable XIMXEthereum L2 (app-specific NFT)zk-STARKs (StarkEx)StarkEx Validiumgithub.com/immutable/imx-contractsLeast Authority, Consensys DiligenceTop 250 (~$117M)2021StarkEx-based. App-specific (NFT/gaming), not general purpose.
33dYdX v3DYDX (v3)Ethereum L2 (app-specific)zk-STARKs (StarkEx)StarkEx for perpetualsgithub.com/dydxprotocolMultiple auditsTop 200 (pre-v4)2021Migrated to Cosmos (dYdX v4). StarkEx is still securing v3. Largest perp DEX.

2C. Additional ZK-Rollup & Infra Projects

#ProjectTickerChainZK TechNotesMC Tier
34zkLink NovaZKLAggregation L3Multi-chain ZK aggregationLinks multiple L2s via ZK proofsTop 600
35Mina ProtocolMINAL1 (ZK-recursive)Kimchi/Pickles recursive SNARKsAlso listed in Section 1BTop 500
36CartesiCTSIEthereum L2Optimistic + ZK (Cartesi Machine)Linux VM on-chain — RISC-V ZKSub-800

SECTION 3: Privacy Protocols & Mixers on Other Chains (Tornado Cash Successors)

Mixers and privacy protocols using ZK proofs on existing L1s (Ethereum, BSC, etc.). Under-constrained circuits here = fake deposit notes enabling theft from the anonymity pool.

#ProjectTickerHost ChainZK TechPrivacy MechanismGitHub / SourceAuditsMC TierLaunchedKnown Vulns / Notes
37Tornado CashTORNEthereum, BNB, Polygon, Arbitrum, Optimism, Avalanche, Gnosiszk-SNARKs (Groth16, circom circuits)Mixer — fixed-denomination deposit/withdraw (0.1, 1, 10, 100 ETH)github.com/tornadocash/tornado-coreABDK (original circuits); Formal verification of MiMC hashTop 800 (~$21M)2019OFAC-SANCTIONED (2022). Original circuits are well-audited. Groth16 proving key was compromised via trusted setup ceremony concern. Contract still operational (immutable). Huge anonymity set.
38RailgunRAILEthereum, BNB, Polygon, Arbitrumzk-SNARKs (Groth16)Privacy pool (not fixed-denomination mixer). Users shield/unshield any token.github.com/Railgun-PrivacyTrail of Bits, ABDK (v2/v3 circuits)Top 250 (~$133M)2021HIGH PRIORITY: "Private Proof of Innocence" — users prove deposits aren't from known-bad addresses. Complex circuits combining ZK + membership proofs.
39Aztec Connect (deprecated)Ethereumzk-SNARKs (UltraPLONK)Cross-shielded-pool DeFi bridgegithub.com/AztecProtocol/aztec-connect-bridgesMultiple auditsN/A (sunset 2024)2022Sunset in 2024 — Aztec pivoting to full L2. Connect bridges had 2023 vulnerability: missing ZK constraint in bridge contract.
40Panther ProtocolZKPEthereum, Polygon, multi-chainzk-SNARKszAsset shielded pool (cross-chain privacy)github.com/pantherprotocolZellic, HackenSub-2000 (~$2.2M)2023Cross-chain privacy using ZK. zAssets = shielded representations of any token.
41Privacy Pools (Ameen Soleimani)N/AEthereumzk-SNARKsTornado Cash successor with "association sets"github.com/ameensol/privacy-poolsUnder developmentN/A (no token)2024Tornado Cash spiritual successor by ex-Tornado dev. Proof-of-Innocence concept. Actively developed.
42Cyclone ProtocolCYCIoTeX, Ethereum, BNBzk-SNARKs (Groth16)Mixer (fixed denominations)github.com/cycloneprotocolCertiKMicro (~$0)2021Multi-chain mixer. Low adoption.
43Semaphore (protocol)N/A (infra)Ethereumzk-SNARKs (Groth16, circom)ZK identity/group membership (basis for many mixers)github.com/semaphore-protocol/semaphorePSE-audited; used by Worldcoin, etc.N/A2020Foundational ZK protocol used by many privacy apps. CIRCUIT IS CRITICAL INFRA — bugs here propagate to all dependents.
44Elixir (privacy)(various)Ethereumzk-SNARKs (circom)Privacy mixerUnclearUnknownMicro2022Low-activity mixer.
45Manta AtlanticMANTAPolkadotzk-SNARKs (Groth16)MantaPay (shielded pool, Zcash Sapling fork)github.com/Manta-NetworkVeridise, Trail of BitsTop 5002023Zcash Sapling fork on Polkadot. Same risk profile as Zcash forks.

SECTION 4: Priority Testing Targets

TIER 1 — HIGHEST VALUE FOR AI-ASSISTED CIRCUIT AUDIT

PriorityProjectRationale
CRITICALZcash (ZEC)Original circuit. Orchard Halo 2 circuits are public. $6.6B at stake. Formal spec exists = perfect for AI-assisted audit. Known precedent of under-constrained circuit bug (2019).
CRITICALScrollUses Halo 2 (Zcash Orchard) directly. zkEVM complexity. Massive bridge TVL.
CRITICALAztec (Noir DSL)User-written ZK circuits via Noir DSL = nearly infinite untested attack surface. Billions in potential bridge volume.
HIGHPirate Chain (ARRR)Shielded-only = supply integrity un-auditable. If counterfeit coins exist, nobody can detect them. $69M MC.
HIGHMina Protocol (MINA)Entire state is one recursive proof. Counterfeit supply is mathematically undetectable without full state reconstruction.
HIGHAleo (ALEO)New L1 with custom circuits. Leo programs can be audited individually.
HIGHRailgun (RAIL)Complex "Proof of Innocence" circuits. Large TVL across multiple chains.
HIGHPolygon zkEVM (POL)Most complex zkEVM circuit in production. Full EVM equivalence.
HIGHDusk Network (DUSK)Self-designed PlonKup circuit (not battle-tested Groth16).

TIER 2 — SIGNIFICANT BUT LOWER URGENCY

PriorityProjectRationale
MEDIUMTornado Cash (TORN)Very well audited. Groth16 circuits are simple (fixed denominations). OFAC sanctions complicate testing.
MEDIUMzkSync Era (ZK)Boojum STARK prover is novel. Large TVL.
MEDIUMFiro (FIRO)History of critical ZK bugs (2017 Zerocoin counterfeit, 2018 RSA flaw). Lelantus Spark is new.
MEDIUMManta Network (MANTA)Zcash Sapling fork. Lower complexity but inherits upstream risk.
MEDIUMStarkNet (STRK)Different bug class (STARKs). No trusted setup risk. Cairo 2.0 migration.
MEDIUMMidnight (NIGHT)IOG-developed. Circuit design not yet public.
LOWDormant Zcash forks (ZCL, YEC, BTCZ, HUSH, ZER, GHOST)Stale code. Known to lack Orchard fixes. Nearly zero economic value but useful for testing circuit bugs on dead coins.

SECTION 5: Methodology Notes for AI-Assisted Circuit Auditing

Under-Constrained Circuit Detection Strategy

  1. Static analysis of circom/R1CS/Halo 2 circuits: Look for missing constraints in signal assignments. Pattern: a signal is computed but never equality-checked against expected value in the constraint system.

  2. Differential circuit analysis: Compare Zcash forks against upstream to identify which circuit fixes they've missed.

  3. Adversarial proof generation: Using a modified prover to generate "valid" proofs for invalid state transitions (supply inflation).

  4. Privacy-pool supply audit: For shielded-only chains (ARRR), reconstruct total supply bounds by analyzing transparent coinbase + shielded pool in-flow/out-flow delta. If coinbase - transparent_out !== shielded_pool_balance, counterfeit coins exist.

Key Questions Per Project

  • Which Zcash circuit milestone does this fork include? (Sprout / Sapling / Orchard / NU5?)
  • Does the project use a publicly audited trusted setup? (Groth16 requires MPC ceremony)
  • Has the proving/verification key been independently verified?
  • Are there any custom circuit modifications beyond stock Zcash?
  • What is the shielded pool anonymity set size over time?

Report compiled from: CoinGecko API (privacy coins, ZK category, rollup category, L2 category), Wikipedia (Zcash, Zerocoin, Monero), L2Beat, project GitHub repositories, and known audit/trail reports. Market data as of 2026-06-05. This analysis is for authorized security research purposes only.

Released under the MIT License.