On October 28, 2026, CFTC Chairman Michael Selig raised questions about whether developers of autonomous trading agents could face registration requirements, who might be liable for an agent’s actions, and how regulators could identify the person it acts for. He also linked blockchain infrastructure to autonomous crypto trading. These were discussion points, not newly announced binding rules.
At a CFTC forum, participants considered how the agency’s existing framework might apply when software agents carry out financial transactions for market participants.
At the October 28, 2026, Frontier Forum, CFTC Chairman Michael Selig described autonomous trading as part of a longer shift toward increasingly automated markets. Among the questions he raised: whether an agent’s developer could be subject to registration requirements, and who would be responsible if an agent went rogue.
The discussion is relevant to crypto trading because Selig said blockchain rails could let autonomous agents custody and trade crypto assets without relying on banks, brokerages or other traditional intermediaries. The forum, however, addressed financial technology more broadly than crypto alone.
The CFTC chairman raised liability as an open question; the forum materials did not provide a final answer about who would be responsible.
With an autonomous trading system, decision-making and execution may involve the user, the agent’s developer and market infrastructure. Selig asked who would be liable if an agent acted unexpectedly and whether its developer might need to register. These were questions for further consideration, not a newly announced legal position.
For users of trading bots, the practical point is that automation does not remove trading risk or the need to understand what a system can do. The CFTC separately warns consumers to be wary of AI trading schemes that promise guaranteed or unusually high returns.
Selig asked how regulators could determine who an agent acts for and whether a distinct identification approach might be needed.
If one user deploys multiple agents that transact through digital infrastructure, it may be harder to identify the person behind a trade. Selig framed this as an agent-identification question. His remarks did not announce a new identification system or requirement.
The news therefore does not mean crypto exchanges are already required to adopt a special registration regime for AI bots. The CFTC’s Innovation Task Force, formed earlier in 2026, lists crypto assets and blockchain as well as artificial intelligence and autonomous systems among its focus areas, showing that these topics are part of the agency’s innovation agenda.
The CFTC materials reviewed describe questions for discussion, not newly adopted binding rules for autonomous AI agents.
Yes. Selig said blockchain infrastructure could enable autonomous agents to custody and trade crypto assets. The broader discussion also covered financial markets beyond crypto.
Automation does not guarantee profits. The CFTC cautions consumers against claims of guaranteed or unusually high returns from AI trading schemes.
Kraken has scheduled maintenance for its Spot Exchange website and API on Thursday, October 29, 2026, starting at 08:01 UTC. The exchange estimates about 15 minutes of downtime, followed by a staged return to normal market operation.
The maintenance is scheduled to begin at 08:01 UTC on October 29, 2026, and is expected to take about 15 minutes.
Kraken says it will upgrade systems supporting the Spot Exchange website and API. The duration is an estimate, and the precise service-restoration time may shift slightly.
If you use the API for automated trading, check the schedule against your system’s time zone and review Kraken’s status page as the maintenance window approaches.
The Kraken Spot Exchange website and API will be unavailable, and Kraken advises users not to place or cancel orders during the window.
Kraken warns that the Spot Exchange website and API will be unavailable during the work. Deposits and withdrawals initiated during the maintenance may be delayed. The notice says sign-in and other non-trading features will remain operational.
If a strategy or third-party integration submits orders through the API, consider reviewing its schedule and handling for temporary unavailability in advance. This is a practical precaution, not a separate instruction from Kraken.
After maintenance, Kraken plans to move markets through cancel-only mode, then post-only mode, before restoring full functionality.
The return to trading will be staged: markets will first enter cancel-only mode, then post-only mode, and finally return to full functionality. The end of the estimated maintenance window therefore may not mean that every order type is immediately available.
Check Kraken’s live status and the current market mode before resuming automated trading or submitting API orders.
It is scheduled for Thursday, October 29, 2026, at 08:01 UTC. Kraken estimates about 15 minutes, but the actual restoration time may vary slightly.
Kraken advises against placing or canceling orders during the maintenance because the Spot Exchange website and API will be unavailable.
Yes. Kraken says deposits and withdrawals initiated during the maintenance window may be delayed.
Check Kraken's status updates. After maintenance, markets are expected to pass through cancel-only and post-only modes before returning to full functionality.
Kraken plans to replace 176 native trading pairs with synthetic pairs. The affected pairs are scheduled to become cancel-only at 14:00 UTC on November 6, 2026; open orders will not transfer, and replacement pairs are scheduled for November 9 by end of day. Bot and API users should review the affected markets and their order-handling logic.
Kraken plans to replace 176 native trading pairs with synthetic pairs; the assets themselves will remain on the exchange.
According to Kraken’s notice, the change concerns the type of trading pairs, not the removal of the assets from Kraken. The exchange has published a list of affected pairs, which users should check before taking action.
The notice describes a change to trading markets. It does not announce changes to API endpoints or message formats, so this should not be presented as a confirmed API migration.
The affected pairs are scheduled to become cancel-only at 14:00 UTC on November 6, 2026; open orders will not carry over to replacement pairs.
Kraken’s notice gives the following timeline:
If you have an open order on an affected pair, Kraken advises canceling it before 14:00 UTC on November 6. Once a replacement pair is listed, any new order must be placed separately. Kraken also says balances are unaffected and margin pairs are not included.
Check whether your strategy uses an affected market and plan for the old pair to stop accepting new orders and for open orders to be canceled.
The market replacement may matter to automated trading even though Kraken has not announced a separate API change. Before the transition:
These are operational precautions for bot users, not claims that Kraken announced specific API changes. The notice does not say that settings, signals, or orders will be migrated automatically.
Kraken Support has published the full list; check it before changing your trading setup.
The list includes pairs with different quote assets, such as ADA/AUD, BTC/DAI, and ETH/JPY. These are examples only, not the complete list. Check the specific market and any updates on Kraken’s official support page; the exchange status page also carries the announcement.
There is a difference in how the dates appear: the status page displays a November 10 window, while the notice text describes the transition stages from November 6 to 9. For order-related actions, check the current support article and verify the schedule again before the event.
No. Kraken says balances are unaffected; the change concerns trading pairs.
No. Kraken says open orders will not transfer; any remaining orders will be canceled.
Kraken says no action is needed if you have no open orders on an affected pair. Bot users may still want to review which markets their software uses.
The notice describes replacement trading pairs, but does not announce changes to API endpoints or message formats.