Trump-Era DOJ Pushes Back on Tornado Cash Developer’s Latest Bid to Toss Case
Attorneys for the U.S. Department of Justice have firmly rejected Ethereum developer Roman Storm’s newest attempt to have his criminal case dismissed, signaling that the high-profile prosecution over Tornado Cash is likely to proceed to a retrial.
In a letter filed Tuesday, federal prosecutors asked Judge Katherine Polk Failla to disregard Storm’s reliance on a recent U.S. Supreme Court decision, arguing that the ruling has no meaningful impact on the charges he faces. Storm’s defense team had cited the Supreme Court case as grounds to revisit the legal foundation of the indictment and potentially throw it out before a new jury is seated.
Storm, a co-founder and developer of Tornado Cash, was arrested in 2023 and charged with offenses tied to the operation of the Ethereum-based coin-mixing protocol. Tornado Cash let users obscure the origin and destination of their crypto transactions-normally visible on the public blockchain-by pooling and “mixing” funds before sending them onward to fresh addresses.
Prosecutors allege that Storm was not just a neutral coder, but that he knowingly facilitated large-scale money laundering through the service. According to the government, Storm was aware that criminals and sanctioned entities were using Tornado Cash to wash illicit proceeds, yet continued to maintain and promote the tool without implementing meaningful safeguards.
A key pillar of the case is the tension between autonomous, open-source software and traditional criminal liability. Tornado Cash’s smart contracts ran autonomously on the Ethereum blockchain, executing transactions according to code rather than manual intervention. Storm’s lawyers have leaned heavily on that fact, arguing he cannot be held responsible for how others chose to use software he no longer controlled.
The DOJ, however, is drawing a sharp line between passive publication of code and active participation in an illicit scheme. In their latest filing, prosecutors characterized Storm’s role as far more than that of a distant programmer. They claim he helped design, deploy, and maintain the infrastructure that enabled anonymous transactions, while being on notice that the system had become a favored tool of bad actors.
Storm’s team recently sought to leverage a fresh Supreme Court ruling that narrowed how certain criminal statutes can be interpreted, especially where intent and vague statutory language are concerned. Defense attorneys argued that this decision undercuts the prosecution’s theory of liability and requires a more constrained reading of the laws being used against Storm.
Federal prosecutors flatly rejected that view. In their letter to Judge Failla, they maintained that the Supreme Court case involved a very different legal context and did not alter the elements of the offenses charged in Storm’s indictment. According to the DOJ, the ruling neither changes the mental state required for liability in this case nor undermines the government’s allegations that Storm acted with knowledge and intent.
The dispute reflects a broader legal battle over how far criminal law can reach into the world of decentralized finance and autonomous protocols. Storm’s defense has portrayed him as a software developer unfairly targeted for writing code that others misused. The government, in contrast, frames him as a central figure in a service that allegedly became a laundering pipeline for hackers and sanctioned groups.
Central to that disagreement is the question of “knowledge.” The indictment claims Storm understood, or at least strongly suspected, that Tornado Cash was helping to obscure stolen or illicit funds, yet took no substantial steps to prevent that abuse. The defense counters that open-source developers cannot feasibly monitor or police all uses of their code-particularly once smart contracts are deployed and become immutable.
Prosecutors insist that Storm’s knowledge was not theoretical. They allege that he received specific warnings and was aware of law enforcement concerns about Tornado Cash’s use by cybercriminals. In their telling, he continued to sustain the project despite clear red flags, which they say crosses the line from neutral infrastructure into willful facilitation.
The Supreme Court ruling at the center of Storm’s latest motion-though not named in the public discussion-appears to involve how courts should interpret ambiguous criminal statutes and the threshold for proving intent. Storm’s attorneys hoped to use that precedent to argue that the statutes he is charged under are being stretched to cover conduct that Congress never clearly criminalized in the context of autonomous code.
The DOJ’s letter attempts to cut off that argument before it gains traction. Prosecutors emphasized that, in their view, the laws at issue are already clear in prohibiting money laundering and sanctions evasion, and that Storm’s alleged conduct falls squarely within those prohibitions. They argued that the Supreme Court decision offers no “new shield” for developers who, with full awareness, support tools used to move dirty money.
Judge Failla now faces the task of deciding how, if at all, the Supreme Court’s reasoning should influence the Tornado Cash case. Her ruling on the motion to dismiss will not just determine whether Storm’s retrial goes forward-it could also set an early benchmark for how courts will treat arguments that autonomous crypto protocols should be treated differently under criminal law.
The looming retrial itself underscores how complex and contentious this case has become. The first proceedings did not resolve the matter, and the defense has continued to introduce new constitutional and statutory challenges. Storm’s team has previously raised issues around free speech, arguing that publishing code is a protected expressive act, and that criminalizing developers for writing and deploying code could have a chilling effect on innovation.
Prosecutors have pushed back on that line of reasoning as well, noting that First Amendment protections do not extend to participation in criminal schemes. While acknowledging that code can be expressive, the DOJ contends that when code is used as a tool to carry out money laundering at scale, it can be regulated and prosecuted like any other instrumentality of crime.
The case is being watched closely across the crypto and tech sectors. Developers, protocol designers, and DeFi entrepreneurs are searching for clues as to where courts will draw the line between protected innovation and prosecutable conduct. Many fear that a broad reading of criminal liability could expose them to risk simply for building tools that can be used for both legitimate privacy and illicit concealment.
At the same time, regulators and law enforcement officials argue that robust oversight is essential. They point to a series of high-profile hacks and ransomware attacks in which stolen funds were allegedly routed through Tornado Cash-like services to frustrate tracing efforts. From the government’s perspective, allowing anonymous, unregulated mixers to operate without accountability would create a massive blind spot in the financial system.
Whatever the outcome, the Storm case is likely to influence future policy debates over privacy technologies, mixers, and zero-knowledge tools. If the court sides with the DOJ, developers may face mounting pressure to build in compliance features, monitoring mechanisms, or geofencing tools-moves that many in the decentralized finance community see as antithetical to the very ethos of permissionless systems.
If, on the other hand, Storm secures a major victory-whether through dismissal or a later acquittal-it could embolden the argument that writing and deploying open-source smart contracts, even with dual-use potential, should not by itself trigger criminal liability. That scenario might push lawmakers to step in with new, more tailored legislation designed specifically for crypto infrastructure.
For now, though, the immediate battle is procedural and interpretive. The DOJ wants the court to view the Supreme Court’s recent ruling as a non-event for this case, preserving the original structure of the indictment and clearing the way for a new jury to hear the evidence. Storm’s lawyers are trying to use that same ruling to reframe the legal standards the government must meet.
As Judge Failla considers the competing briefs, both sides are bracing for a decision that will determine the next phase of a trial that has already become a touchstone in the clash between open-source crypto development and traditional financial crime enforcement. Storm’s fate-and the boundaries of liability for developers of autonomous protocols-may turn on how narrowly or broadly the court reads the reach of existing criminal law in the age of decentralized technology.