CFTC gives passive software providers a path around introducing-broker registration

On September 17, the CFTC’s Market Participants Division issued a no-action position for passive software providers — the kind of infrastructure that sits between users and regulated counterparties without itself running the trading relationship. The primary CFTC release describes the position as broadly available and comparable to Staff Letter 26-09.

What MPD won’t do: recommend enforcement against passive-software providers or their personnel solely for failing to register as an introducing broker or as an associated person of an introducing broker. Those are the two specific registration categories the position covers, and the scope is tighter than it might sound.

The permission attaches to “the provision and marketing of software to facilitate trading” by users with registered futures commission merchants, introducing brokers, and designated contract markets. The document addresses the software layer and its marketing. Users’ actual trading relationships still run through registered entities — that part of the structure doesn’t change.

The exposure stays tied to scope, though. The fact sheet doesn’t supply the letter’s specific conditions, so the record available here doesn’t establish how MPD would classify every software design, interface, or operating model.

That gap matters. Projects whose role extends beyond supplying and marketing software are in different territory. The CFTC’s stated position covers facilitation for users trading with registered futures commission merchants, introducing brokers, and designated contract markets; it’s not a blanket clearance for every DeFi developer or every product that touches futures in some way.

What the position does is carve out a meaningful separation between a passive tool provider and a party doing something the described software-only role doesn’t cover. Qualifying infrastructure projects get a cleaner enforcement posture. Teams still have to map their own functions against the letter’s conditions before treating September 17’s position as applicable to them.

This is one document in a sequence of CFTC relief actions, not a new statutory registration regime. Staff Letter 26-09 is the named comparison in the release. Coinscoop has also covered a separate CFTC no-action action involving large-trader reporting, which targets a different population entirely.

For users and token holders, the September 17 release states no token, trading, or protocol change. The direct beneficiaries are software providers and their personnel that fit the stated scope. Whether a given product satisfies the letter’s undisclosed conditions is the question that still needs answering.