CLARITY’s developer shield could shape crypto policy

The CLARITY Act could protect open-source crypto builders while keeping enforcement against illicit conduct.

Solana’s policy chief says the Senate should keep a developer shield in the CLARITY Act, and the debate now centers on a 15-9 committee vote, Section 604, and where software ends and financial intermediation begins.

1. The developer shield is the bill’s main fault line

Kristin Smith, president of the Solana Policy Institute, is pressing senators to keep the CLARITY Act’s protections for non-controlling blockchain developers. Her argument is simple: if the bill blurs the line between writing software and running a financial business, builders may move their work outside the U.S.

The core issue is not whether crypto should be regulated. It is which actors should carry the rules. The bill’s supporters want a structure that treats developers differently from custodians, brokers, and exchanges, since those firms actually hold assets, route trades, or manage customer transactions.

• Open-source code publication
• Infrastructure maintenance
• Self-custody tooling
• Distributed ledger support

2. Section 604 gives developers a specific legal lane

The Senate version of H.R. 3633 includes Section 604, the Blockchain Regulatory Certainty Act, which says a non-controlling developer or provider would not be treated as a money transmitter solely for publishing software, providing self-custody tools, or maintaining distributed ledger infrastructure.

That language matters because it gives legal cover to people who support a network without controlling user funds. In practice, it is aimed at open-source teams, validators, and wallet builders who help keep blockchains running but do not execute trades or take custody of customer assets.

3. The bill still draws a hard line around intermediaries

Smith’s position is that builders should not be treated the same way as regulated intermediaries. Under the draft framework, the people who custody assets, facilitate trading, or process customer transactions remain in the regulatory bucket, while software publishers stay outside it unless they cross into control or custody.

That distinction is the policy heart of the fight. If lawmakers preserve it, developers can keep building without being pulled into money-transmission rules just because their code touches a blockchain. If they weaken it, the compliance burden could spread far beyond exchanges and custodians.

• Developers: write and maintain code
• Validators: secure and confirm network activity
• Wallet providers: offer self-custody tools
• Exchanges and custodians: handle user assets and transactions

4. The Senate fight is now about scope, not just passage

The CLARITY Act advanced from the Senate Banking Committee in a 15-9 vote on May 14, but the floor debate will likely be messier. Lawmakers are also wrestling with anti-money-laundering rules, stablecoin rewards, and political issues tied to crypto ventures.

More than 200 crypto companies and organizations have urged Senate leaders to move the bill forward, and more than 60 executives and founders have separately asked for the developer language to stay intact. The bill also keeps criminal liability for people who act with intent to move funds tied to criminal activity, which is the main safeguard for enforcement hawks.

• 15-9 committee approval
• 200+ firms backing a vote
• 60+ leaders backing developer language
• Criminal intent carveout remains in the text

How to decide

If you are an open-source builder, validator, or wallet developer, the current draft is attractive because it separates software work from custody and trading. If you are a compliance-focused exchange or custodian, the bill is more about clarifying where your obligations begin than reducing them.

The real test is whether the Senate keeps the shield narrow enough to protect non-controlling developers while leaving enforcement tools intact for fraud and illicit finance. That balance will decide whether CLARITY reads like a boundary-setting bill or a wider crypto compliance reset.