Skip to main content

This site is for educational purposes only. Nothing here constitutes financial advice.

Topic 97 of 189

Zcash Architecture

How Zcash uses zk-SNARKs to enable optional shielded transactions, why Sapling was the breakthrough that made shielded pool usage practical, and how Halo2 removed the trusted setup.

Beginner
8 min readUpdated July 2026Block Clarity Hub Editorial Team

The basics

Zcash's Optional Privacy Model

Zcash (ZEC) launched October 2016 as a privacy-focused cryptocurrency using zk-SNARKs. Unlike Monero, Zcash offers optional privacy — users choose between transparent transactions (like Bitcoin) or shielded transactions (with zero-knowledge proofs). This dual mode was intended to balance privacy needs with regulatory compatibility. In practice, transparent transactions have dominated usage historically, though shielded usage has grown substantially through 2023-2025.

The zk-SNARK Innovation

Zcash pioneered production zk-SNARK use in cryptocurrency. Its shielded transactions use zero-knowledge proofs to hide sender, receiver, and amount while proving the transaction is valid (no double-spends, correct math). At launch in 2016, this was cutting-edge cryptography — much of the modern ZK ecosystem traces back to Zcash's research and implementations. Even Ethereum's ZK rollups rely on cryptography with substantial Zcash-heritage contributions.

Major Evolution Milestones

Sprout (2016): original shielded implementation using BCTV14 SNARKs. Practical but slow. Sapling (2018): dramatic performance improvement using BGM17 SNARKs — shielded transactions became fast enough for common use. Orchard (2022): further improvements using Halo 2 SNARKs, which importantly eliminated the need for trusted setup. NU5 and later upgrades brought better wallet support and reduced friction. Each major upgrade has substantially improved shielded pool usability.

  • Zcash launched October 2016 — pioneered production zk-SNARKs in crypto
  • Optional shielded transactions vs Monero's mandatory privacy
  • Sprout → Sapling → Orchard evolution improved performance dramatically
  • Halo 2 (Orchard) eliminated trusted setup requirement

Key Takeaways

  • Zcash was the first production zk-SNARK cryptocurrency
  • Optional privacy design — users choose transparent or shielded
  • Sapling made shielded usage practical at scale
  • Halo 2 in Orchard eliminated trusted setup — a major cryptographic advance

Going deeper

Shielded Pool Mechanics

Zcash's shielded pool works via zero-knowledge proofs. Users deposit ZEC (transparent) → z-address (shielded). Once shielded, transactions between z-addresses hide sender/receiver/amount. Withdrawal from shielded pool back to t-address (transparent) reveals the amount and destination. The 'shielded pool' is the collective pool of shielded UTXOs; anonymity depends on the pool's size and diversity. Larger pools with diverse activity provide better anonymity than small quiet pools.

The Trusted Setup Problem

Sprout and Sapling required trusted setup ceremonies. If the ceremony's toxic waste was compromised, attackers could create counterfeit ZEC undetectably. Zcash held multi-party computation ceremonies (Powers of Tau) to reduce this risk — as long as at least one participant destroyed their share, the setup was secure. This was a real concern; multiple Zcash upgrades happened partly to progressively strengthen setup security. Halo 2 (Orchard) eliminated the need entirely — a major cryptographic milestone.

Compliance and Exchange Support

Zcash's optional privacy has made it more exchange-friendly than Monero. Major exchanges (Coinbase, Binance in many jurisdictions, others) support ZEC. Exchanges often restrict withdrawals to t-addresses (transparent), keeping their books clean. Users can shield after withdrawing. This compromise has kept ZEC broadly available while maintaining the shielded pool for privacy-conscious users. Regulatory pressure on ZEC has been less intense than on Monero, though not zero.

The Anonymity Set Problem

Zcash's shielded pool has historically been smaller than expected — much of ZEC circulation is in transparent addresses. Smaller shielded pool = smaller anonymity set = weaker privacy. This is a network-effect problem: users want privacy but only shield if others shield too. Recent improvements have addressed this via wallet defaults and UX. Shielded pool activity has grown substantially but still lags Monero's per-transaction anonymity set.

Key Takeaways

  • Users transparently deposit → shield → transact privately → transparently withdraw
  • Trusted setup was a real concern; Halo 2 in Orchard eliminated it
  • Exchange support is broader than Monero due to optional privacy
  • Shielded pool anonymity is limited by pool size — historically smaller than Monero's

Under the hood

Halo 2 and Recursive Proofs

Halo 2 (developed by Electric Coin Company, Zcash's foundation) is a zero-knowledge proof system without trusted setup. It uses a technique called 'inner product arguments' to construct proofs recursively. Recursive proofs — proofs that verify other proofs — enable dramatic scalability. Halo 2 has influenced substantial ZK research beyond Zcash; several ZK rollups use Halo 2 derivatives. The Zcash team's cryptography contributions extend well beyond Zcash's specific use.

ECC vs Zcash Foundation

Zcash's development is split across two organisations. Electric Coin Company (ECC): the original founders, focused on protocol development and Halo 2 research. Zcash Foundation: nonprofit focused on infrastructure, wallets, and community. Historically, some ZEC token issuance flowed to these organisations (founders reward, structured to sunset over time). The organisational structure creates governance complexity — decisions about protocol direction, funding, and community priorities require coordination. Multiple protocol upgrades have been contentious.

The Zcash Roadmap

Zcash's ongoing roadmap includes shielded pool usability improvements, wallet standardisation, and continued cryptographic evolution. Whether ZEC accrues meaningful long-term adoption depends on how well the shielded pool grows and how well the ecosystem executes. The optional-privacy model has both advantages (regulatory tolerance) and disadvantages (smaller anonymity set) vs Monero's mandatory model. Both approaches remain viable, with different tradeoffs.

Zcash and Broader ZK Ecosystem

Zcash's cryptographic work has cascaded through the broader ZK ecosystem. Sapling's cryptography influenced many later designs. Halo 2 is used by ZK rollups (Scroll, Aztec via variants). The Zcash cryptography research team has contributed to numerous non-Zcash projects. Even if Zcash itself doesn't achieve mass adoption, its cryptographic contributions are foundational to the broader ZK ecosystem.

Zcash vs Monero — Different Tradeoffs

Monero's mandatory privacy maximises anonymity set but constrains regulatory compatibility. Zcash's optional privacy maximises regulatory compatibility but produces smaller anonymity sets. Both approaches are defensible. Choose based on your priorities: pure privacy → Monero; broader utility with optional privacy → Zcash. The choice reflects different views on how privacy should be integrated into cryptocurrency ecosystems.

Key Takeaways

  • Halo 2 eliminated trusted setup and enables recursive proofs — landmark cryptography
  • Development split: ECC (protocol) + Zcash Foundation (infrastructure)
  • Shielded pool growth is the long-term adoption question
  • Zcash's cryptography influenced broader ZK ecosystem beyond ZEC itself
  • Monero vs Zcash reflects different views on privacy integration

Related Content

DAO Treasury Management

How major DAOs (Uniswap, MakerDAO, Optimism, Arbitrum) manage multi-billion-dollar treasuries, the conflicts between treasury preservation and value creation, and the patterns emerging in DAO finance.

The Four-Year Crypto Cycle

The empirical history of Bitcoin's roughly four-year boom-bust cycles, the halving-driven structural explanation, and the debate about whether the cycle pattern persists in the institutional era.

Halving Market Behaviour

How Bitcoin price has actually behaved around halvings (2012, 2016, 2020, 2024), the structural reasons behind the patterns, and what is known about the 2028 halving.

Monero Privacy — Deep Dive

How Monero's ring signatures, stealth addresses, and Bulletproof range proofs combine to provide default-on privacy for every transaction, and the regulatory pressures the project faces.

Tornado Cash Mechanics and OFAC Context

How Tornado Cash's Merkle tree deposit-and-mix architecture worked, the August 2022 OFAC sanctions, the 2024 Van Loon ruling and the March 2025 delisting, and the broader question of sanctioning immutable smart contracts.

Aztec and Railway — Ethereum Privacy Layers

How Aztec's zkRollup and the RAILGUN shielded pool (used through the Railway wallet) approach privacy on Ethereum from different architectural angles, and what shipping ZK-based Ethereum privacy actually looks like.

Lightning Network — Deep Dive

How Lightning's payment channels enable instant Bitcoin transactions, the routing challenges that shape the network's topology, and why LN adoption has grown more slowly than early forecasts suggested.

Liquid Network

How Liquid is a Bitcoin sidechain with faster settlement, confidential transactions, and asset issuance — and where it fits in the Bitcoin scaling ecosystem alongside Lightning.

References & further reading