Senator Lummis has placed Section 604 of the CLARITY Act at the core of her advocacy for developer protections, citing the August 6, 2025 conviction of Tornado Cash co-founder Roman Storm as definitive proof that open-source developers face real criminal liability under existing law.
A Statutory Safe Harbor
The provision aims to establish a federal safe harbor, exempting software developers who do not hold custody of user assets from being classified as money transmitters. This would serve as a direct legislative counter to the prosecution’s strategy that led to Storm’s trial.
The bill previously passed the House of Representatives with a 294-134 vote in July 2025 and was advanced by the Senate Banking Committee with a 15-9 vote in May 2026. However, it has yet to receive a vote on the Senate floor.
Nuances of the Provision
The actual scope of the provision is more narrowly defined than industry proponents often suggest, and its limitations are more significant than its supporters typically acknowledge.
The Digital Asset Market Clarity Act secured broad bipartisan support in the House, passing with a 294-134 margin in July 2025, reflecting a shared desire to bring regulatory clarity to cryptocurrency markets. The Senate Banking Committee followed suit in May 2026, voting 15-9 to move the bill forward. However, its progression to a full Senate vote remains procedurally uncertain, with no date set and ongoing inter-committee disputes unresolved.
The Roman Storm Case as a Catalyst
Senator Lummis has explicitly identified the Roman Storm case as the primary impetus for the bill. Storm, a co-founder of Tornado Cash, an open-source privacy protocol built on Ethereum, was convicted of conspiracy to operate an unlicensed money transmitting business. The jury was unable to reach a verdict on the more serious charges of conspiracy to commit money laundering and conspiracy to violate sanctions. The conviction carries a maximum sentence of five years.
In June, over 60 CEOs and founders from prominent companies including Coinbase, Uniswap, Kraken, a16z crypto, and Paradigm, sent a letter to Senate leadership, declaring Section 604 a non-negotiable requirement for their support of the broader legislation.
Legislative Intent and Legal Architecture
“Software developers should not need an army of lawyers to know if their code is legal. The Clarity Act ends that absurdity,” Lummis stated. This framing aligns with the legislative intent, though the provision’s effectiveness hinges on the specific legal framework of Section 604.
Section 604 is derived from the Blockchain Regulatory Certainty Act (BRCA), first introduced in 2018 and subsequently integrated into the CLARITY Act after multiple reintroductions. The operative text clarifies that a developer or provider who does not have control over user funds will not be considered a money transmitting business under 31 U.S.C. § 5330, nor engaged in money transmitting under 18 U.S.C. § 1960, solely by virtue of publishing distributed ledger software, offering self-custody tools, or operating infrastructure nodes.
Closing Regulatory Gaps
The Clarity Act is intended to close loopholes that illicit actors exploit, arguing that regulatory ambiguity not only hinders legitimate builders but also benefits criminals. The provision codifies existing administrative guidance from FinCEN’s 2019 statement, which held that non-custodial developers who do not control user funds are not money transmitters.
The critical determinant is the “non-controlling” test. A developer qualifies if they lack the legal authority to control user transactions, the unilateral ability to initiate transactions on demand, and the capacity to complete transfers without the approval of another party. Non-custodial protocols, by their nature, satisfy these criteria, as smart contracts execute autonomously, and developers do not possess keys to move funds. Tornado Cash exemplifies this architecture.
Under Section 604, the act of writing and deploying such code would not, in isolation, classify Storm as a money transmitter under federal law.
A Comprehensive Framework
Section 604 is complemented by Section 601, which delineates SEC registration requirements for non-custodial software builders, and Section 207, which provides a commodities-law exemption. Together, these sections form a three-part framework that positions open-source developers as technical publishers rather than financial intermediaries. This structure is significant for the broader regulatory landscape of decentralized finance, extending beyond privacy tools.
Leave a Reply