CFTC Moves to Protect Non-Custodial Wallets, Clamps Down on Prediction Markets

The CFTC is moving toward formal protections for some non-custodial crypto wallet developers, with Phantom potentially becoming the template for actual rules instead of a one-off no-action letter. At the same time, the agency is taking a hard line on prediction markets, telling states to back off and let federal law do its job.

• Phantom-style wallet protections may soon be codified by the CFTC
• Non-custodial wallets could get clearer limits on broker registration risk
• Prediction markets remain under federal CFTC authority
• States challenging these markets are getting pushed back in court
• Crypto builders still need real rules, not vague staff-level handwaving

CFTC Eyes a More Practical Approach to Wallet Regulation

CFTC Chair Michael Selig said the agency wants to codify its Phantom no-action position “very soon,” which is a pretty big signal that regulators may finally be waking up to a basic truth: software that helps users access markets is not automatically the same as a broker. That matters for crypto software developers building wallets, front ends, and trading interfaces, because the line between a neutral tool and a regulated middleman has been fuzzy for years.

And that fuzziness has been a problem. When regulators treat every interface like a financial intermediary, they create a legal minefield for builders who are not holding customer funds, not taking custody, and not making trading decisions for users. That kind of overreach doesn’t just annoy developers. It pushes innovation offshore, into gray areas, or straight into the arms of lawyers. Nobody wins except the lawyers. They always seem to win.

The key issue is custody versus access. A self-custody or non-custodial wallet lets users control their own assets. The software may help them connect to trading venues, but the developer is not holding the funds or acting as a broker in the traditional sense. That distinction is central to the CFTC’s current thinking, and it is exactly where a more sensible regulatory framework could finally emerge.

What the Phantom No-Action Letter Actually Means

The Phantom no-action letter, issued on March 17, said CFTC staff would not recommend enforcement against Phantom Technologies for failing to register as an introducing broker or associated person, so long as certain conditions are met. In plain English, the agency said it would not go after Phantom for offering self-custodial wallet software used to trade with registered futures commission merchants, introducing brokers, and designated contract markets.

An introducing broker is a firm or person that solicits or accepts orders for derivatives trading. An associated person is someone tied to a registered firm who performs certain regulated functions. A futures commission merchant handles futures trades for customers, and a designated contract market is a regulated exchange where derivatives are traded. That’s a lot of regulatory machinery for what is, in this case, basically a wallet interface.

That’s why the distinction matters so much. The CFTC appears to be drawing a line between neutral software and firms that actually control customer assets or act as financial middlemen. That line should have been obvious years ago, but U.S. regulators have a bad habit of discovering nuance only after they’ve already scared off half the industry.

Still, this is not a blanket exemption. The Phantom relief is narrow and fact-specific, tied to the exact conditions laid out in the request. A no-action letter is not durable law. It is more like the regulator saying, “we’re not planning to bring enforcement on these facts, for now.” Helpful? Yes. Rock solid? Not even close.

Why Developers Care About Broker Registration Rules

If the CFTC turns this no-action position into formal rules, it could finally give non-custodial wallet developers something they have been begging for: regulatory clarity. Right now, builders face a messy question every time they create a tool that touches trading activity. Does the interface itself make them a broker? Do they need to register? Could a software product suddenly be treated like a financial intermediary just because users can trade through it?

That uncertainty is toxic. It chills development, slows launches, and forces teams to spend money on compliance theater instead of product design. Crypto does not need fewer builders. It needs fewer bureaucratic tripwires.

To be fair, regulators do have a point when software starts looking like a de facto trading venue. If a company is controlling assets, routing orders, or effectively operating as the middle layer between user and market, then “we’re just software” stops being a serious defense. But that’s exactly why the rules need to be specific. Sloppy regulation punishes the wrong people and leaves the actual bad actors with plenty of room to play games.

The CFTC has not yet released proposed rule text, and any formal rule would likely need to go through a public comment period before adoption. So while the tone is encouraging, the agency still has to do the boring part: write the rule, publish it, take comments, and stick with it. That’s the part regulators often hate because it requires accountability instead of vibes.

The SEC Is Moving Too, But Builders Want More Than Guidance

The CFTC’s signals arrive alongside related SEC guidance issued on April 13 regarding broker-dealer registration for certain crypto user interfaces. Taken together, the two agencies appear to be inching toward a clearer split between software, custody, and financial intermediation. That would be a welcome change if it turns into actual policy instead of another round of temporary statements and legal fog.

DeFi groups including DeFi Education Fund, Aave Labs, Uniswap Labs, Paradigm, and Andreessen Horowitz have pushed for binding SEC rules rather than temporary guidance. Their argument is simple: staff letters and informal guidance can be yanked, reinterpreted, or ignored. Builders need durable rules they can plan around, not bureaucratic mood swings dressed up as legal clarity.

That demand is reasonable. Crypto infrastructure is not built on sand, and developers should not be forced to guess whether a wallet or interface might be reclassified after the fact. The industry has already paid enough tuition to the school of expensive lessons.

Prediction Markets: Federal Authority, Not State-Level Interference

The CFTC’s broader message is even sharper on prediction markets. Selig said prediction markets fall under federal CFTC authority, which puts the agency directly at odds with states like Arizona, Connecticut, Illinois, and New York. Those states have tried to block or restrict federally regulated prediction markets, and the CFTC has sued them over it.

Prediction markets are contracts that let people trade on the outcome of real-world events such as elections, policy decisions, sports, and other measurable outcomes. In practice, they work a lot like derivatives markets, because participants are betting on whether a specific event will happen. The CFTC sees those markets as a federal matter, not a local playground for states to shut down whenever they get nervous about gambling optics or political heat.

The agency’s position is blunt: Congress chose a national framework for these markets instead of separate state rules. That matters because state-by-state interference would create a patchwork of nonsense, where a federally regulated market could be tolerated in one state and attacked in another. That is not serious market structure. That is regulatory chaos with a patriotic sticker on it.

This fight is really about federal preemption, meaning federal law overriding conflicting state efforts in areas where Congress has already set the framework. In plain terms, the CFTC is saying: if the market is federally regulated, states do not get to freeload on the enforcement process and start making up their own rules whenever it suits them.

Why This Matters for Crypto and DeFi

This sits at the intersection of two long-running U.S. regulatory battles: how to treat crypto software interfaces, and who controls prediction markets. On the wallet side, the potential codification of Phantom-style protections would be a real win for self-custody and for developers who are not trying to custody customer funds or act as brokers.

On the prediction market side, the CFTC is drawing a much harder line. The message is that federal oversight should remain federal, and state regulators should stop trying to swat down markets they do not like just because they can find a local statute with a scary-sounding name.

For crypto as a whole, the upside is obvious. Clearer rules could encourage more serious builders to stay in the U.S. and build products that respect both user sovereignty and legal boundaries. The downside is equally obvious: until the rules are actually published and enforced consistently, developers are still operating under a system that too often rewards caution, legal gymnastics, and delay.

And that’s the real story here. The CFTC seems to understand that self-custody wallets are not automatically brokers and that prediction markets should not be treated as state-level toys. That would be a meaningful step toward sane regulation. But crypto has heard promising language from Washington before. The proof will be in actual rule text, not press-release wallpaper.

Key Questions Answered

What is the CFTC considering?
The agency may turn its Phantom no-action stance into formal rules that protect some non-custodial wallet developers from broker registration requirements.

Why does Phantom matter?
Phantom could become a template for how regulators treat self-custody wallet software that helps users access markets without taking control of their funds.

What is the key legal distinction here?
The main line is between software that provides access and firms that hold customer assets or act as intermediaries. The former may get more protection; the latter likely won’t.

Is the Phantom relief a blanket exemption?
No. It is narrow, fact-specific, and limited to the conditions in the request. It is not a universal safe harbor.

Why do developers care?
Because unclear broker registration rules can chill wallet development, front-end development, and trading interface design in the U.S.

What is the SEC doing on this front?
The SEC issued guidance on broker-dealer registration for certain crypto interfaces, but DeFi groups want binding rules instead of temporary staff statements.

What is the CFTC’s position on prediction markets?
The CFTC says prediction markets fall under federal authority and that states should not interfere with federally regulated contracts.

Why are states fighting the CFTC?
Some states are trying to use gambling or local market laws to block or restrict federally regulated prediction markets.

What does this mean for crypto regulation more broadly?
It suggests regulators may be moving toward clearer lines between software, custody, and financial intermediation — but only if they stop hand-waving and actually write durable rules.