Skip to main content

This site is for educational purposes only. Nothing here constitutes financial advice.

Topic 98 of 189

Tornado Cash Mechanics and OFAC Context

How Tornado Cash's Merkle tree deposit-and-mix architecture worked, the August 2022 OFAC sanctions, the 2024 Van Loon ruling and the March 2025 delisting, and the broader question of sanctioning immutable smart contracts.

Beginner
8 min readUpdated October 2026Block Clarity Hub Editorial Team

The basics

What Tornado Cash Did

Tornado Cash was a smart-contract-based privacy protocol on Ethereum. Users deposited fixed denominations (0.1, 1, 10, 100 ETH; various USDC amounts) into the protocol; later, they withdrew the same denomination to a different address, breaking the on-chain link between deposit and withdrawal. Between deposit and withdrawal, the funds mixed with other users' deposits in the same denomination. The privacy came from the anonymity set — many users depositing and withdrawing the same denomination made it hard to link specific deposits to specific withdrawals.

Why the Design Worked

The protocol used a Merkle tree to track deposits. When you deposited, your commitment (hash of a secret) was added to the tree. When you withdrew, you proved you knew a secret that hashed to one of the commitments in the tree — without revealing which commitment. This ZK proof let you withdraw without linking to your specific deposit. The math was elegant. The fixed denominations meant every withdrawal looked identical to every other, maximising the anonymity set.

August 2022 OFAC Sanctions

August 8, 2022: OFAC designated Tornado Cash smart contract addresses as SDN-listed entities. This meant US persons couldn't interact with the contracts under sanctions law. The action was novel — sanctioning a smart contract (immutable code, not a company) was legally unprecedented. Multiple developers were subsequently arrested (Alexey Pertsev in Netherlands, others). The community and legal advocacy pushed back; the 5th Circuit ruled in November 2024 that OFAC exceeded its authority (Van Loon v. Treasury), and on March 21, 2025 the Treasury announced it had removed the economic sanctions against Tornado Cash — so the sanctions on the protocol itself are no longer in effect. Treasury added that it would continue to monitor transactions that may benefit malicious cyber actors or North Korea, and that US persons should exercise caution before engaging in transactions that present such risks. CoinDesk reported in April 2025 that OFAC left developer Roman Semenov on the SDN list, and criminal cases against other developers continued, so the broader legal landscape stays complex.

  • Deposit + delay + withdraw pattern with ZK proof unlinking
  • Fixed denominations maximised anonymity set
  • August 2022 OFAC SDN designation was novel legal step
  • Van Loon ruling (Nov 2024) + Treasury delisting (Mar 2025) removed the protocol sanctions

Key Takeaways

  • Tornado Cash used Merkle tree + ZK proofs to enable private mixing
  • Fixed denominations were critical to anonymity set size
  • August 2022 OFAC action was legally unprecedented
  • Van Loon (2024) + the March 2025 delisting ended the sanctions on the protocol itself

Going deeper

The Sanctions Design Question

OFAC's Tornado Cash designation raised fundamental questions. Can you sanction code? Traditional sanctions target entities that can be compelled — persons, companies, governments. Smart contracts are immutable code that can't be compelled. OFAC's argument: the contracts served as tools for money laundering (allegedly ~$7B including Lazarus Group North Korean funds); designation prevents US persons from using them. Critics' argument: sanctioning code chills legitimate uses (privacy for donations, personal safety) and sets dangerous precedents. The legal debate was substantial.

The Van Loon Ruling

November 2024's Fifth Circuit ruling in Van Loon v. Treasury found that immutable smart contracts don't qualify as 'property' under the sanctions statute — property must be capable of being 'owned' in a legal sense, which requires the possibility of someone possessing or controlling it. Immutable code isn't ownable in that sense. Following the ruling, OFAC delisted Tornado Cash in March 2025 — a landmark reversal that removed the protocol from the sanctions list. But the ruling narrowed rather than eliminated OFAC's authority: non-immutable contracts, developer-controlled contracts, and supporting infrastructure may still face designation, and CoinDesk reported that developer Roman Semenov remained on the SDN list (April 2025). The precedent is important but bounded.

Developer Prosecutions

Beyond sanctions, developers faced criminal prosecution — a track that continued even as the protocol sanctions were lifted. Alexey Pertsev was arrested in the Netherlands (August 2022), convicted of money laundering in May 2024 and sentenced to 64 months; Decrypt reported in August 2026 that he was released to electronic monitoring in February 2025 while appealing. Roman Storm was arrested in the US (August 2023); at his 2025 trial a New York jury convicted him of one count of conspiracy to operate an unlicensed money transmitting business (maximum sentence five years) but deadlocked on conspiracy to commit money laundering and conspiracy to violate US sanctions. Decrypt reported on 26 August 2026 that Judge Katherine Polk Failla had adjourned the retrial on those two counts to April 26, 2027, that his motion for acquittal was still undecided, and that he had not yet been sentenced on the money transmitting count. These prosecutions substantially chilled DeFi privacy-tool development. The message: even code you write can produce criminal liability if others use it for prohibited purposes, and the delisting of the contracts did not end the personal legal exposure of their authors.

The DeFi Chill Effect

Post-Tornado Cash, DeFi developers have become substantially more cautious about privacy-tool development. Many privacy-focused projects paused or wound down. Development moved to more permissive jurisdictions. The Van Loon ruling and the March 2025 delisting of the protocol eased the chilling effect, but developer prosecution risk remains — as Roman Storm's 2025 partial conviction showed. This has real costs — legitimate privacy uses (protecting donations, personal safety, business confidentiality) don't have production infrastructure they might otherwise have.

Key Takeaways

  • Sanctions on immutable code raised novel legal questions
  • Van Loon v. Treasury narrowed OFAC's authority over immutable smart contracts
  • Developers faced criminal prosecution beyond civil sanctions
  • Broader chilling effect on DeFi privacy tool development

Under the hood

Anonymity Set Analysis

Tornado Cash's privacy depended on the anonymity set — how many users could plausibly be the source of any given withdrawal. Chainalysis and other firms developed techniques to reduce effective anonymity: timing analysis, address clustering, wallet fingerprinting, off-chain data correlation. In some cases, especially for large deposits with distinctive characteristics, effective anonymity was substantially less than nominal anonymity set size. This is important context: the protocol provided real privacy but not perfect privacy against sophisticated adversaries.

Compliant Alternatives Post-Tornado

Post-Tornado Cash sanctions, several projects have explored 'compliant privacy' — mixing protocols with disclosure mechanisms allowing legitimate users to prove funds aren't from sanctioned sources. Privacy Pools (proposed by Vitalik Buterin) uses ZK proofs of association with 'good' or 'bad' pools. Users can prove their funds came from compliant pools without revealing which specific deposit. These designs try to preserve privacy for legitimate users while excluding sanctioned funds. Adoption is emerging but faces the same regulatory ambiguity as Tornado.

Broader Regulatory Signals

The Tornado Cash proceedings signal regulators' willingness to pursue crypto privacy tools aggressively. Related actions: multiple mixer prosecutions (Bitcoin Fog, Helix, etc.), FinCEN's October 2023 proposed rule (a Notice of Proposed Rulemaking under its Section 311 authority) that identifies international convertible-virtual-currency mixing as a class of transactions of primary money laundering concern, EU AML directive updates targeting privacy tools. The trend line: privacy is regulatorily disfavoured, especially where used at scale for potentially illicit funds. This shapes the design space for future privacy protocols — 'pure privacy' is regulatorily costly; 'compliant privacy' is less so but adoption is unproven.

The Zero-Knowledge Path Forward

Zero-knowledge proofs enable both pure privacy and compliant privacy. The technology itself isn't the constraint; regulation is. The question isn't 'can we build private crypto' but 'what forms of private crypto can operate in current regulatory environments.' Multiple projects (Namada, Nocturne, various ZK L2s) are exploring different points on the privacy-compliance spectrum. The Tornado Cash case will be studied as a foundational precedent shaping this landscape for years.

Sanctions Status Can Change — Verify the Current List

Tornado Cash was delisted in March 2025, so its contracts are no longer under US sanctions — a reminder that designation status is not static. Treasury's delisting statement still told US persons to exercise caution before engaging in transactions that may benefit malicious cyber actors or North Korea. The episode is a lasting caution: other mixers remain sanctioned, individuals can stay listed even when a protocol is delisted (CoinDesk reported in April 2025 that Tornado developer Roman Semenov remained on the SDN list), and interacting with any currently-designated crypto tool creates real legal exposure (exchange freezes, civil enforcement). Always check a protocol's current OFAC status — not its historical one — before interacting, and seek legal advice where in doubt.

Key Takeaways

  • Effective anonymity was smaller than nominal anonymity set for sophisticated adversaries
  • Compliant privacy designs (Privacy Pools) attempt to bridge privacy and regulation
  • Broader regulatory signals: privacy tools disfavoured, especially at scale
  • ZK technology enables the design space; regulation constrains what's viable
  • Sanctions status changes — TC was delisted March 2025; verify current designations (other mixers/individuals may still be listed)

Related Content

The Four-Year Crypto Cycle

The empirical history of Bitcoin's roughly four-year boom-bust cycles, the halving-driven structural explanation, and the debate about whether the cycle pattern persists in the institutional era.

Halving Market Behaviour

How Bitcoin price has actually behaved around halvings (2012, 2016, 2020, 2024), the structural reasons behind the patterns, and what is known about the 2028 halving.

Monero Privacy — Deep Dive

How Monero's ring signatures, stealth addresses, and Bulletproof range proofs combine to provide default-on privacy for every transaction, and the regulatory pressures the project faces.

Zcash Architecture

How Zcash uses zk-SNARKs to enable optional shielded transactions, why Sapling was the breakthrough that made shielded pool usage practical, and how Halo2 removed the trusted setup.

Aztec and Railway — Ethereum Privacy Layers

How Aztec's zkRollup and the RAILGUN shielded pool (used through the Railway wallet) approach privacy on Ethereum from different architectural angles, and what shipping ZK-based Ethereum privacy actually looks like.

Lightning Network — Deep Dive

How Lightning's payment channels enable instant Bitcoin transactions, the routing challenges that shape the network's topology, and why LN adoption has grown more slowly than early forecasts suggested.

Liquid Network

How Liquid is a Bitcoin sidechain with faster settlement, confidential transactions, and asset issuance — and where it fits in the Bitcoin scaling ecosystem alongside Lightning.

Validium, Plasma, and State Channels

The scaling designs that lost to rollups — Validium (off-chain data), Plasma (mass exit games), and state channels (bilateral off-chain) — and why understanding them helps make sense of current rollup design.

References & further reading