Invest1 publisher3 min readPublished
CFTC extends Phantom-style broker exemption to crypto software makers meeting strict conditions
Two days after the Senate stalled the CLARITY Act, the CFTC's Market Participants Division opened Phantom's March no-action position to any software provider that stays clear of custody and order routing, on ten conditions.
The Investor · Invest desk

What happened
- CFTC Staff Letter 26-25, signed by Market Participants Division director DJ Hennes, says staff will not recommend enforcement against eligible passive software providers that do not register as introducing brokers.
- Phantom Technologies got the same treatment in March, but only Phantom was covered and other developers had to file their own requests; the new letter offers substantially the same terms to any qualifying provider.
- Eligible providers cannot decide how orders are routed or executed, cannot issue express buy or sell signals and cannot take custody, and money backing a derivatives position must sit with the clearing structure.
- The conditions include conflict and fee disclosures, evidence that users acknowledged risk warnings, notice to the CFTC of any insolvency, and a filing in which the provider accepts the agency's jurisdiction.
- The letter came two days after the Senate blocked the CLARITY Act, and the SEC released its long-awaited innovation exemption the same day.
Compiled by The InvestorSomething wrong?How this is made
Why it matters
- exposure Joint and several liability with every registered partner puts the software firm's own balance sheet behind a registered firm's obligations, and contract liability is not something CFTC staff can suspend later.
- constraint Keeping the relief means leaving users a way to the venue that bypasses the app, so a provider cannot build the exclusive funnel a per-transaction fee would otherwise be charged against.
- decision Anyone weighing introducing-broker registration against the free relief is choosing between a registration it keeps and a permission one division can end at its discretion.
- precedent The CFTC has shown it will hand out in pieces, under existing authority, what the Senate declined to legislate, so the next perimeter question for crypto software is likelier to arrive as a staff letter than as a rule.
The condition that costs money is the written agreement each provider has to sign with every registered partner, covering joint and several liability [10][11]. So a wallet maker that never registers, never holds customer funds and never decides how an order is routed agrees in writing to stand behind obligations alongside the registered firm [7][11]. It also files a notice accepting the CFTC's jurisdiction, and it has to tell the agency if it becomes insolvent [12].
What it gets back is a position staff can withdraw. The division wrote that its view does "not necessarily represent the position or view of the Commission or of any other office or division of the Commission", and the letter does not bind the CFTC [13]. Staff may modify, suspend or end the relief, and it lapses if the Commission adopts formal guidance on how broker registration applies to software developers [14]. Chair Michael Selig said in May at Consensus Miami that he wanted the Phantom position codified into rules "very soon", calling the sequence "crawl, walk, run"; the rulemaking has not arrived [15].
The revenue side comes through intact. A provider can advertise its ties to registered firms, promote specific derivatives contracts, steer users toward particular venues, collect fees from registered counterparties and charge users per transaction [9]. It cannot be the only way in: users must be able to reach a designated contract market, futures commission merchant or introducing broker without passing through the software at all [8]. The per-transaction fee therefore sits on a route the user is entitled to bypass.
The legislative alternative did not fail by a hair. Cloture on the Digital Asset Market CLARITY Act went down 49 to 50, eleven short of the 60 needed, which accounts for 99 recorded votes [16][1]. Four Republicans voted no and no Democrat voted yes [17]. Flip those four and cloture stands at 53, seven short [3].
I think the letter is worth more to a developer that could not have afforded to file its own request than to anyone underwriting years of order flow on it, because the liability agreements run with the contracts while the cover behind them can be pulled by a division [4][5][11][14]. The counter-case is plain enough: registering as an introducing broker costs money this avoids entirely, and a compliant wallet discloses its fees and conflicts anyway [3][11]. Three ways it goes differently. The Commission writes the rule Selig described and the staff position gives way to guidance [15]; another division or the Commission takes a different view, as the letter says it may [13]; or CLARITY comes back and the whole file is moot [16]. Selig, writing on X after the vote, said the CFTC would help President Trump deliver "a future-proof crypto asset regulatory market structure", adding, "One way or the other, and we will help him get the job done using our existing statutory authorities." [19]
What to watch
- Whether futures commission merchants and introducing brokers will actually sign the joint and several liability agreements the relief requires.
- Whether any named developer publicly claims cover under 26-25, which would show how wide the class really is.
- How far the SEC's innovation exemption, released the same day, overlaps with the firms relying on the CFTC letter.