Tornado.cash: DNS and Hosting as the Enforcement Layer

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

Tornado.cash is often described as a test of whether decentralized software can be regulated, but the record shows something narrower and more instructive. Enforcement landed almost entirely on layers operated by identifiable companies, and it did not land on the layer where the code runs. That split is not unique to this case; it is the ordinary shape of internet enforcement, made unusually visible.

Which layers could enforcement actually reach?

Enforcement reached every layer with an accountable operator: the registrar holding the naming record, the provider hosting the public interface, the platform storing the source repository, and the exchanges and banks sitting at the boundary between chains and the banking system. Each of those is a company with an address, a compliance function and a license or reputation to protect.

The naming layer is the most easily addressed of the four. A registrar maintains a contract with whoever holds a name and can suspend or transfer it under its own policies or on legal instruction, and a registry operator sits above it with authority over the entire suffix. Neither party touches the software a name points at.

Hosting works the same way one step down. Files a browser renders live on machines rented from a provider that holds billing records, terms of service and a simple ability to stop serving them. When an interface goes dark, the mechanism is nearly always an account decision at a hosting company.

The financial edge is where the most durable effect sits. Exchanges and payment firms operate under licensing regimes requiring risk-based anti-money-laundering programs, and those programs classify funds by transaction history. A firm flagging mixer-associated deposits is applying its own risk model rather than enforcing a list, which is why the behavior persists through changes in legal status.

Why is the intermediary the standard point of leverage?

Because intermediaries are the only participants in the internet stack that reliably combine three properties: they are identifiable, they are located in a jurisdiction, and they hold a switch. A regulator seeking a practical result will act where all three coincide, which is almost never where the software itself sits.

This pattern long predates cryptocurrency. Copyright enforcement runs through hosts and search engines rather than through individual file transfers, gambling restrictions run through payment processors, and content rules run through platforms. In each case the legal system reaches a corporation that can be summoned, fined or licensed, and that corporation’s compliance decision then affects a very large number of end users at once.

The economics reinforce the choice. Pursuing individual users is slow and jurisdictionally messy, while one instruction to an intermediary produces a broad effect at almost no cost. Intermediaries also tend to over-comply, because losing a customer costs less than appearing to have facilitated a violation.

What sat outside the reach of those controls?

The deployed pool contracts sat outside it. They are Ethereum smart contracts published without an owner, without a pause function and without an upgrade path, replicated across every node validating the chain. There is no account to suspend, no company to instruct and no administrative key, so no intermediary exists at that layer to be leveraged.

This is a property of how the contracts were written rather than a philosophical claim. A contract can be deployed with an administrator address, a proxy allowing the logic to be replaced, or a halt function, and many are. When those are absent the bytecode is fixed, and every node reaches the same result independently.

A federal appeals court eventually treated that fact as legally decisive. In November 2024, in Van Loon v. Department of the Treasury, the Fifth Circuit held that the immutable contracts were not property under the governing statute and so could not be designated, reasoning that property implies something capable of being owned, excluded from or disposed of. The ruling was about the limits of sanctions authority, not about whether any conduct was lawful.

How can you find the primary record behind an enforcement action?

You find it by identifying the body that issued the measure, locating the notice or docket entry itself, reading the scope language closely, separating the order from voluntary corporate responses, and recording the citation with the date you read it. This is a research method for checking claims, not a procedure involving any service.

Step 1: Identify the body that issued the measure

Establish which specific agency, court or private company actually took the step, because a report will often describe an action in the passive voice without naming the actor. A sentence saying something was blocked conceals whether a government, a registrar or a hosting provider made the decision.

Step 2: Locate the notice or docket entry itself

Find the underlying document, such as an agency action notice, a published rule or a numbered court filing, since that document is the record and everything else is commentary on it. Most enforcement bodies publish these routinely and they are usually short.

Step 3: Read the scope language closely

Read the part of the document that states what it covers and what it does not, because scope is where an action usually turns out to be narrower than the reporting suggested. Scope also tells you which named objects are affected and which merely share a brand.

Step 4: Separate the order from voluntary responses

Distinguish what the document itself required from what companies chose to do afterward, since intermediaries frequently go further than any order compelled them to go. Conflating the two produces an inflated picture of what the state actually did.

Step 5: Record the citation and the date you read it

Save the document reference and note the date you consulted it, because enforcement positions are revised and a later reader needs to know which version you relied on. A dated citation is also what allows someone else to reproduce your conclusion.

Enforcement points and their practical limits

Different layers give an enforcing party different amounts of leverage, and each comes with a characteristic limit. The table summarizes the four reachable layers and the one that was not, in general terms rather than as a description of any current arrangement.

Layer	What action there achieves	Characteristic limit
Registrar and registry	The familiar name stops resolving to a destination	A different name or a direct address still reaches the same software
Hosting provider	A public interface stops being served to browsers	Interface code is small and can be served from anywhere else
Repository platform	The canonical copy of source code becomes unavailable	Copies and forks already exist outside the platform’s control
Exchange or bank	Funds with a given history face restriction at the boundary	Applies only where regulated firms sit in the payment path
Deployed contract	No action is available at this layer	No owner, no pause function and no upgrade path exist

Reading across the rows shows why this case produced such contradictory summaries. Every reachable layer yielded a visible result, and none of those results touched the row at the bottom, so reports emphasizing either half were describing something real.

What does this pattern suggest about future actions?

It suggests that pressure moves toward the layers that remain reachable, and that the human layer is the most reachable of all. Where software cannot be switched off, attention shifts to the people who wrote, funded, promoted or operated services around it, and to the regulated firms that touch the resulting funds.

That shift is visible in the record. The August 2022 designation notice named contract addresses, and by November 2024 a court had held that the immutable ones could not be designated at all. Treasury removed the name from the sanctions list in March 2025, so it is not currently designated, while criminal proceedings against individuals continued on their own footing.

Those proceedings show the human layer clearly. Alexey Pertsev was convicted in the Netherlands in May 2024 and sentenced to 64 months, then conditionally released in February 2025 to prepare an appeal that remains pending. In August 2025 a jury convicted Roman Storm on one count of conspiracy to operate an unlicensed money transmitting business and deadlocked on two others, and a retrial is scheduled for April 26, 2027 before Judge Katherine Polk Failla in the Southern District of New York.

For a reader assessing risk, layer matters more than headline. A measure aimed at a registrar says little about legal exposure, one aimed at an exchange describes compliance friction, and a criminal proceeding concerns individual liability. Only a qualified adviser can map those onto a specific situation.

Frequently asked questions

Can an intermediary restrict something without any legal order?

Yes. Registrars, hosts and platforms all operate under contracts and acceptable-use policies that permit them to suspend an account on their own assessment of risk. A great deal of what readers interpret as government action is a private company applying its own terms.

Does a restriction in one country block access from every other country?

Not necessarily. Some layers, such as a registry record for a global suffix, have worldwide effect, while others are applied per jurisdiction or per provider. The practical reach of a measure depends on which layer it touched and how centrally that layer is operated.

Is an action against an intermediary the same as a criminal charge?

No. An administrative or contractual restriction changes what a service will carry, while a criminal charge alleges that a person committed an offense and must be proved to a court. The two proceed on separate tracks and neither determines the outcome of the other.

What happens to funds an exchange has already restricted?

That depends on the legal basis the exchange acted under and on its own policies, and it is not resolved automatically by a later change in status. Anyone in that position should raise the specific facts with qualified counsel rather than assume a general rule applies.