DOJ seeks October retrial of Tornado Cash dev Roman Storm over $1B laundering, sanctions charges

Key Point

According to a court filing, US Attorney Jay Clayton has told the court that prosecutors are prepared to retry Tornado Cash developer Roman Storm on Counts 1 and 3 of his indictment, proposing an October 5–12, 2026 trial window. Count 1 alleges that Storm conspired to commit money laundering by knowingly helping criminals conceal over $1 billion in stolen cryptocurrency through Tornado Cash, including funds tied to the Ronin hack involving North Korea’s Lazarus Group. Count 3 alleges that Storm conspired to violate sanctions by continuing to operate Tornado Cash after the US Treasury sanctioned the protocol in August 2022. Storm remains free on bail after a Manhattan jury convicted him only on Count 2, operating an unlicensed money transmitting business, and he is challenging that conviction with a Rule 29 motion that the court is expected to decide soon.

Market Sentiment

Cautiously Bearish, Risk-off, Regulatory-driven.

Reason: The request to retry Roman Storm on money-laundering and sanctions conspiracy counts signals that authorities are continuing aggressive enforcement efforts against crypto protocol developers.

Similar Past Cases

Historically, enforcement cases against individual developers or mixer-style tools have often led to long legal battles and uncertain precedents while direct market impact stayed concentrated in that niche segment. The current case could diverge if the eventual rulings give a clearer standard for when open-source protocol developers face liability for how users route illicit or sanctioned funds.

Ripple Effect

This retrial could influence how developers and operators think about legal risk when maintaining protocols that might be used to move hacked or sanctioned funds, because it tests how far conspiracy and sanctions laws reach into protocol governance and operations. If courts narrow or expand the interpretation of money-laundering and sanctions conspiracy for protocol maintainers, that change could shift how projects design compliance controls, front ends, or access restrictions around sanctioned addresses.

Opportunities & Risks

Opportunities: Observers can watch the Rule 29 ruling on Count 2 and pre-trial motions ahead of the October retrial window to see whether courts provide clearer guidance on developer responsibility for protocol use, which could eventually reduce legal uncertainty for some privacy or DeFi projects.

Risks: The retrial on Counts 1 and 3, together with the existing Count 2 conviction, could broaden perceived liability for running or contributing to crypto protocols, so any harsh rulings may chill developer activity and reduce usage of tools that regulators view as facilitating money laundering or sanctions evasion.