Zcash guide — optional privacy, with real caveats

Zcash can make payments strongly private, and lets you selectively reveal them with a viewing key, but that privacy is optional. This guide compares it honestly with Monero.

Zcash guide — optional privacy, with real caveats

Zcash guide

Zcash can make payments strongly private, and lets you selectively reveal them with a viewing key, but that privacy is optional. This guide compares it honestly with Monero.

Who this guide is for. For readers who know the Monero guide and are wondering whether Zcash (ZEC) is an alternative — for example broader exchange availability, or wanting to selectively prove a transaction later. Not a guide for readers who just want to pay privately without thinking about it — Monero’s privacy-by-default is simpler for that.

What you gain, and what it costs

You gain the ability to make transactions strongly private (amount, sender, and recipient hidden) and, separately, the ability to selectively lift that privacy for whoever you choose via a “viewing key”. Monero has a view key too, but it shows only incoming payments; a Zcash full viewing key also shows outgoing ones. Zcash is also still listed on large exchanges such as Kraken and Coinbase, where Monero isn’t available in the EU.

The cost is that privacy on Zcash is optional, not the default. Fully public (transparent) addresses are still widely used — most exchanges, for example, pay out only to one — and how much privacy you actually get depends on which address type you use and which wallet you choose. On top of that, the protocol had a serious, years-undetected bug in 2026 in exactly the component that makes privacy possible — see the caveat further down.

When this is overkill

If you just want to pay for something online without hassle, a debit card, cash, or a privacy-friendly prepaid route is more practical. And if you mainly want privacy you can’t accidentally “forget” to use, Monero’s privacy-by-default is simpler and more mistake-resistant than Zcash’s opt-in model.


What you should know before reading further

Two things that shape the rest of this guide, and that you shouldn’t stumble across buried in a caveat section at the bottom:

A serious bug in the shielded pool, May–June 2026. Since Orchard (Zcash’s main privacy pool from 2022 until July 2026) activated in May 2022, its underlying cryptographic code contained a flaw — a check that was supposed to guarantee no fake ZEC could be created inside the shielded pool didn’t work as intended. Security researcher Taylor Hornby — at the time working as a paid consultant engaged by Shielded Labs specifically to hunt for this kind of bug — discovered this on May 29, 2026; Orchard transactions (not the older Sapling pool) were suspended from the evening of June 1 for about a day, and ZODL, which developed the fix, reported it complete on June 2, 2026. There’s no confirmed evidence the bug was ever exploited — but Shielded Labs, which had engaged the researcher, judges exploitation unlikely but says it can’t be ruled out with cryptography alone, precisely because shielded transactions are deliberately untraceable by design. That’s not a minor footnote — it’s a direct consequence of how privacy-by-design works, and it belongs stated up front, not buried. As an added precaution, a later upgrade (NU6.3 “Ironwood”, 28 July 2026) closed the old Orchard pool to new deposits and to payments between addresses inside it: funds can only leave it, through a “turnstile” that never lets more ZEC out of Orchard than went in, so any fake ZEC from that period can’t get into circulation. New shielded payments now land in the new Ironwood pool (ZIP 258). There is no deadline, but whatever you send from Orchard crosses the turnstile: amounts passing the turnstile are visible on-chain (see the Zodl review).

An organizational split among the developers. In January 2026, according to ZODL the entire team of Electric Coin Co. (the organization that originally built Zcash) left ECC and formed a new, investor-funded company (ZODL); ZODL says the move let it grow Zcash “without reliance on the Zcash development fund”, and the nonprofit that governs ECC has not published its side that we could find. The team took development of the wallet ECC had built with them — it has since been renamed from “Zashi” to “Zodl.” See the Zodl review for the full background. The relevant point for this guide: Zcash’s development has seen more organizational turbulence over the past year and a half than Monero’s more stable, community-driven model.

Neither point means Zcash is now unsafe or unusable: the flaw was fixed in June 2026, and Ironwood followed in July. But an honest guide starts here, not with the sales pitch.


How Zcash technically handles privacy

Zcash uses zero-knowledge proofs (specifically, zk-SNARKs) — a cryptographic technique that lets you prove something is true without revealing the underlying data. A simple analogy: proving you know a safe’s combination without ever saying the combination out loud. Applied to a transaction: the network can verify a transaction is valid (the sender had the funds, no money was created out of thin air) without the amount, sender, or recipient ever becoming visible.

This system has gone through four shielded pools:

Version Year Trusted setup required? Status
Sprout 2016 Yes Closed; leftover funds can’t be spent since NU7 (2026)
Sapling 2018 Yes Still exists, but not the default
Orchard 2022 (NU5) No Closed to new funds since July 2026
Ironwood 2026 (NU6.3) No (same protocol as Orchard) Current pool

Trusted setup was a real risk in the first two pools: the cryptographic parameters were generated in multi-party ceremonies, in which each participant adds secret randomness and then destroys it. Only if every participant had kept or leaked their part could someone have counterfeited ZEC undetected; one honest participant was enough (Zcash: Sprout ceremony). That made the risk small, but it remained a theoretical weak point Monero has never had. Orchard (2022) removed this problem: it uses a newer proving system (Halo) that requires no trusted setup at all (z.cash: NU5). Ironwood uses the same Orchard protocol, so new shielded payments no longer carry this risk.

Transparent, shielded, and “Unified Addresses” — untangling the address landscape

This is where Zcash gets genuinely confusing for beginners, even in the official documentation:

  • Transparent address (t-address): works like a Bitcoin address — sender, recipient, and amount are all openly visible on the blockchain.
  • Shielded address (z-address): amount, sender, and recipient are encrypted, as long as the payment goes from shielded to shielded. Several technically distinct “pools” exist: Sapling, Orchard (closed to new funds) and Ironwood.
  • Unified Address (UA): the current default format, introduced in 2022. A single address that bundles multiple types behind it (transparent, Sapling, Orchard): the sending wallet must use the newest type it supports, Orchard before Sapling before transparent (ZIP 316). Since NU6.3, a payment to the Orchard part lands in Ironwood. Think of it as a universal travel adapter: you don’t have to pick the type yourself, the technology handles that.

The practical rule of thumb: use a wallet that gives out a shielded address by default and shields incoming transparent funds before you spend them. Zodl does both. The Zodl review covers what this actually looks like in practice.

The “turnstile” — why moving between transparent and shielded leaves a trace

Funds moving from a transparent address to a shielded one (or back) pass through what Zcash itself calls a “turnstile.” The total amount entering and leaving the shielded pool is publicly visible on the blockchain, even though individual shielded balances aren’t. That means: if you buy Zcash on an exchange (transparent) and then shield it, that moment of crossing is itself a point of correlation — and the same applies in reverse if you move shielded ZEC back to a transparent address to sell it. The less often you cross that boundary, the less metadata you leave behind.


Zcash vs Monero — a fair comparison

Monero Zcash
Privacy by default Yes, always, no choice needed Optional — depends on address type and wallet choice
Share of shielded transactions Near 100%, by design Partial: transparent addresses are still common (exchange payouts, for one); the share moves and we found no current primary figure
Ever required trusted setup No, never Yes, for Sprout (2016) and Sapling (2018); no longer since Orchard (2022)
Recent serious bug None comparable that we found in 2026 May 2026: 4-year-old flaw in the shielded-pool code, patched June 2026, exploitation can’t be ruled out with certainty
Selective disclosure (viewing key) View key shows incoming payments only; single payments can be proven Incoming or full viewing key, which also shows outgoing payments: useful for readers who sometimes need to prove where funds came from
Availability on EU exchanges Heavily restricted — dropped from many major platforms Listed on Kraken and Coinbase (not on Bitvavo), but with an uncertain future (see below)
Mining with ordinary hardware Yes, realistic (RandomX, CPU-friendly) Not realistic: miners use specialized ASIC hardware (Equihash)
Merchant acceptance Limited Even more limited in direct acceptance, with one notable exception: the Flexa integration lets shielded ZEC be spent at stores in the Flexa network (Flexa says thousands of locations)
Development and governance Community-driven, stable Recent split: core team left for a new organization (ZODL) in early 2026

Neither wins across the board. Monero is the simpler, more mistake-resistant choice if financial privacy is your goal and you don’t want exceptions. Zcash is more relevant if you specifically want the combination of “mostly private, but with the ability to prove it on my own terms” — for example, readers who sometimes need to demonstrate to an accountant, counterparty, or regulator that funds are legitimate, without exposing their entire transaction history.


Buying Zcash

Via a KYC exchange

Unlike Monero, Zcash is still listed on some large exchanges: Kraken and Coinbase list ZEC, Bitvavo doesn’t (their public market data, 9 November 2026). Whether you can buy it depends on your country: Kraken’s own list of restrictions excludes ZEC only for clients in Australia (Kraken, updated 4 November 2026); Coinbase has a ZEC market in US dollars but none in euros, and we found no country list from Coinbase for ZEC. So check in your account. Most exchanges pay out only to a transparent address (Coinbase accepts only t- and tex-addresses for ZEC), so that withdrawal is public; shield the funds in your wallet before you spend them (Zodl help).

Peer-to-peer

As with Monero, direct peer-to-peer trading remains the most private route to acquire Zcash without a KYC link, but it requires more caution on your part and is less standardized than an exchange purchase.

Mining

Technically possible (Equihash algorithm), but not realistic for an individual with ordinary hardware. Unlike Monero’s CPU-friendly RandomX, Zcash is mined with specialized ASIC hardware, as Zcash’s own site says.


Using Zcash for payments

Direct merchant acceptance is more limited than Monero’s — don’t expect to simply pay at an ordinary Dutch shop. The one notable exception is the Flexa integration: through the Zodl wallet, you can spend shielded ZEC directly at physical stores in the Flexa network. Flexa’s own site and help pages don’t say which countries those stores are in, so check before you count on it.


Practical privacy — what Zcash doesn’t solve

IP address: Zcash protects the content of a transaction, not your network traffic. A mobile wallet talks to a server, and Zodl’s help warns that without Tor your IP address leaks to that server and can be linked to the amounts you move between pools. Since 3.20.0 (9 November 2026, rolling out) Zodl by default sends its server requests through an OHTTP relay run by Cloudflare or Fastly, so ZODL’s servers don’t see your IP address (the relay does, but not your requests); if you pick a public server, Tor Protection is a setting you turn on yourself.

Exchange linkage still exists. If you buy Zcash on a KYC exchange, that exchange knows you bought ZEC — regardless of what you do with it afterward. Shielding only protects what happens after that point, not the origin itself.

The turnstile boundary (see above). Every crossing between transparent and shielded is itself a visible moment on the blockchain.

Recipient cooperation. As with Monero: if the recipient of a shielded payment reveals their own identity and cooperates with an investigation, they can confirm that you paid them.


Zcash and the law in the EU

The EU’s anti-money-laundering regulation (AMLR, Regulation (EU) 2024/1624 — part of the broader EU AML Package, which aligns with MiCA but is a separate legislative track) prohibits, in Article 79, banks, other financial institutions, and crypto-asset service providers from keeping anonymous accounts from 10 July 2027 onward, including accounts that enable anonymity via “anonymity-enhancing coins.”

The regulation defines that term itself, in Article 2: crypto-assets with built-in features designed to make transfer information anonymous, “systematically or optionally.” That last word is exactly why this matters for Zcash, even though the text names no specific coins: Zcash’s shielding is optional by definition, and the law explicitly covers that case too — not only coins where privacy is mandatory, like Monero. There’s currently no official, definitive list of which coins this covers; in practice that gets filled in by regulators and exchanges, not fixed in advance per ticker.

Important to keep clear: this prohibition targets regulated institutions — banks and crypto-asset service providers (CASPs) — not the technology itself. The regulation’s own explanatory recitals explicitly state the prohibition does not apply to providers of hardware, software, or self-hosted wallets, as long as they don’t themselves have access to or control over those wallets. In other words: this is a restriction on what regulated parties may offer their customers, not a ban on owning, self-custodying, or using privacy-preserving cryptography peer-to-peer. That distinction — targeting the access points rather than banning the underlying technology — is exactly why this kind of regulation rarely stops what it’s aimed at: it makes the regulated route harder, not the underlying capability impossible.

Practically, for now (November 2026): Zcash, unlike Monero, is still listed on some large exchanges. Whether that’s still true after 10 July 2027 depends on how exchanges end up applying “anonymity-enhancing” in practice to a coin with optional privacy — that’s not settled yet. No need for alarm, but worth watching if you’re planning around it long-term.


Conclusion

Zcash isn’t “Monero with a marketing problem,” nor is it an outdated attempt at privacy — it’s a different tradeoff. Orchard’s flaw was fixed in June 2026, Ironwood now keeps any counterfeit ZEC from leaving the old pool, and eliminating trusted setup removed a real historical weak point. Viewing keys that also show outgoing payments go further than Monero’s view key, and broader exchange availability makes it more practical for many readers to actually acquire.

But the honest caveats carry real weight too: privacy is optional rather than default, transparent addresses are still widely used, the recent bug in the shielded-pool code is a genuine trust incident (even without confirmed exploitation), and the development team just went through an organizational split. For readers who want privacy-by-default with no exceptions, the Monero guide remains the simpler, more mistake-resistant route. For readers specifically looking for the combination of mostly-private-with-the-option-to-prove-it, Zcash is a serious option, but not a carefree one.

Next step

Choosing a Zcash wallet

  • Zodl review — the Zcash wallet from the former ECC team (formerly Zashi), including the background on the rename and the organizational split

Comparing with the alternative

Further privacy