| Paper | Tornado Cash Privacy Solution |
|---|---|
| Version and date | Version 1.4, December 17, 2019 |
| Authors | Alexey Pertsev, Roman Semenov, and Roman Storm |
| Network in the paper | Ethereum and Ether (ETH) |
| License | Not stated in the original paper |
| Original document | Readable copy of the original v1.4 PDF, hosted by Berkeley DeFi |
Tornado Cash Privacy Solution is a short 2019 design paper for reducing the on-chain link between an Ether deposit and a later withdrawal. It combines a fixed-value pool, a secret withdrawal note, a Merkle tree, and a zk-SNARK proof. The idea is to let a smart contract verify that a withdrawal belongs to some valid, unspent deposit without showing which deposit it came from. The paper describes a privacy mechanism; it does not make every part of an Ethereum transaction private or guarantee that outside observers cannot infer a link.
| Original paper | Original paper |
|---|---|
| Directories | Ethereum Whitepapers & Research |
What the 2019 paper describes
Version 1.4 is dated December 17, 2019 and lists Alexey Pertsev, Roman Semenov, and Roman Storm as authors. Its stated model is an Ethereum smart contract that accepts a fixed amount of Ether, recorded as a commitment, and later releases the corresponding amount to a recipient. The paper says ERC-20 support was a future extension; later deployments and variants should not be read back into this specific document. In particular, the project documentation distinguishes the classic fixed-amount pools from Tornado Cash Nova, which uses a different account-based design.
How a deposit can be withdrawn without naming it
- Create a private note. The depositor generates secret values and submits a cryptographic commitment with a fixed amount of ETH. The contract adds that commitment as a leaf in its Merkle tree.
- Keep the withdrawal secret. The depositor must retain the note. It is the information used to prove control of the deposit later; losing it can make the funds unrecoverable.
- Prove membership. At withdrawal, the user creates a zero-knowledge proof that a valid commitment is in the tree and that its nullifier has not been used. The proof lets the contract check the claim without publishing the secret or the deposit’s position in the tree.
- Pay the recipient once. The contract verifies the proof, marks the nullifier as spent, and transfers the fixed amount minus any relayer fee to the chosen recipient. This one-time nullifier check prevents the same note from being withdrawn twice.
The contract and its transactions remain public. What the proof hides is the direct deposit-to-withdrawal correspondence encoded by the private note. The paper itself cautions that user behavior can make some possible deposits more likely than others. A small pool, a prompt withdrawal, a reused address, a distinctive transaction pattern, or information exposed outside the chain can narrow the plausible matches. Privacy is therefore a property of the proof and the surrounding behavior, not a promise that a transaction becomes invisible.
Fixed amounts, relayers, and trade-offs
The paper uses a fixed amount, written as N ETH, so the amount alone does not distinguish one deposit from another in that pool. The group of deposits that could plausibly correspond to a withdrawal is often called an anonymity set. More eligible deposits can make simple matching harder, but the count does not capture every timing, address, or off-chain clue.
The paper gives two withdrawal paths. A recipient can submit the transaction and pay Ethereum gas, or a smart contract can be called through a relayer: the relayer submits the withdrawal and receives a fee, while the chosen recipient receives the remainder. A relayer can keep the recipient from having to fund the withdrawal directly from the visible deposit address, but it adds a service dependency and a fee. It does not conceal the public withdrawal transaction, erase outside records, or guarantee privacy if addresses and behavior are linked by other clues.
Users also take on operational risk. The note must be stored safely; smart-contract, cryptographic, wallet, and user-interface risks remain. A contract can be non-custodial in the sense that the operator does not hold a user’s note or control a normal account balance, while still being exposed to software and implementation failures. The paper’s security claims are the authors’ design claims, not a substitute for independent review of a specific deployed contract or a guarantee about its current status.
Regulatory timeline: date the claim
Regulatory descriptions need a date. On August 8, 2022, the U.S. Treasury announced an OFAC designation of Tornado Cash and stated its reasons and allegations in that release. On March 21, 2025, Treasury published a separate notice saying it had removed the economic sanctions against Tornado Cash. These are dated U.S. government actions; the 2022 announcement should not be presented as the current status by itself. The later notice should not be read as a blanket ruling on every transaction, every individual case, or the laws of other countries. This page does not determine whether a particular use is lawful.
Social Media Sentiment
A very small, non-representative Reddit sample shows two recurring themes rather than a consensus. In an April 16, 2026 r/ethereum discussion, some commenters described permissionless transaction privacy as useful and worried that legal uncertainty could discourage privacy tools; others questioned permissioned alternatives and how practical privacy can be. In a separate r/defi thread posted May 2, 2026, users asked what people were using after sanctions, while later comments in September still asked for the official URL. That thread suggests some confusion about the dated sanctions timeline and where to find the project. These posts are anecdotes from a few users, not a measure of broader public opinion.
Last updated: 2026-10
Related Terms
See Also
- Ethereum: A Next-Generation Smart Contract and Decentralized Application Platform
- Zerocash: Decentralized Anonymous Payments from Bitcoin
- Halo 2: Zcash’s PLONKish Proof System
Sources
- Pertsev, A., Semenov, R., and Storm, R. (2019). Tornado Cash Privacy Solution, version 1.4. Readable copy of the original paper hosted by Berkeley DeFi. The original tornado.cash download host did not resolve during this review.
- Tornado Cash documentation, How Does Tornado Cash Work?
- U.S. Department of the Treasury, August 8, 2022 designation announcement.
- U.S. Department of the Treasury, March 21, 2025 delisting announcement.
- Reddit, r/ethereum daily discussion, April 16, 2026.
- Reddit, r/defi discussion, May 2, 2026, with later comments through September.