
The CLARITY Act is on the Senate calendar, with a developer safe harbor tied to contested money-transmission definitions. Front-end operators and governance signers face continued uncertainty until the final text is settled.
DeFi teams want a bright line between building neutral code and running regulated financial services. The U.S. Senate is finally engaging with a bill that promises to draw that line. The line is still moving.
On June 1, H.R. 3633 landed on the Senate Legislative Calendar, making it eligible for a floor vote, CryptoSlate reported. The next day, the Blockchain Association sent a letter signed by 160 former national security and law enforcement officials urging leadership to advance the bill, the group said. By June 9, the White House had hosted a meeting to hash out remaining concerns, particularly around developer protections and illicit finance enforcement, according to The Crypto Times.
Momentum exists. The text is not settled.
The bill's core protection for non-custodial participants appears in Sections 601 and 604, drawing from the Blockchain Regulatory Certainty Act. The intent is clear: publishing or supporting code without taking control of user funds should not trigger state money-transmission rules. The carve-out is tied to 18 U.S.C. §1960, the criminal statute covering unlicensed money transmitting. Negotiators want to keep that statute as a prosecutorial backstop, The Crypto Times reported.
That link matters. If amendments narrow the safe harbor, publishing code might be protected. Operating a front-end, controlling upgrade keys, routing transactions, or collecting protocol fees would still look like financial intermediation. Pure code publishing is probably safe. Business-like operations are not.
Two areas where the line blurs: front-end operations and governance control. Hosting a UI and routing orders look like facilitation, even if the protocol itself is autonomous. Capturing fees adds another layer. A team that controls the interface is likely to stay in the regulated bucket under any version of the safe harbor. Governance control is a second hotspot. A small group holding upgrade keys or directing fee flows can be treated as a de facto operator. Time-locked changes and public mandates help reduce discretion but do not eliminate risk. Cross-chain infrastructure adds another layer of ambiguity. Bridges and messaging layers where assets are locked and re-minted on another chain look custodial at the lock step. Relayers that pay gas or enforce policy rules may be offering a service, not just publishing code.
Even if the safe harbor survives in its current form, three regulatory obligations remain strict. Sanctions liability is one. OFAC's rules apply to any U.S. person operating an interface or service that touches blocked jurisdictions, regardless of money-transmission status. The bill does not pre-empt that. Contracts may be immutable. Front-ends and relayers are not. State money-transmitter regimes are another. The bill's pre-emption language has not been finalised. Multiple state regulators are watching. A federal safe harbor that does not override state law would leave a patchwork in place. SEC and CFTC jurisdiction is the third. A money-transmission carve-out does not immunize token designs, liquidity programs, or synthetic exposures from securities or commodities law. The bill does not address those questions directly.
The safe harbor hinges on not taking control of customer funds. Control is not always clear. A team that holds upgrade keys can change contract parameters, potentially redirecting funds. A relayer that pays gas fees might be seen as facilitating transactions. The statutory cross-reference to §1960 means any activity that could be construed as money transmitting without a license remains risky. The line between neutral infrastructure and financial intermediation will be tested in negotiations.
The June 9 meeting reportedly focused on two issues: developer protections under Section 604 and illicit finance enforcement. Law enforcement officials argued for preserving §1960 as a backstop. Industry representatives pushed for broader carve-outs. The outcome will shape the final text.
Practical moves that travel well across regulatory outcomes include separating pure code publication from fee-collecting services and documenting governance processes in public. Screening wallets on user-facing interfaces adds compliance. These steps do not guarantee immunity. They shift the narrative from running a broker to publishing autonomous software with compliance wrappers.
The Senate calendar does not guarantee a vote date. The key signals are amendment proposals that touch Sections 601 and 604, and any new statements from the White House or Treasury on the safe harbor's scope. FinCEN guidance and OFAC settlements in the crypto space will also shape how the bill's text is interpreted in practice.
A final vote could come this session. The text may change before then. DeFi teams that design for less discretionary control and more auditability now will have an easier transition regardless of where the line lands.
Prepared with AlphaScala research tooling and grounded in primary market data: live prices, fundamentals, SEC filings, hedge-fund holdings, and insider activity. Each story is checked against AlphaScala publishing rules before release. Educational coverage, not personalized advice.