Since 21 March 2025, Tornado Cash is no longer under U.S. Treasury economic sanctions, but that change does not make every transaction lawful or every withdrawal safe. The protocol’s smart contracts remain on Ethereum, while users still face wallet, exchange, compliance, and jurisdiction risks. The practical answer depends on what changed: the sanctions designation changed; the underlying privacy mechanism and its exposure to scrutiny did not.
Is Tornadocash usable after the sanctions changed?
Technically, the protocol can still operate because its core contracts are deployed on a public blockchain and are designed to be non-custodial. A user deposits assets into a pool, receives a private note, and later uses that note to withdraw to another address. The protocol documentation explains that custody remains with the user during the process, while a relayer can submit the withdrawal transaction and pay its gas.
That is why the answer is not simply “yes” or “no.” The U.S. Treasury announced the removal of economic sanctions against Tornado Cash on 21 March 2025, but also said it remained concerned about transactions that could benefit North Korean cyber actors and advised U.S. persons to exercise caution. Read the Treasury delisting announcement as a change in sanctions status, not as a universal approval of future use.
For a person evaluating the service today, the important distinction is between protocol availability and usable privacy. The contracts may accept deposits and process withdrawals, yet an exchange, wallet provider, analytics company, or compliance team may still treat funds connected with a mixer as high-risk. The transaction can succeed on-chain and still create an off-chain problem later.
What the privacy mechanism does—and does not—hide
The system breaks the obvious address-to-address trail by combining deposits in a shared pool and allowing a later withdrawal to a different address. It does not erase the blockchain. Deposit and withdrawal transactions remain public, and outside observers can study timing, amounts, address reuse, relayer behavior, and surrounding activity.
Its main cryptographic tool is a zero-knowledge proof, meaning a method for proving that a statement is valid without revealing the underlying information. In this case, the withdrawal proof can show that the user knows a valid deposit secret and that the deposit has not already been withdrawn, without identifying which deposit belongs to that withdrawal.
That privacy is conditional. A fresh receiving address helps, but reusing an address, withdrawing immediately, funding the destination from a known wallet, or later sending the assets to a regulated exchange can reconnect parts of the trail. Privacy is therefore a probability and process problem, not a magic switch.
Which option fits the reason you need privacy?
| Option | Privacy model | Main trade-off | Best fit |
|---|---|---|---|
| Tornado Cash | Fixed-amount pool with separate withdrawal address | High compliance scrutiny and limited room for mistakes | Experienced users who understand on-chain and off-chain exposure |
| Privacy Pools | Privacy pools designed around selective compliance concepts | Different liquidity, tooling, and adoption profile | Users who want privacy with stronger screening possibilities |
| Railgun | Shielded on-chain activity using zero-knowledge cryptography | More complex wallet and application workflow | Users who need privacy while interacting with supported DeFi activity |
| Stealth addresses | New receiving address for individual payments | Does not hide the full history of the sender or later spending | People receiving private payments rather than breaking a transaction link |
Ethereum’s current privacy overview lists mixers, shielded pools, and stealth-address systems as separate approaches. That distinction matters: a mixer is built around separating a deposit from a later withdrawal, while a shielded pool can maintain private balances and transfers inside the system. The right choice follows the privacy problem, not the brand name.
What should a cautious user check before interacting?
- Jurisdiction: Confirm the rules that apply where the user is located. The end of one U.S. sanctions designation does not settle laws in another country, and it does not override anti-money-laundering or proceeds-of-crime rules.
- Source of funds: Keep records showing where the assets came from and why they are being moved. A private transaction is not the same thing as an unexplainable transaction.
- Counterparty policy: Check whether the destination exchange, custodian, lender, or payment provider accepts assets with mixer exposure. Their internal screening may be stricter than the law.
- Operational risk: Treat the deposit note like a private key. Losing it can mean losing access; exposing it can let someone else withdraw the funds.
- Privacy limits: Assume that timing, amounts, address reuse, and later identity-linked activity can weaken the separation.
So what is the honest bottom line?
The protocol is technically available, and its U.S. sanctions status changed in 2025. That does not mean it is a frictionless privacy wallet, a guarantee of anonymity, or a clean route into every exchange. It remains a specialized tool whose usefulness depends on careful operational choices, local law, and the policies of the services that will eventually handle the assets.
For someone who only wants to stop a public wallet address from being associated with everyday payments, stealth addresses or a shielded system may be easier to explain and manage. For someone considering the original pool-based design, the decisive question is whether they understand both sides of the transaction: what the cryptography obscures and what the surrounding blockchain activity can still reveal.