CFTC clarifies no-action stance for crypto software developers
DeFi & Yields ·
The commission says builders of passive derivatives tools and self-custodial interfaces won't need broker registration if they never control user funds or direct trades.
The Commodity Futures Trading Commission has issued a no-action position covering developers of passive crypto derivatives software, according to The Block. The move mirrors an approach the Securities and Exchange Commission has already taken toward crypto builders, extending a similar regulatory posture across both major U.S. derivatives and securities regulators.
Under the clarified position, developers who build passive derivatives software or self-custodial trading interfaces can do so without triggering broker registration requirements, provided they do not control customer funds or direct order flow. The distinction the CFTC is drawing centers on custody and control: tools that merely facilitate access to markets, without the developer holding assets or making trading decisions on a user's behalf, fall outside the scope of broker-dealer obligations that would otherwise apply.
The clarification is being read as an attempt to remove regulatory ambiguity that has hung over software teams building trading infrastructure for crypto derivatives markets. Multiple accounts of the development describe it as a no-action position specifically for passive derivatives software providers, a category that had previously operated without explicit guidance on registration status.
Coverage tracked by leviathan.news situates the CFTC's move within a broader pattern of regulators addressing crypto infrastructure questions in sequence, with the CFTC's guidance following the SEC's earlier developer-friendly stance rather than arriving independently. The overlap between the two agencies' positions suggests a degree of coordination, or at least parallel reasoning, on how to treat non-custodial software providers within existing regulatory frameworks.
What remains unclear from the available material is the precise scope of "passive" software under the CFTC's definition, how the agency will treat hybrid products that combine passive interfaces with some custodial functions, and whether the no-action position carries any expiration or conditions for revocation. Also unaddressed is how state-level regulators or other federal bodies might respond to or diverge from this joint federal posture. Further guidance or enforcement actions testing the boundaries of "control" over funds or orders would clarify how durable this developer-friendly framework proves to be in practice.