What is a shielded pool?
A shielded pool holds funds as private notes inside a smart contract. Deposits and withdrawals are public, but what happens inside is proved with zero-knowledge proofs and does not reveal who owns what.
Also called privacy pool.
Explain it like I’m five
A big hall holds thousands of identical sealed boxes, and a guard stands at the door. Anyone can drop coins into a fresh box at the door while everyone watches. Inside the hall nobody can tell whose box is whose. To take coins out, you prove to the guard that you own one of the boxes without saying which, and you cross its secret number off a public list so that the same box cannot be emptied twice. The guard also checks that the hall never pays out more than was put in.
What problem it solves
A public blockchain shows every payment, so anyone can follow a payment back to a person. A shielded pool keeps value in one place where individual ownership is hidden. Coins enter and leave in public, and between those two points nobody can tell which deposit paid for which withdrawal.
How it works, step by step
- A deposit turns public coins into a note, a record of an amount and an owner. Only a commitment to the note goes on the chain (shielding).
- The commitments go into a Merkle tree, so the pool can show that a note exists without listing it.
- To spend, the owner makes a zero-knowledge proof that the note is in the tree, that they hold its key and that the amounts add up.
- A signature made with a re-randomized key authorizes the spend, so that the key shown on the chain cannot be linked to the owner’s address (Zcash).
- The spend publishes the note’s nullifier, and the chain refuses any nullifier it has seen before.
- New notes for the recipient and for any change are created with fresh commitments, and amounts and recipients stay hidden inside the pool.
- A withdrawal turns a note back into public coins (unshielding).
- The pool’s balance is checked in public. Zcash’s rules reject any block that would make a shielded pool’s balance negative.
A worked example
Ten people deposit one coin each during a day, and later a withdrawal of one coin appears. The chain shows ten deposits and one withdrawal, and nothing links the withdrawal to a particular deposit, so a guess is right one time in ten. If a deposit of 1,234 coins is followed an hour later by a withdrawal of exactly 1,234 coins, the amounts and the timing point at each other, and the crowd shrinks to one. Zerocash, the design behind Zcash, makes transactions of under 1 kilobyte that verify in under 6 milliseconds.
What it guarantees
- The deposit and withdrawal addresses, the amounts and the times are public. Zcash’s specification notes that moving value between pools always reveals the amount.
- Which note a withdrawal spends, who owns the notes and, in a fully shielded transfer, the amounts and recipients stay hidden.
- The set of notes a spend could have come from is large. In Zcash, the traceability set includes all earlier notes that the adversary does not control or know to have been spent.
- Double spends and overdrafts are ruled out by design. Each nullifier works once, and the pool balance can never go below zero. Nodes can track how much value has entered and left each pool, so the total in a pool is public even though the notes are hidden.
- An owner can still show a history on purpose. Zcash lets an owner share a full viewing key, which recognizes incoming and outgoing notes without any power to spend.
Common misunderstandings
- Not everything is hidden. The edges are public, and an observer still sees coins go in and come out.
- Cryptography alone does not make the privacy. The crowd, the timing and the amounts matter as much.
- A shielded pool leaves room for accountability. Privacy Pools lets a user prove that a deposit belongs to a set that an association set provider has approved, without saying which deposit it is.
- No person holds the coins. The pool’s rules, enforced by a contract or by consensus, are what hold them.
Where it is used
Zcash runs shielded pools, among them the Sprout, Sapling and Orchard pools. The ethereum.org documentation lists Tornado Cash on Ethereum, and Privacy Pools adds approved sets of deposits on top of the same idea.
History
Zerocoin hid only where a payment came from. Zerocash (2014) hid the amount and the recipient too, and Zcash launched on that design in 2016. Its pools have moved to newer proof systems since, with Sprout on BCTV14, Sapling on Groth16 and Orchard on Halo 2.
In Redacted
Redacted’s version is the Reserve, a shared space where every user’s deposits live together as notes that look alike from the outside. Instead of only withdrawing, you act from it through a Spending account and trade, swap, stake, lend and borrow on Rujira. The Reserve contract’s own books always balance, because it continuously accounts for what it owes against what it holds in each asset.
Reserve and Spending →Related terms
Sources: Zcash Protocol Specification · ZIP 209, Zcash Improvement Proposals · Zerocash: Decentralized Anonymous Payments from Bitcoin, Ben-Sasson et al., 2014 · Zero-knowledge proofs, ethereum.org · What is Privacy Pools?, Privacy Pools Documentation
Updated November 1, 2026. All terms