Episode Summary
Executive Summary: The episode examines whether Tornado Cash sanctions mark the death of crypto privacy. Jake Chervinsky argues the move was surprising, likely driven by North Korea/Ronin-related national security pressure, and may be legally vulnerable because Tornado Cash is software, not a person. The discussion centers on privacy, code as speech, over-compliance risks, and whether courts will become the battleground for crypto rights.
Main Topics: Tornado Cash sanctions and crypto privacy (Priority: 5/5): Hosts and Jake debate whether OFAC’s sanctions on Tornado Cash amount to an attack on privacy tools broadly or a narrower response to North Korea’s misuse of one protocol. Code as speech vs. conduct (Priority: 5/5): The conversation revisits First Amendment doctrine from the 1990s crypto wars and asks whether writing/deploying smart contracts should be treated as protected speech or regulable conduct. National security and illicit finance tradeoff (Priority: 4/5): Jake explains Treasury’s perspective: privacy tech can help bad actors, and the Ronin/North Korea funding episode made policymakers more aggressive about cutting off illicit flows. Developer arrest and due process concerns (Priority: 5/5): The arrest of Tornado Cash developer Alex Pertsev in the Netherlands is framed as especially alarming because it appears to punish open-source software development without clear charges. Industry over-compliance and censorship risk (Priority: 4/5): The hosts discuss spillover reactions from Circle, GitHub, and potential validator/miner censorship, warning that U.S. companies may comply more broadly than required. Lessons from the 1990s cryptography wars (Priority: 4/5): The episode draws parallels to PGP, Bernstein, Junger, and the eventual success of cryptography as protected speech, arguing crypto may need similar litigation and advocacy. Advocacy strategy and public pressure (Priority: 3/5): Jake stresses that education, storytelling, donations, and public dissent matter, and that organizations like the Blockchain Association, DeFi Education Fund, EFF, and Coin Center are key defenders.
Key Arguments: OFAC’s Tornado Cash action was surprising because it targeted software and smart contracts rather than a person or entity. Privacy tools are not inherently criminal; they are neutral technologies with legitimate uses for ordinary users, dissidents, and freedom fighters. North Korea’s heavy use of Tornado Cash and the Ronin hack created a powerful national-security narrative that likely influenced Treasury. Using a privacy pool does not necessarily mean users are directly transacting with bad actors; the anonymity set is not the same as counterparty identity. The government’s current surveillance model relies on intermediaries and public blockchains; privacy-preserving tech challenges that model and may force courts to decide the limits. The 1990s cryptography cases show that code can be protected speech, but smart contracts may be treated differently once deployed as functional transaction logic. Over-compliance by firms like GitHub or Circle may exceed legal requirements and chill open-source and privacy development. The best defense is a mix of litigation, public education, and demonstrating clear legitimate use cases for privacy technology. Treasury may not be trying to “destroy crypto,” but it does want to preserve enforcement tools and limit anonymity available to U.S. persons. If crypto privacy is to survive, the industry may need to build stronger decentralized systems and push back against demands for excessive censorship.
Data Points: Tornado Cash illicit usage: ~30% to 40% of volume - Jake cites estimates that North Korea accounted for roughly this share of Tornado Cash usage recently. Ronin hack value: $640 million - Used as an example of how North Korea financed itself through crypto-linked exploits. North Korea illicit proceeds: over $1 billion in one year - Jake says Lazarus Group’s illicit activity in a year exceeded prior annual totals by about 10x. Tornado Cash launch year: 2019 - Referenced when comparing it to older privacy technologies like Monero and Zcash. PGP timeline: early 1990s - Used as historical precedent for cryptography battles over export controls and free speech. Developer detention: ~10 days - Alex Pertsev was described as being held in detention for around ten days without charges at the time of discussion. Bankless impact claim: Within 1-2 weeks - Jake says government officials have told him they listened to prior Bankless episodes shortly after airing. SmartCon date: 2022-09-28 to 2022-09-29 - Sponsor mention for Chainlink’s in-person conference in New York City. RocketPool node minimum: 16 ETH - Used in sponsor copy describing permissionless node operation. Blockchain Association policy context: U.S. crypto industry - Jake explains his role advocating for crypto firms in Washington.
Pivotal Quotes: "we are lawyering up right now" — David: Describing the industry’s response to Tornado Cash sanctions and the need for legal defense. "code is speech, right? End of story, code is speech, and speech is protected by the First Amendment." — Jake Chervinsky: Summarizing the core constitutional argument inherited from the cryptography wars. "if I were to go use Tornado Cash tomorrow, I could be thrown in jail for that." — Ryan: Expressing alarm at the practical consequence of the sanctions for U.S. users.
Implications: The episode frames crypto privacy as a live civil-liberties battle, not a solved policy issue. If sanctions on Tornado Cash stand, privacy tools, developers, and infrastructure providers may face broader censorship pressure; if challenged successfully, crypto could preserve a First Amendment-style defense for open-source financial privacy.