Trump-Era DOJ Pushes October Retrial for Tornado Cash Developer Roman Storm
Federal prosecutors in Manhattan are pressing ahead with a second attempt to convict Tornado Cash developer Roman Storm on serious criminal charges, proposing an October retrial even as the U.S. government publicly concedes that crypto mixing technology can serve lawful and legitimate purposes.
Storm, a key contributor to the Tornado Cash protocol, is facing accusations of money laundering and sanctions evasion tied to the use of the Ethereum-based privacy tool. A jury last August failed to reach a unanimous verdict on key counts, resulting in a mistrial. Rather than drop the case, the Department of Justice has now moved to put Storm back on trial.
In a letter submitted Monday to Judge Katherine Polk Failla in the Southern District of New York, prosecutors working under U.S. Attorney Jay Clayton requested that the court set a new trial date for either October 5 or October 12. Those dates, they noted, align with timeframes that Storm’s defense team previously said would work for them.
The government’s filing makes clear that it intends to retry Storm on counts one and three of the superseding indictment. Together, those two charges carry a potential maximum sentence of up to 40 years in prison if he is convicted on both. The precise details of the counts have not changed: they center on allegations that Storm conspired to launder funds and to help users circumvent U.S. sanctions through Tornado Cash.
The decision to seek a retrial comes against a backdrop of mixed and sometimes contradictory signals from Washington about how crypto privacy tools should be treated under U.S. law. On one hand, the Treasury Department has acknowledged in public guidance and enforcement actions that mixing services can have lawful, even beneficial uses-such as protecting user privacy, shielding dissidents, or preventing commercial data harvesting. On the other, prosecutors are arguing that creating and maintaining such tools can cross the line into criminal activity if they are used by bad actors.
Complicating matters further, the White House has previously indicated it was at least open to the idea of clemency or a pardon for another developer involved in crypto privacy or anonymity technologies, whose alleged conduct bears similarities to the accusations now leveled against Storm. That contrast-harsh prosecution in one case, potential leniency in another-has intensified debate in legal and crypto circles over consistency, fairness, and the boundaries of responsibility for open-source developers.
Storm and his supporters have long argued that he wrote and deployed code that others chose to use, and that he did not personally handle customer funds or facilitate specific illegal transactions. To them, the case is as much about the First Amendment and whether “code is speech” as it is about financial crime. Prosecutors, by contrast, argue that Storm and his co-developers knowingly built and maintained an infrastructure that criminals-including sanctioned entities-could rely on to obscure the trail of illicit funds.
The August trial ended with the jury deadlocked on the most serious charges, signaling that at least some jurors were unconvinced by the government’s attempt to turn software development into a conspiracy to launder money. A hung jury is not an acquittal, however, and the mistrial gave prosecutors an opportunity to regroup, refine their arguments, and take another shot before a new panel.
Storm has publicly warned that the sheer cost of defending himself against the federal government is becoming a weapon in its own right. He has emphasized that if he cannot finance an adequate legal defense, the prosecution will effectively prevail “by default” rather than on the merits. For advocates of financial privacy and open-source development, his situation is a cautionary tale about how the threat of overwhelming legal expenses can chill innovation in sensitive areas like encryption and decentralized finance.
Beyond the courtroom, the case is being watched closely by developers of wallets, privacy protocols, and other infrastructure that can be used both legitimately and illicitly. Many of them fear that if Storm is ultimately convicted, it could set a precedent where writing or deploying open-source code is treated as a crime whenever that code is later misused by third parties. That risk could deter talented engineers from working on privacy-preserving tools at all, even when such tools have clear and lawful applications.
The Treasury Department’s own stance underscores the tension. Officials have repeatedly acknowledged that many individuals and organizations use mixers for entirely legal purposes: to keep salary payments private, to prevent on-chain surveillance by competitors, or to protect activists operating under repressive regimes. At the same time, regulators and law enforcement agencies highlight the role of mixers in high-profile hacks, ransomware schemes, and sanctions evasion linked to hostile states and organized crime.
This dual reality-privacy tools that are both valuable and vulnerable to abuse-lies at the heart of Storm’s case. Prosecutors are not trying to outlaw privacy per se, but they are pushing courts to accept that creators of such tools can be held criminally liable when they allegedly fail to implement controls or take action to prevent clear patterns of illicit usage. Defense attorneys counter that forcing open-source coders to police permissionless, decentralized systems is both technically unrealistic and legally unprecedented.
The retrial also dovetails with a broader political shift in how U.S. authorities approach crypto. Under successive administrations, enforcement actions have grown more aggressive, with a stronger emphasis on sanctions, anti-money laundering rules, and know-your-customer requirements. Even as policymakers speak about fostering innovation, high-profile criminal cases send a very different message to the industry: step carefully, or risk becoming the next test case.
For Storm personally, the stakes could hardly be higher. A conviction on both remaining counts could leave him facing decades behind bars, while an acquittal would be hailed by many in the crypto community as a landmark victory for developer rights and privacy technologies. The upcoming October trial dates, if approved, would set the stage for another lengthy legal battle over where the law draws the line between neutral tools and criminal facilitation.
Legal scholars are already dissecting the implications. Some argue that traditional conspiracy and money-laundering statutes are being stretched to cover technological conduct that Congress never specifically contemplated. Others maintain that the flexibility of those laws is a feature, not a bug, allowing prosecutors to adapt to new methods of hiding funds as they emerge in the digital age.
Whatever the outcome, the retrial of Roman Storm will likely shape how regulators, courts, and developers think about crypto mixers and privacy protocols for years to come. It will test whether the U.S. justice system can balance the legitimate need to combat financial crime with the equally important values of privacy, open innovation, and freedom of expression encoded in software.
As the October window approaches, both sides are expected to sharpen their narratives. The government will attempt to present Tornado Cash not as a neutral protocol but as a sophisticated laundering machine knowingly left open to sanctioned and criminal actors. The defense, in turn, will try to convince jurors that punishing a coder for the actions of unknown users would set a dangerous and far-reaching precedent-one that could redefine the risks of building privacy into the financial systems of the future.