A person searching for a privacy mixer usually needs to know whether an old legal warning still controls the practical decision. The answer depends on three separate things: the protocol’s smart contracts, the website or interface used to reach them, and the exchange or wallet that later screens the funds. A change in government listing status can affect one layer without making the others safe, available, or acceptable everywhere.
Is tornado cash usable again after the delisting?
The short answer is: technically, possibly; operationally, not necessarily; legally, not universally.
On 21 March 2025, the U.S. Treasury announced that Tornado Cash had been removed from OFAC’s Specially Designated Nationals list. The official notice also told U.S. persons to exercise caution around transactions that could benefit malicious cyber actors or North Korea. The Treasury’s delisting announcement is the controlling reference for that specific change.
That distinction matters because a smart contract does not automatically disappear when a government list changes. The contracts may remain deployed on a blockchain, while the familiar frontend, RPC provider, wallet, exchange, or compliance service may impose its own restrictions. A user can therefore encounter a protocol that is technically reachable but practically difficult to fund, use, or exit from.
What the mixer actually changes—and what it cannot hide
The system is designed to break the obvious link between a deposit address and a withdrawal address. In broad terms, a user deposits an asset into a pool, receives a private cryptographic commitment, and later withdraws using a zero-knowledge proof. The public chain can still show deposits and withdrawals; the privacy goal is to make the relationship between a particular pair harder to establish.
It does not erase the blockchain. Timing, denomination, wallet behavior, relayer activity, reused addresses, and later interactions can still create clues. A private withdrawal is not the same as an untraceable one.
For a plain-language explanation of the interface, deposits, withdrawals, and practical failure points, the tornado cash guide is the relevant companion resource. It should be read as an operating explanation, not as a promise that a transaction will pass every compliance screen.
Three routes lead to three different kinds of exposure
| Option | Privacy potential | Main failure point | Best fit |
|---|---|---|---|
| Direct interaction with a deployed mixer contract | Highest protocol-level privacy, subject to usage quality | Blockchain forensics, wallet screening, interface or RPC access | Technically experienced users who understand legal and tracing risk |
| A regulated privacy-preserving service | Usually narrower, with identity and policy controls | Account review, withdrawal limits, jurisdiction rules | Users who need a documented compliance path |
| Ordinary wallet-to-wallet transfer | Low; the transaction graph remains visible | Address linkage and public transaction history | Users prioritizing simplicity and broad acceptance |
The direct contract route fits someone evaluating smart-contract risk, chain analysis, and local law before acting. A regulated service fits someone who values a record of where funds came from and why they moved. A normal transfer fits someone for whom convenience matters more than transaction privacy.
The practical test is what happens after the withdrawal
The most overlooked question is not whether a transaction can be submitted. It is whether the recipient can later use the funds without an unexpected review, delay, freeze, or request for evidence.
Before moving anything, a cautious user should check the destination platform’s current policy, preserve transaction records, avoid sending funds directly to a service that may reject privacy-linked assets, and understand whether the relevant jurisdiction treats privacy tools differently from illicit source funds. No interface can guarantee acceptance by a bank, exchange, tax authority, or investigator.
So the delisting changes one important U.S. sanctions-list fact. It does not turn privacy into anonymity, remove blockchain evidence, bind private companies, or answer the user’s local legal question. The sound decision is the route whose remaining exposure the user can explain and accept.