CFTC's 'Dumb Pipe' Doctrine Opens Developer Relief Beyond Phantom
The CFTC's Market Participants Division issued Staff Letter 26-25 on September 17, extending the no-action framework first granted to Phantom Technologies to all similarly situated passive software providers, and the legal logic reaches well beyond derivatives.
The CFTC just put in writing that routing software is not brokerage. That distinction matters far beyond derivatives.
Key takeaways
- The CFTC's Market Participants Division issued Staff Letter 26-25 on September 17, extending no-action relief from introducing-broker registration to passive software providers broadly, not just Phantom Technologies.
- To qualify, software must not custody assets, generate buy/sell signals, or exercise routing discretion; providers must meet ten conditions including notice filing and accepting CFTC enforcement jurisdiction.
- The "dumb pipe" principle the CFTC codified in staff form directly contradicts the legal theory DOJ used to prosecute Bitcoin wallet developers, creating an internal federal government contradiction that defense attorneys will cite in future cases.
The CFTC's Market Participants Division issued Staff Letter 26-25 on September 17, extending conditional no-action relief from introducing-broker registration to any qualifying passive software provider connecting users to regulated derivatives markets. The framework had previously been available only to Phantom Technologies, which received the original relief via Staff Letter 26-09 on March 17. Six months later, the CFTC opened that same path to the broader developer community.
Phantom co-founder and CEO Brandon Millman said in a statement that Phantom was the first passive software provider to receive no-action relief from the CFTC in March, and called the broader extension a win for the whole industry.
What the Letter Actually Permits
The staff position draws a clear line. Software can display derivatives markets, pass user orders to registered futures commission merchants, introducing brokers, or designated contract markets, and collect transaction-based fees, without triggering broker registration requirements.
What it cannot do: custody assets backing a derivatives position, generate express buy/sell signals, exercise discretion over order routing or execution, or direct users toward unregistered venues. Users must onboard directly with the registered market participant.
Providers must meet ten conditions, including maintaining compliance policies, making required disclosures, and accepting CFTC enforcement jurisdiction, per Press Release 9300-26. Relief runs until the Commission issues formal rulemaking or guidance that supersedes the staff position. This is a no-action letter, not a rule. The division says it will not recommend enforcement; it cannot bind the full Commission, and the relief can be withdrawn without a rulemaking proceeding.
The Contradiction DOJ Now Has to Answer
Event-level coverage will frame this as a derivatives story: wallets can display futures without a broker license. That framing undersells the significance of what the CFTC just published.
A software developer who builds a non-custodial front-end, routes orders to a registered counterparty, and exercises no discretion over execution is not operating as a financial intermediary. DOJ rejected that logic when it prosecuted the Samourai Wallet developers for running an unlicensed money transmitting business and Roman Storm for operating a money services business. One arm of the federal government now formally argues that passive, non-custodial routing software does not equal brokerage. Another arm has been arguing the opposite in criminal court.
That contradiction is useful, though it is not a safe harbor for Bitcoin wallet developers. Letter 26-25 is scoped to derivatives connectivity under the Commodity Exchange Act, not to Bitcoin-only wallets with no derivatives integration. The CFTC has no jurisdiction to immunize a Bitcoin wallet developer from a DOJ/FinCEN Bank Secrecy Act theory.
But the internal federal inconsistency is now documented, public, and citable. Defense attorneys in future developer prosecutions will point to it. The government cannot simultaneously maintain that routing software is categorically a financial institution and that routing software is categorically not a financial institution without explaining where the line is and why.
The CFTC's existing Bitcoin futures oversight framework gives the agency standing on derivatives, but the "dumb pipe" logic it just articulated is not derivatives-specific in principle, only in jurisdiction. That gap is where the legal argument lives.
What Has to Hold for This to Matter
The falsifiable version of the thesis: Letter 26-25 establishes a durable dumb-pipe doctrine, and that doctrine shifts the burden of proof in future developer prosecutions even outside the CFTC's direct jurisdiction.
The trigger that breaks it: the CFTC formally withdraws Letter 26-25 without replacing it through rulemaking, or DOJ successfully argues in a subsequent prosecution that the CEA no-action position is irrelevant to non-derivatives software, quarantining the "passive software is not a broker" logic entirely within the derivatives context. If that prosecution succeeds, the precedent value collapses.
The higher-value path is formal rulemaking. If the Commission votes to codify the passive-software framework into binding CFTC rules, it moves from staff opinion (revocable, non-binding) to federal regulation (requires notice-and-comment to undo). At that point, the dumb-pipe doctrine acquires real legal force and the DOJ/FinCEN theory faces a much harder challenge. Watch whether the Commission moves to initiate rulemaking in the next six to twelve months.
What to Watch
Congress will eventually need to choose a lane. The SEC's parallel custody reform and the same-day SEC relief for tokenized NMS stock trading are moving in a similar direction: regulators drawing sharper lines around what constitutes operating a financial institution versus building software that connects to one. Whether DOJ coordinates with that directional shift, or continues pursuing developers under the MSB theory regardless, is the defining question for the next cycle of developer prosecutions.
Sources
Frequently Asked Questions
No, not directly. The letter is scoped to software connecting users to CFTC-regulated derivatives markets under the Commodity Exchange Act. A Bitcoin-only wallet with no derivatives integration falls outside the CFTC's jurisdiction here, and DOJ's Bank Secrecy Act / money services business theory operates under a different statutory framework.
What the letter does do is create a documented, public federal position that passive routing software is not financial intermediation. That position is available as an argument in future cases, even where it is not controlling law.
A no-action letter is a staff-level position: the division says it will not recommend enforcement against qualifying providers. It can be withdrawn by staff without a formal Commission vote or public comment period.
A formal rule requires the full Commission to vote, publish in the Federal Register, and accept public comment. Reversing a rule requires another rulemaking cycle. The relief in Letter 26-25 is temporary by design and expires whenever the Commission issues formal guidance or rulemaking on this question.
Letter 26-25 sets out ten conditions, including maintaining written compliance policies, providing required disclosures to users, filing notice with the MPD, and accepting CFTC enforcement jurisdiction. The full enumerated list is in the letter text. Providers should read the source document directly at cftc.gov rather than rely on summaries for compliance purposes.
