Two days after the Senate failed to pass the Clarity Act, the Commodities and Futures Trading Commission sent a crypto rulemaking proposal to the White House Office of Management and Budget. We don’t know what’s in it. That’s not a rhetorical flourish. The CFTC disclosed no details.
Which crypto assets does it cover? Unclear. What would an exchange have to do to qualify? Unclear. What restrictions apply, and how far does the CFTC think its own authority reaches? Also unclear.
So the headline here isn’t the content of the rules. It’s the timing.
Congress couldn’t get it done, so the agencies moved on their own.
The Clarity Act was supposed to settle the jurisdictional question that has defined US crypto regulation for years. It didn’t pass. Within 48 hours, both market regulators started filling the gap with tools they already had.
“The CFTC is locked in and ready to ship its rules for the new frontier of finance,” CFTC chair Mike Selig wrote in a post on X after Wednesday’s vote.
Selig’s phrasing is worth reading twice. “Ready to ship” is developer talk, not regulator talk, and it lands differently when the thing being shipped hasn’t been described to anyone outside the building.
The proposal still has three gates to clear.
Here’s the part that gets lost when people treat an OMB submission as a done deal. The OMB reviews the draft. It goes back to the CFTC. The commission votes. There’s a public comment period. Then it needs another vote to actually become effective.
That’s a long runway for something nobody has read yet. If you’re trading on the assumption that CFTC-supervised crypto markets arrive on a specific date, you’re guessing.
The SEC moved the same day, and its action is the more concrete one.
On Thursday, the Securities and Exchange Commission issued an “innovation exemption” giving qualifying platforms a five-year path to offer onchain trading of certain tokenized stocks without registering as securities exchanges.
Five years is a real number attached to a real mechanism. Compare that to the CFTC filing, where the only verifiable fact is that a document exists and the OMB has it.
Both agencies said they’ll keep working together to give the industry clearer rules under their existing authority now that the Clarity Act is dead for the moment. Existing authority is the operative phrase. Neither regulator is claiming new powers here, and that constraint shapes everything they can do.
The no-action letter is the piece builders should read first.
On Friday, the CFTC published a no-action letter that gives certain software providers a way to connect users to regulated derivatives markets without registering as introducing brokers. It covers passive software that lets users view markets and submit orders directly to registered firms, including through crypto wallets.
Unlike the OMB submission, this one has specifics you can act on.
Providers can market specific contracts. They can take transaction-based fees. What they can’t do, according to the letter: hold customer assets, generate buy or sell signals, or control how orders are routed or executed.
Draw that line honestly and a lot of wallet front ends fall on the wrong side of it.
Any interface that surfaces a “recommended” trade is generating a signal. Any router that picks an execution venue for you is controlling routing. The relief is written for thin, passive plumbing, and a fair amount of what ships in crypto wallets today is neither thin nor passive.
The conditions attached include risk disclosures, recordkeeping and compliance with marketing rules. None of that is free to implement, and the compliance overhead is the real cost of the exemption.
And the relief has an expiration date nobody controls.
It stays in place until the CFTC adopts rules or guidance addressing registration requirements for software developers. Meaning the same agency that just sent an undisclosed rulemaking proposal to the OMB can end this relief by finishing that work.
The no-action letter and the OMB submission aren’t separate stories. They’re the temporary version and the permanent version of the same question.
If you build software that touches regulated derivatives, the practical move this week is to audit your product against those three prohibitions and assume the relief is a bridge, not a destination. If you’re waiting on the CFTC’s actual rules, check back after the commission votes and the comment period opens. That’s the first moment anyone outside the OMB will see what’s in the thing.
