CFTC Chairman Michael S. Selig raised a question for developers of autonomous crypto agents on October 28: when software can custody assets and trade without traditional intermediaries, who bears the registration and liability obligations?
His remarks at the Frontier Forum on Super Intelligence put that question on the policy agenda without answering it. The speech announced no rule, enforcement action or implementation date. Selig also said the views were his own and did not necessarily reflect those of the Commission.
For developers, the immediate distinction is between an open regulatory question and an existing, conditional staff position. September relief for passive software describes interfaces that transmit users’ orders without making decisions about particular trades. It does not settle the treatment of an autonomous agent that selects or executes trades.
What Selig asked about autonomous agents
Selig described blockchains as infrastructure through which autonomous agents could custody and trade crypto assets without traditional intermediaries. He asked whether developers might need to register, who would be liable when an agent acts improperly, and how to determine on whose behalf it trades.
Those questions reach beyond the label attached to a product. In the speech, Selig pointed to the functions performed, the control exercised and the economic realities of a transaction as considerations for the regulatory approach. That was policy framing in his remarks, rather than a newly adopted legal test.
The speech identified no particular product or developer and announced no determination that an agent falls within an existing registration category. It therefore provides no basis to conclude either that all autonomous crypto agents must register or that they sit outside CFTC jurisdiction.
Where the passive-software position stops
The relevant existing document is CFTC Letter 26-25, issued by the Market Participants Division on September 17. It addresses introducing-broker and associated-person registration requirements for passive software providers facilitating users’ access to registered futures commission merchants, introducing brokers and designated contract markets.
The covered interface transmits users’ orders directly and has no affirmative involvement in particular orders. Under the letter’s conditions, the provider must not hold, control or custody user assets, generate express buy or sell signals, or exercise discretion over order routing or execution.
The CFTC’s September announcement made a similarly conditioned staff position broadly available to passive-software providers beyond the original Phantom letter. Broader availability did not remove those conditions or turn the position into a Commission rule.
This is the practical tension raised by Selig’s speech: software described as autonomous may perform decisions that the passive-software position expressly excludes. That difference explains why the letter cannot, by itself, answer the agent question. It does not establish the legal classification of any specific agent.
CRYPTO MAIN NEWS previously covered the letter in its report on separate CFTC policy steps. The new development is Selig’s discussion of autonomous agents, rather than a revision of that September relief.
A policy signal with no implementation timetable
The letter remains a fact-specific, conditional position of the issuing Division and is expressly not binding on the Commission. It says the position lasts until the effective date of Commission rulemaking or guidance addressing introducing-broker registration for software developers. Selig’s speech is neither such rulemaking nor such guidance.
His remarks could be an exploratory statement at a forum rather than a sign of imminent rulemaking. The absence of a named proceeding, proposed requirement or timetable leaves that distinction unresolved. Developers have a clearer view of the questions the chair is asking, but no new agent-specific registration answer from this speech.
The next material development would be a Commission proposal or guidance addressing autonomous agents, a specific registration or liability determination, or a change to the passive-software staff position. Any of those would need to be assessed on its own terms. For now, the October 28 remarks identify the policy problem while leaving the operative legal questions open.
Editorial illustration: CRYPTO MAIN NEWS / OpenAI. Generic hearing-room setting; not the CFTC or an actual event.
Investment disclaimer: This article is provided for general information only and does not constitute investment, financial, legal or tax advice. Digital assets are volatile, and all investment decisions and their consequences are your own responsibility.