In a move that stands to reshape the regulatory landscape for decentralized finance and blockchain software development, the Commodity Futures Trading Commission's Market Participants Division (MPD) issued a formal staff letter on September 17, 2026, declaring a no-action position in favor of providers of passive, non-custodial software. The decision signals a meaningful recalibration of how the agency intends to treat software developers whose tools facilitate trading activity without those developers ever holding, controlling, or managing user assets.
The core of the MPD's letter is straightforward in principle if complex in consequence: subject to certain specified conditions, the division will not recommend that the full Commission take enforcement action against qualifying passive software providers. In practical terms, this means that developers who build and deploy non-custodial tools — code that operates autonomously without granting its creators access to user funds or discretionary control over transactions — will no longer face the looming threat of being classified as brokers under existing Commodity Exchange Act frameworks, provided they meet the criteria outlined in the letter.
The Broker Classification Problem
The broker registration question has haunted decentralized protocol developers for years. Under the Commodity Exchange Act, entities that solicit or accept orders for derivatives or operate as intermediaries in futures markets are generally required to register with the CFTC as introducing brokers or futures commission merchants. The definitions, drafted long before smart contracts or automated market makers existed, were capacious enough to create genuine legal ambiguity around whether the developers of self-executing financial software might qualify as regulated intermediaries simply by virtue of having written the code that users interact with.
That ambiguity carried real consequences. Compliance with full broker registration is an onerous undertaking — capital requirements, record-keeping obligations, supervision mandates, and ongoing reporting duties that are calibrated for professional financial intermediaries, not software engineers. The prospect of those obligations being extended to open-source developers or decentralized application builders had served as a persistent chilling effect on innovation within the United States, pushing development talent and project incorporation offshore to more permissive jurisdictions.
What the No-Action Position Actually Covers
The MPD's staff letter is careful to make clear that the relief is conditional. The no-action position extends specifically to providers of passive software — a designation that implies the developer neither takes custody of user assets nor exercises discretionary control over how the software executes on behalf of any counterparty. The conditions attached to the relief will be critical to scrutinize in their full text, as the distinction between passive and active software roles in a financial context can be technically nuanced and fact-dependent.
A non-custodial architecture, by definition, means that private keys remain with end users and that the software developer at no point holds or controls the underlying assets being transacted. This structure has long been the design philosophy of many decentralized finance protocols, which route trades and settlements through smart contracts rather than through any centralized intermediary. The CFTC's recognition of this architectural reality, and its willingness to carve out regulatory space for it, represents an important acknowledgment that the existing brokerage rulebook was not designed with this technology paradigm in mind.
A Broader Regulatory Shift in Washington
The September 17 announcement does not emerge in isolation. It reflects a broader recalibration across United States financial regulatory agencies toward providing greater certainty — if not outright relief — to digital asset market participants. The CFTC's action fits within an evolving federal posture that increasingly distinguishes between actors who bear genuine intermediary risk and responsibility and those who build infrastructure that others use autonomously.
No-action letters, it should be noted, are not binding law. They represent the enforcement discretion of a division's staff and can be revised, withdrawn, or superseded by Commission-level rulemaking or court interpretation. Developers and their legal counsel would be prudent to treat the MPD's position as a meaningful but provisional safe harbor, not a permanent legislative exemption. Full codification of these distinctions through formal rulemaking would provide a far more durable foundation for the industry.
What This Means for the Industry
For the decentralized finance ecosystem, the CFTC's no-action relief represents one of the more concrete regulatory acknowledgments of how passive, non-custodial software actually functions — and how it differs materially from the brokerage relationships that existing rules were designed to govern. Developers of qualifying tools can now operate within the United States with a substantially clearer understanding that their software activities will not, absent a change in circumstances or conditions, draw a broker-registration enforcement recommendation from the MPD.
The decision will likely accelerate conversations between regulators and industry stakeholders about where precisely the boundary lies between passive infrastructure and active intermediation — a conversation that will only grow more consequential as on-chain derivatives markets mature and the volume of assets flowing through non-custodial protocols continues to expand. For now, the CFTC has drawn a line that the development community has long needed to see.
Written by the editorial team — independent journalism powered by Codego Press.