Code is not a crime, DOJ redraws line

Code is not a crime: the new DOJ line

Code is not a crime has become the clearest policy signal yet from the Justice Department’s crypto team. Acting Attorney General Todd Blanche now says developers should not be investigated or charged unless they knowingly help third parties commit crimes. That matters because the U.S. has spent years testing how far criminal law can reach into software design, especially around mixers, wallets, and privacy tools. The new stance does not erase enforcement. It redraws the boundary between building software and helping conceal illicit activity.

For crypto developers, that distinction is everything. A protocol can be permissionless, privacy-preserving, and still attract scrutiny if prosecutors think the team encouraged or knowingly enabled misuse. Blanche’s statement suggests the DOJ wants to stop treating software authors like automatic accessories to every downstream abuse. But it also leaves intact the core idea that intent, knowledge, and conduct still matter. In other words, the code itself is not the crime; the surrounding behavior may still be.

What did Todd Blanche actually say?

Blanche said developers who are not the third-party user and are not helping that user commit crimes will not be investigated or charged. He framed the shift as a change in enforcement philosophy, not a broad amnesty for crypto companies. The comments came as the DOJ also continues to pursue active cases tied to digital assets and financial crime. The practical message is narrow: software creation alone is not enough for a criminal case, but evidence of coordination, concealment, or facilitation still matters.

That is a major contrast with the past few years, when U.S. authorities used aggressive theories to reach developers and protocol operators. The Tornado Cash dispute became the emblem of that tension, with prosecutors arguing that privacy infrastructure can be misused while defenders argued that publishing code cannot equal criminal conduct. Blanche’s remarks do not end that debate. They simply make the DOJ’s current posture more explicit: the government wants to focus on the person who uses the tool to commit fraud, laundering, sanctions evasion, or other crimes.

Why this matters for crypto developers and protocols

The market should read this as a legal narrowing, not a regulatory holiday. DOJ crypto enforcement still exists, and the agency can still target conduct linked to fraud, money laundering, sanctions violations, and other offenses. What changes is the implied threat surface for open-source builders. If the government sticks to this line, developers may face less fear that shipping neutral infrastructure will automatically trigger prosecution. That could support more experimentation in privacy, payments, and decentralized financial tooling.

But the structural risk has not disappeared. The line between “building” and “aiding” is still contestable, and that leaves room for selective enforcement. The biggest takeaway is that prosecutors are signaling they want cleaner cases with clearer intent. That should reduce some chilling effects, but it will not protect teams that ignore obvious abuse or design systems to hide it. For protocols, governance, documentation, and compliance controls still matter. The DOJ may have softened its rhetoric, but it has not abandoned the logic of culpability.

Could this change the Tornado Cash debate?

Yes, but only at the margins. The Tornado Cash developers case remains one of the most important tests of how U.S. law treats open-source software, privacy, and criminal intent. Blanche’s statement gives defense lawyers a cleaner policy argument: if the DOJ says code alone is not enough, then the prosecution must prove more than publication and participation. Yet prosecutors still have a path if they can show knowledge, coordination, or deliberate disregard for obvious criminal use.

The deeper issue is institutional. The DOJ appears to be separating two categories of crypto activity: legitimate infrastructure and intentional criminal enablement. That sounds simple, but in practice it is difficult. Many tools are dual-use. Mixers, bridges, wallets, and privacy layers can serve ordinary users and bad actors at the same time. The policy shift therefore reduces ambiguity at the top level, but it does not remove ambiguity in the courtroom.

What This Means For Investors (Our Take)

For investors, the message is cautiously constructive for the infrastructure layer. A clearer standard around crypto developer charges could improve confidence in open-source teams, privacy-adjacent projects, and the broader U.S. builder ecosystem. It may also reduce the legal discount applied to protocols that have always depended on software neutrality rather than centralized control.

Still, the real signal is not “permission.” It is selectivity. The DOJ seems more willing to chase users, fraud rings, and explicit facilitators than to make examples of coders. That is better for the industry, but it also means enforcement risk now concentrates where evidence is easiest to prove.

Focus: The DOJ is not absolving crypto — it is narrowing the target from code to conduct.

Antonio Quinn, Director & Lead Bitcoin Analyst, The Chain Journal