Episode Summary
Executive Summary: The episode centers on the Roman Storm/Tornado Cash case and the claim that a developer of immutable, non-custodial smart contracts may face criminal liability when third parties misuse the code. Guest Jake Chervinsky argues Judge Failla’s ruling is a dangerous precedent for DeFi, open-source software, and privacy, with potential spillover beyond crypto into broader software, AI, and encryption policy.
Main Topics: Roman Storm case and the motion-to-dismiss ruling (Priority: 5/5): The hosts unpack Judge Failla’s oral ruling denying Storm’s motion to dismiss and why Jake sees it as a major legal and civil-liberties threat. The key issue is whether a developer can be prosecuted despite lacking control over the protocol or user funds. Money transmission law and DOJ vs. FinCEN (Priority: 5/5): The conversation explains how the Bank Secrecy Act (Title 31) and the criminal money-transmitting-business statute (Title 18, Section 1960) differ, and why DOJ’s interpretation conflicts with FinCEN guidance on when crypto developers are money transmitters. Threat to DeFi, non-custodial protocols, and open-source software (Priority: 5/5): The guests stress that the ruling could implicate all DeFi developers, since many protocols are immutable and permissionless. They warn that if control is not required, neutral software developers could be exposed to criminal liability whenever bad actors use their code. Privacy, surveillance, and civil liberties (Priority: 4/5): A major theme is that Tornado Cash was primarily used for legitimate privacy, and the case is framed as part of a broader struggle over the right to transact privately, build software, and resist financial surveillance. Related Tornado Cash litigation: Netherlands and sanctions (Priority: 4/5): The episode briefly covers Alexey Pertsev’s conviction in the Netherlands and the U.S. sanctions challenge led by Preston Van Loon and others, focusing on whether OFAC can sanction immutable code or a protocol as an “entity.” SEC/crypto regulation and broader political outlook (Priority: 3/5): The discussion widens to the SEC’s enforcement posture, leadership turnover, election implications, and the overall regulatory environment. Jake argues crypto is making progress against agency overreach, even if the DOJ/Treasury front remains a major concern. Geofencing and compliance strategy (Priority: 3/5): Jake’s geofencing paper is discussed as practical guidance for projects trying to navigate unclear U.S. regulation, including when geo-blocking is sensible and how to do it more robustly than simple IP blocking.
Key Arguments: An open-source, immutable smart contract developer should not face prison for third-party misuse when he had no custody or control over user funds. The DOJ’s theory effectively decouples criminal money-transmitter liability from FinCEN’s long-standing Title 31 guidance, creating uncertainty for crypto builders. Judge Failla’s oral ruling appears to treat Tornado Cash as a “service” and says control over funds is unnecessary, which could expand liability to many DeFi protocols. DeFi exists specifically to remove centralized intermediaries; if developers must retain control to avoid liability, the core value proposition of DeFi is undermined. The ruling’s practical danger is not just Tornado Cash or privacy—it may chill open-source software development, encryption, validators, AI agents, and other neutral tools. Law enforcement’s concern is strongest when privacy prevents surveillance; public, traceable blockchains have been tolerated more than privacy-preserving ones. The best immediate outcome for crypto is an acquittal at trial; if convicted, the case could create binding appellate precedent in the Second Circuit. Sanctioning immutable code would be a profound expansion of state power and could enable arbitrary censorship of software and services the government dislikes.
Data Points: Date of ruling: Friday, September 26 - Judge Failla orally denied Roman Storm’s motion to dismiss the indictment Criminal charge under Title 18 Section 1960: 5 years in prison - Potential penalty for operating an unregistered money transmitting business Trial date: December 2 - Roman Storm’s trial was described as scheduled for early December Number of main Tornado Cash developers: 3 - Roman Storm, Roman Semenov, and Alexey Pertsev were identified as the principal developers Relevant U.S. code titles: Title 31 and Title 18 - Title 31 covers Bank Secrecy Act/FinCEN compliance; Title 18 covers criminal prosecution Chervinsky’s historical reference: 2013-2019 - He cited a long arc of FinCEN guidance on money transmission in crypto over these years Treasury-linked holding cited: 2019 FinCEN guidance - Presented as the key regulatory guidance developers and exchanges relied upon Agency affected by leadership turnover: 9 days notice - SEC enforcement director Gurbir Grewal’s departure was noted as having unusually short notice Treasury sanctions body: OFAC - The sanctions litigation challenges OFAC’s authority to sanction Tornado Cash as software/entity Layer-2 treasury figure: $3 billion - Mentioned in the sponsor segment about Mantle’s treasury size
Pivotal Quotes: "This is, in my view, for the first time, the United States government saying the developer of an open source immutable smart contract protocol should go to prison for how someone else abused that protocol even though there was nothing he could do to stop it." — Ryan Shawn Adams: Opening framing of why the Tornado Cash ruling feels historically unprecedented "Judge Fela's ruling denying Roman Storm's motion to dismiss the indictment is an assault on the freedom of software developers everywhere." — Jake Chervinsky: Jake’s core reaction to the September 26 oral ruling "You can be in compliance with Title 31, following all of Treasury's guidance, and nonetheless be engaged in money transmission as we differently define it under Section 1960." — Jake Chervinsky: Jake explaining the DOJ/FinCEN conflict and why the ruling alarms industry participants
Implications: If this logic stands, U.S. crypto builders could face criminal exposure for neutral code later abused by others. That would chill DeFi, privacy tech, and open-source software, while strengthening state surveillance power and pushing innovation offshore.