Coinbase Tornado Cash: What the Ruling Changed for AML

Prepared by the editorial team. Updated August 31, 2026.

Coinbase Tornado Cash is a connection that runs through litigation rather than commerce, because the exchange funded the challenge decided as Van Loon v. Department of the Treasury in November 2024 and had no operational relationship with the service. Compliance teams reading that decision drew a far narrower conclusion than the coverage did. This article explains why a limit on one sanctions mechanism left anti-money-laundering obligations exactly where they were.

What did the decision actually change for a compliance team?

Very little in day to day terms. It established that a particular category of immutable smart contracts is not property the sanctions statute allows the government to block, which constrains what can be designated in future. It did not alter customer due diligence, transaction monitoring, reporting duties or any licensing requirement.

The reason is that these obligations sit in different statutes. Sanctions law tells a firm which parties it must not deal with and whose property it must freeze. Anti-money-laundering law tells a firm how it must know its customers, monitor their activity and report what looks suspicious. A court reading the first says nothing about the second, however dramatic the headline.

There was a practical consequence at the margin. Firms that had built controls around the listed addresses had to work out what to do when the listing was later removed, and that is a change to a screening list rather than to a policy. The underlying question of how to treat funds with mixer history was untouched, because it was never a list question.

The clearest evidence for this reading is what did not happen afterwards. Regulated venues continued to treat mixer exposure as elevated risk through the delisting and beyond, because the risk assessments driving that treatment do not have a citation to the sanctions list in them.

Why do anti-money-laundering duties survive a sanctions loss?

Because they come from separate legislation with a different logic. Sanctions law is list-driven and prohibitory: it names parties and forbids dealings. Anti-money-laundering law is risk-driven and procedural: it requires a firm to assess, monitor, record and report, whatever any list happens to say on a given day.

The distinction shows up in what each regime asks. A sanctions question is closed: is this counterparty listed, yes or no. An anti-money-laundering question is open: how likely is it that this value has an illicit origin, what does the firm know about the customer, and does the pattern warrant a report. The second question does not become easier when a name leaves a list, because it was never asked about the list.

The two also have different failure modes. Dealing with a designated party is a strict liability problem, while an anti-money-laundering failure is usually judged on whether the programme was reasonable and whether the firm followed it. Supervisors examine process, documentation and consistency, none of which is affected by a ruling about the definition of blockable property.

Criminal law forms a third, independent layer. Statutes on money laundering, unlicensed money transmission and sanctions evasion operate on conduct rather than on status, and a decision limiting an agency’s designation power does not amend any of them.

Why did practitioners read the outcome more narrowly than headlines?

Because they read the holding rather than the summary. The court answered a definitional question about a statutory term and expressly did not address whether any conduct was lawful. To a compliance reader, an opinion that leaves the conduct question open changes almost nothing about how to handle a deposit tomorrow morning.

Coverage compresses in a predictable direction. A court telling a government agency it went beyond its statute is naturally reported as a defeat for the agency, and a defeat for the agency is easily rendered as a victory for the thing the agency acted against. Each step is a small stretch, and by the end the story has become a claim about legality that the opinion never made.

Practitioners also work with a longer time horizon than a news cycle. The relevant question in a compliance function is what a supervisor or a prosecutor will make of a decision two years from now, and a narrow definitional holding is a thin foundation for relaxing anything. The safer reading is also the accurate one here, which is unusual and worth noting.

Subsequent events supported the cautious reading. Treasury removed the name from the list in March 2025, and the official notice of that delisting is an administrative record of a status change rather than any statement about risk, while the criminal proceedings in New York carried on entirely unaffected.

How can you test whether a legal development changes your obligations?

You write down the source of the obligation, identify what the development actually operated on, check whether the two intersect, establish the reach and finality of the change, and put the conclusion to qualified counsel with a dated record. The method is a research discipline and does not replace advice on your own position.

Step 1: Write down the source of the obligation

State in one line which statute, regulation or supervisory expectation creates the duty you are asking about, because an obligation with no identified source cannot be tested against anything. A surprising number of internal rules turn out to rest on habit rather than on a citation.

Step 2: Identify what the development operated on

Read the primary document to establish exactly which power, list entry or provision the decision or action addressed, rather than relying on the subject line of a news alert. Opinions and agency notices are usually explicit about their own scope in a way that summaries are not.

Step 3: Check whether the two actually intersect

Compare the source of your duty with the provision the development touched and ask whether they are the same body of law, because most developments that feel relevant turn out to sit in a different statute. When the answer is no, the analysis is finished and the finding is that nothing changed.

Step 4: Check the reach and the finality of the change

Establish which jurisdictions the change binds and whether it is subject to further review, since a decision under appeal or limited to one circuit is a weaker foundation than a settled one. The same test applies to agency actions, which can be revisited later.

Step 5: Put the conclusion to counsel and record it

Ask qualified counsel to confirm the analysis and file the answer with the date and the documents relied on, because a compliance decision is judged later on the reasoning available at the time. The file is what turns a defensible judgment into a demonstrable one.

Does a narrow ruling ever change compliance practice?

Sometimes, but through a slower route. A holding that defines the outer edge of a power affects what the agency does next, and agency behaviour is what compliance functions actually respond to. The change arrives as a shift in how future designations are drafted rather than as an instruction to firms.

The likely practical effect here is on targeting. If autonomous, unownable code cannot be listed, then future actions aimed at similar activity have to reach people, companies, front-end operators or intermediaries instead. Those are all things a regulated firm already screens for, so the shift is one of emphasis rather than a new control.

There is also a documentation effect. A decision that draws a line between contracts that have a controller and contracts that do not gives compliance teams a vocabulary for describing why two superficially similar protocols are treated differently, which is useful when explaining a risk assessment to a supervisor or a banking partner.

Where each obligation comes from

Sorting duties by their legal source makes it obvious why one court decision touched so little. The table lists the main obligations a regulated venue carries and where each originates, as an orientation rather than a compliance checklist.

Obligation	Source of the duty	Touched by the decision
Blocking property of a designated party	Sanctions statutes and the SDN list	Yes, as to contracts held not to be property
Screening counterparties against sanctions lists	The same sanctions regime	No, the duty and the lists remain
Customer identification and due diligence	Anti-money-laundering legislation	No
Monitoring and suspicious activity reporting	AML legislation and supervisory rules	No
Money transmission licensing and registration	Federal and state money services law	No, and separately contested in the criminal case

Only the first row moved, and it moved for one narrow category of object. Everything a compliance function does on an ordinary day sits in the rows below it, which is the whole explanation for why the reaction inside firms was so much quieter than the reaction outside them.

Frequently asked questions

Did the decision affect obligations outside the United States?

No. A United States federal court interprets United States law, and other countries maintain their own sanctions regimes and money laundering rules. A firm operating elsewhere has to read its own national requirements, which may reach conduct the American position does not.

Was the criminal case in New York affected by the outcome?

It continued. A jury convicted Roman Storm in August 2025 on one count of conspiracy to operate an unlicensed money transmitting business and deadlocked on two further counts. A motion for acquittal argued in April 2026 remains undecided, and a retrial is scheduled for April 26, 2027.

Should an internal policy be relaxed once a name is delisted?

That is a judgment for the firm and its advisers rather than an automatic consequence. A delisting removes one prohibition, and a firm remains free to keep a stricter internal position, provided the reasoning is documented so the choice can be explained to a supervisor later.

Why do some summaries say sanctions on mixers were struck down?

Because a narrow holding compresses badly. The court addressed whether particular immutable contracts fit a statutory definition, not whether mixing services can be sanctioned at all, and designations of people and companies connected to such services were unaffected by the reasoning.