Wyden Pushes to Keep Crypto Devs Out of Money Transmitter Rules
Senator Ron Wyden (D-Oregon) wants the CLARITY Act to keep language protecting blockchain developers from being treated like money transmitters. The core question is simple: if a developer writes non-custodial software and never touches customer funds, should that person follow the same rules as a payments company? Wyden says no. My take: that is the cleanest version of the argument, and it is also the part opponents keep trying to complicate. Crypto teams care because the answer could affect whether more DeFi work stays in the US or moves to places with clearer rules.
Wyden asked Senate Majority Whip John Thune (R-South Dakota) and Senate Majority Leader Chuck Schumer (D-New York) to preserve Section 604, the Blockchain Regulatory Certainty Act (BRCA). His argument is not fancy. Remove the language, and developers are left guessing which law applies to them. Keep it, and law enforcement can focus on people and companies that actually hold or move funds. Most crypto policy debates pretend every participant is doing the same thing. That is only half right. The BRCA began as a standalone bill from Senator Cynthia Lummis (R-Wyoming) before it was folded into the CLARITY Act. Wyden is its only Democratic co-sponsor, so yes, the support is bipartisan. Narrow, too.
The BRCA would create a safe harbor for people who build non-custodial blockchain software. In plain English, that means software that does not hold, control, or transfer user funds. Right now, those developers have an odd legal threat hanging over them: maybe they are money transmitters, maybe they are not. If they are, the registration and compliance burden can be brutal, especially for a 5-person team trying to ship code instead of hire a legal department. The BRCA says developers are not money transmitters simply because they wrote the software. Why does this matter? Because this is not some academic argument about definitions. It is the difference between building the next DeFi protocol in Oregon, New York, or Wyoming, or quietly moving the company to Singapore or Switzerland.
Wyden is stepping in while the CLARITY Act is still moving through the Senate, where one amendment can change the bill. He says policy should give law enforcement useful tools without turning software developers into financial intermediaries by default. I will be honest: I think that distinction is the whole fight. If a company takes custody of funds, regulate it like a financial service. If a developer publishes code that users run themselves, that is different. Counter to the usual advice, “more regulation” is not the useful phrase here. The useful line is custody versus non-custody. The crypto industry mostly backs the BRCA because it gives developers something they rarely get in Washington: a plain answer. It also pushes back against the lazy version of the crypto debate, where every on-chain activity gets treated as the same risk.
Law enforcement groups are not convinced. Some worry the BRCA could make it harder to pursue crimes tied to human trafficking, sanctions evasion, or money laundering. Their concern is that exempting developers from money transmitter rules could leave gaps investigators have to deal with later. Fair concern. The law has to separate neutral software from services that actively move money, and it has to do that without handing bad actors an escape hatch. For investors, this is the kind of regulatory fight that can move prices before the law changes. Developer liability affects how risky a US-based protocol looks. Enforcement news has already hit crypto markets hard. SEC actions around staking services, for example, have helped trigger 5-10% drops in tokens like ETH during periods of heavier scrutiny. Clearer rules could cut the other way.
If the BRCA gets removed, US developers stay in the fog. Some will keep building anyway. Others will leave, or at least set up somewhere with fewer legal unknowns. Is this overkill for one section of one bill? No, because Section 604 is the part that tells builders whether publishing non-custodial code can drag them into money transmitter territory. That could slow US-based crypto projects and make American teams less competitive. If the provision survives, it would give courts, founders, and investors a cleaner line between decentralized software and custodial financial services. Yes, this slightly contradicts the “plain answer” point above, so bear with me: the line will still be fought over. It will just be a better fight. That line sounds boring until you need it. Then it is everything. A win here could make US crypto ventures easier to fund, especially infrastructure projects and DeFi teams. It could also help sentiment around large assets like BTC and ETH if investors read it as a sign that US rules are becoming less hostile.
What this means
This fight is about what kind of crypto activity the US wants to allow. The BRCA is not only a definition fight, though the wording matters. It asks whether writing non-custodial software should trigger the same obligations as holding customer funds. My read: the market will treat this less like a legal footnote and more like a signal about whether US crypto policy is becoming usable. If the provision passes, it could pull more developers and venture money back toward the US. That would likely help infrastructure tokens and layer-1 networks like Ethereum (ETH) and Solana (SOL), since both rely heavily on developer activity. If it gets cut, expect more talk about US brain drain and a weaker short-term mood around projects with American teams.
Investors should watch the CLARITY Act closely, especially Senate floor votes and amendments over the next few weeks. News that the BRCA is being removed would probably hurt sentiment. News that it stays in could give the market the cleaner regulatory story it has been waiting for. This will not be settled in one headline. Watch what Wyden, Lummis, Thune, Schumer, and the major industry groups say as the bill moves. Section 604 may look dry, but for developers building in the US, it could decide how much legal risk they take on every time they ship code.