Tornado Cash and the Roman Storm Retrial: What It Means for Crypto Developers

One question hangs over the entire Roman Storm prosecution, and every open-source developer should care about the answer: can you go to prison for writing code that strangers later misuse? A 2025 jury could not agree, which is precisely why this case is so unsettling for the industry.

A mixed verdict, a retrial push, and a court-ordered sanctions delisting have left developer liability genuinely up in the air. The outcome will shape how much legal exposure builders of permissionless tools face.

Key takeaways

• In August 2025, a jury convicted Storm of conspiring to run an unlicensed money-transmitting business but deadlocked on the two more serious counts: money laundering and sanctions-violation conspiracy.
• In March 2026, the Department of Justice asked to retry the deadlocked charges, proposing an October 2026 start.
• A 2024 appeals ruling found that sanctioning Tornado Cash's immutable smart contracts exceeded the government's authority, and the protocol was delisted from the sanctions list in 2025.
• The central issue is developer liability: whether writing and publishing code makes you responsible for others' misuse.
• Nothing is final; post-trial motions, a possible retrial, and an anticipated appeal all remain in play.

What Tornado Cash is and why it is contested

Tornado Cash is a set of smart contracts that mix crypto deposits to obscure the link between sender and receiver, providing transaction privacy on a public blockchain. Privacy advocates see legitimate uses: shielding salaries, donations, and ordinary financial activity from total public visibility. Prosecutors emphasized that it was also used to launder proceeds, including funds tied to sanctioned actors. The tool itself is neutral code; the legal fight is about responsibility for its use.

The mixed verdict and the retrial

After a four-week trial, the August 2025 jury delivered a split decision. It convicted Storm on one count, conspiring to operate an unlicensed money-transmitting business, but it deadlocked on the two heaviest charges: conspiracy to commit money laundering and conspiracy to violate sanctions. A deadlock is not an acquittal, which is why the government can try again.

In March 2026, the DOJ filed to retry the unresolved counts, proposing a start date in early-to-mid October 2026 and estimating a roughly three-week trial. Storm, who remained free on bail, sought a judgment of acquittal, with the two unresolved counts carrying substantial additional sentencing exposure on top of the money-transmitting conviction.

Here is where each charge stands:

Charge	2025 outcome	2026 status
Unlicensed money transmitting	Convicted	Subject to post-trial motions and appeal
Money-laundering conspiracy	Hung jury (deadlocked)	DOJ seeking retrial (Oct 2026 proposed)
Sanctions-violation conspiracy	Hung jury (deadlocked)	DOJ seeking retrial (Oct 2026 proposed)

The sanctions thread

Running alongside the criminal case is the sanctions story. In late 2024, a federal appeals court held that the Treasury's sanctions office had overstepped by sanctioning Tornado Cash's immutable smart contracts, reasoning that those contracts were not "property" because no person controlled them. The protocol was subsequently removed from the sanctions list in 2025, though an individual associated with it remained listed. That ruling matters because it touched the question of whether autonomous, unowned code can be treated like a sanctioned entity at all.

Why developers are watching

The principle at stake is sometimes summarized as "code is speech" and "tools are neutral." If publishing open-source software can expose the author to criminal liability for downstream misuse, developers of privacy tools, wallets, and other permissionless infrastructure face real uncertainty. If it cannot, regulators worry that genuinely illicit activity gains a shield. The case sits at the intersection of those concerns, and its resolution, through the retrial and an anticipated appeal, will inform how builders weigh legal risk.

There is an important nuance that gets lost in the "is code free speech?" framing. The charge Storm was actually convicted of, operating an unlicensed money-transmitting business, is not really about the act of writing software. It is about whether the developers operated a service that moved other people's money. Prosecutors pointed to elements like a user interface, a relayer system, and fee mechanisms as evidence the team ran something more than a static published codebase. That distinction is the crux for the wider developer community: publishing immutable, autonomous contracts and walking away is legally very different from running an ongoing service around them. Where exactly the line falls is what the retrial and appeal may help clarify.

For the open-source world, the worst outcome is not a clear ruling in either direction but prolonged ambiguity. Developers can build around a known rule; they struggle to build around a maybe. A privacy-tool author today has to weigh whether shipping at all could one day be construed as operating a service, and that chilling effect is real regardless of how the specific charges against Storm ultimately resolve. That is why even developers with no connection to Tornado Cash are following every motion in this docket.

This connects to broader privacy debates. The fight over government-issued digital currency and financial surveillance runs parallel; our U.S. CBDC ban explainer covers that policy strand, and the general regulatory direction is captured in our CLARITY Act overview. The illicit-finance side that prosecutors lean on shows up in our reporting on North Korea's Lazarus crypto theft.

What this means for you

If you build or use permissionless software, here is the practical read while the case is unresolved:

• Builders of privacy and DeFi tools: the law is genuinely uncertain right now; document your intent, avoid operating the money-flow yourself, and get real legal advice before launching mixing or transmitting features.
• Users of mixers: the protocol's smart contracts were delisted, but compliance risk on centralized off-ramps remains; do not assume "delisted" means "no scrutiny."
• Open-source contributors generally: the money-transmitting conviction is the part that should worry you most, because it touches operating a service, not just publishing code.
• Everyone: treat the October 2026 retrial and the anticipated appeal as the moments that actually set precedent; nothing is settled yet.

Frequently asked questions

Was Roman Storm found guilty? Partly. In 2025 a jury convicted him of conspiring to operate an unlicensed money-transmitting business but deadlocked on the money-laundering and sanctions-violation conspiracy charges.

Why can the government retry him? A deadlock, or hung jury, is not an acquittal. The DOJ may seek a retrial on the unresolved counts, which it moved to do in March 2026.

Is Tornado Cash still sanctioned? The protocol's smart contracts were delisted in 2025 after a court found the sanctions exceeded statutory authority. An individual associated with the project remained listed separately.

Why does this case matter to ordinary developers? It tests whether writing and publishing open-source code can create criminal liability for how others use it, a question relevant to anyone building permissionless software.

This article is for general information and is not legal advice.