The Commodity Futures Trading Commission is drawing a sharper line between building financial software and acting as a financial intermediary, potentially opening a new chapter for derivatives markets and crypto trading.
The agency’s position that developers can create passive derivatives software without registering as brokers, including software used in crypto markets, addresses a question that has become increasingly important as financial infrastructure moves from traditional intermediaries into code.
If software merely provides tools for users to interact with markets without taking custody, exercising discretion or executing trades on their behalf, the regulatory treatment can be different from that applied to a conventional broker.
Register for the next Tekedia Mini-MBA.
Register for Tekedia AI in Business Masterclass.
Join Tekedia Capital Syndicate and co-invest in great global startups.
That distinction matters because decentralized finance has increasingly challenged the assumptions embedded in financial regulation.
Traditional markets were constructed around identifiable institutions: brokers accept orders, exchanges match trades, clearinghouses manage settlement and custodians hold assets. In crypto markets, some of those functions can be replaced by smart contracts, automated protocols and interfaces operated by software developers.
The CFTC’s approach could therefore have consequences well beyond a narrow compliance question. It potentially gives developers greater room to build derivatives infrastructure without automatically becoming subject to the registration requirements associated with intermediaries.
The crucial word, is “passive.” Developers do not receive a blanket exemption simply because their products are built with blockchain technology or marketed as decentralized. The regulatory distinction depends on what the software actually does and how much control its operator exercises.
A system that simply provides technical functionality may be treated differently from one that actively solicits customers, manages transactions, controls funds or exercises discretion over trading activity.
That creates an important boundary for the emerging crypto derivatives industry. Developers can build infrastructure, but the closer a product moves toward brokerage, execution or financial intermediation, the greater the possibility that existing regulatory obligations become relevant.
For the crypto industry, this clarification could encourage experimentation. Derivatives are among the most sophisticated and economically significant products in digital assets, offering tools for hedging, leverage and price discovery. Yet they also carry substantial risks.
Leverage can amplify losses, while poorly designed protocols can expose users to liquidation cascades, smart-contract vulnerabilities and market manipulation. The challenge is therefore not simply whether developers should be allowed to build.
It is whether regulators can distinguish technological infrastructure from financial activity without creating loopholes that allow regulated functions to migrate into supposedly neutral software.
That question will become more important as financial applications become increasingly autonomous. An interface may look passive while its underlying architecture performs functions that resemble those of a traditional intermediary.
Imposing broker-style obligations on every developer who creates open financial software could discourage useful innovation and push activity toward less transparent jurisdictions. The CFTC’s position represents an attempt to navigate that middle ground.
It recognizes that writing software is not necessarily the same thing as operating a brokerage, while preserving the possibility of regulatory oversight when developers cross into active financial services. For crypto, that distinction could prove consequential.
The next generation of derivatives markets may not be built around firms that look like yesterday’s brokers. They may be built around protocols, smart contracts and permissionless software.
The regulatory question is becoming less about who owns the trading desk and more about what the code actually does. That shift could define the next phase of digital-asset market structure.
But the lasting test will be whether regulatory clarity can encourage innovation without allowing financial risk to disappear behind the word “software.”