CLARITY Act Section 604: Wyden Fights to Protect Crypto Developers

On July 8, Senator Ron Wyden (D-OR) sent a letter to Senate leaders that changed the math on crypto's most consequential legislative fight of 2026. He demanded that Section 604 of the CLARITY Act — a provision that shields non-custodial blockchain developers from being prosecuted as unlicensed money transmitters — survive the Senate floor battle intact.

The letter, first made public by Fox Business journalist Eleanor Terrett, is the clearest signal yet that the developer safe harbor has bipartisan backing. For the thousands of builders shipping open-source wallet software, node implementations, and smart contract tooling, it's a development worth understanding in full.

What Section 604 Actually Does

Section 604 of the Digital Asset Market Clarity Act incorporates the Blockchain Regulatory Certainty Act (BRCA), a standalone bill introduced by Senator Cynthia Lummis (R-WY) with Wyden as the sole Democratic co-sponsor. The provision creates a statutory safe harbor: developers who publish or maintain non-custodial software — and who do not control user funds — cannot be classified as money transmitters under the Bank Secrecy Act (31 U.S.C. § 5330) or prosecuted under the criminal money transmission statute (18 U.S.C. § 1960).

In his own words, Wyden cut through the legalese: "Developers who make and release software that allows people to manage their own digital assets, and, critically, where the developer does not control user assets, should not be treated as money transmitters solely because they create or publish software."

The safe harbor covers a broad category of activity: publishing distributed ledger software, providing hardware or software wallets for self-custody, running infrastructure that supports decentralized services, and operating nodes or validators. What it does not cover is equally important. Centralized exchanges, hosted wallets, and any service that exercises unilateral control over customer funds would still need appropriate money transmitter licenses.

Why the Safe Harbor Exists: The Tornado Cash Precedent

Section 604 did not emerge from a policy vacuum. It is a direct response to the prosecution of Roman Storm, the Tornado Cash developer facing money-transmitter charges in the Southern District of New York. Storm's case established that publishing non-custodial software is not, by itself, a defense against criminal prosecution under 18 U.S.C. § 1960.

The chilling effect is measurable. Electric Capital's annual Developer Report has tracked a material decline in America's share of open-source blockchain developers over recent years. Without a statutory safe harbor, every developer shipping a non-custodial wallet, a Lightning node implementation, a DEX smart contract, or a self-custody tool operates in the same legal gray zone that put Storm in front of a jury. The Samourai Wallet developer prosecution reinforced the same template: the government treats non-custodial software publishers as if they are financial institutions.

Then-Acting Assistant Attorney General Matthew Galeotti stated in August 2025 that "merely writing code, without ill intent, is not a crime." But enforcement discretion changes with administrations. Section 604 would codify that principle into federal statute, removing the reliance on the goodwill of whichever party occupies the White House.

The Vote Math: Why Wyden's Letter Matters

Republicans hold 53 Senate seats. The CLARITY Act needs 60 votes to clear a filibuster, meaning at least seven Democratic crossovers are required — assuming no Republican defections. Before Wyden's letter, the Democratic position on Section 604 was unclear. Now there is at least one prominent Senate Democrat on the record demanding that the developer safe harbor be preserved.

Prediction markets currently price the CLARITY Act at roughly 45 percent odds of becoming law in 2026, according to Polymarket. The bill cleared the House 294 to 134 on July 17, 2025, and advanced out of the Senate Banking Committee 15 to 9 on May 14, 2026. The floor fight is expected before the August recess, and if leadership does not bring the bill to a vote before lawmakers leave Washington, the window narrows considerably.

There is an important caveat. Wyden's letter is a demand to preserve Section 604, not a commitment to vote for the full CLARITY Act. Alex Thorn, head of research at Galaxy Digital, flagged the distinction: "Pro-BRCA does not mean he will vote YES on CLARITY." Wyden previously voted against the DeFi CRA and the GENIUS Act, so his support for the developer safe harbor does not automatically translate to the broader bill.

What Gets Protected — and What's at Stake

The universe of software covered by Section 604 is broad by design. Bitcoin Core development, Bisq, Sparrow Wallet, BTCPay Server, Phoenix Wallet, Lightning Network implementations — these are all examples of projects where developers publish code but do not control user assets. The same logic extends to smart contract platforms and non-custodial DeFi protocols. Any project where users retain full control of their funds and the developer does not intermediate transactions falls within the safe harbor.

Critically, the provision also contains a bad-actor carveout. Developers engaged in illicit activity are not protected, and the safe harbor is designed to direct enforcement resources toward actual criminals and unlicensed money-transmitting businesses, not neutral software publishers. Law enforcement groups have been lobbying to strip or weaken Section 604, arguing that it could create loopholes for illicit finance. Wyden's letter pushes back on that framing by emphasizing that the provision "does not shield those who engage in illegal activity."

What This Means for Web3 Builders

If Section 604 survives the floor vote intact, the United States will have codified a simple principle into federal law: publishing code is not transmitting money. That clarity alone would be transformative. It removes the ambient legal risk that currently makes lawyers nervous about approving open-source contributions, protocol deployments, and non-custodial product launches from US-based teams.

If Section 604 is stripped or diluted with a knowledge standard broad enough to functionally recriminalize non-custodial development, the status quo continues. Developers building in the US remain one administration change away from a hostile enforcement posture, and the talent exodus to jurisdictions with clearer frameworks — the EU under MiCA, Dubai, Singapore, Hong Kong — is likely to accelerate.

The CLARITY Act deadline is real, and so is the gap between supporting one section of a bill and voting yes on the whole thing. For the developers watching from the sidelines, Wyden's letter is not a victory lap. It is a signal that the fight over who gets to build on open networks, and where, is happening right now — and the people writing the rules may actually be listening.

If you're building onchain, the tools you use matter as much as the regulatory environment you build in. thirdweb offers developer infrastructure that handles the heavy lifting — from smart contract deployment to wallet SDKs and payments — so you can focus on shipping, no matter what happens on the Senate floor. Explore the plans at thirdweb.com/pricing.