Skip to content
Advertisement
CFTC chair Selig outlines registration rules for onchain perpetual futures

CFTC chair Selig outlines registration rules for onchain perpetual futures

Platforms offering onchain perps to US retail traders must register as exchanges or partner with one, according to CFTC Chairman Michael Selig

Running a derivatives market on a blockchain does not exempt it from the rulebook. CFTC Chairman Michael Selig said platforms offering onchain perpetual futures to US retail traders must either register as exchanges themselves or partner with an entity that has.

What Selig laid out

The guidance comes alongside a concrete approval. On November 16, 2026, Selig announced that Backpack had become the first blockchain-based designated contract market (DCM) and derivatives clearing organization (DCO).

Those acronyms do a lot of work. A DCM is a federally regulated exchange where futures can trade, while a DCO is the clearinghouse that sits in the middle of trades and makes sure both sides actually pay up.

Backpack holds the licenses through two US entities, TLD Markets, Inc. and TLD Clearing, Inc. Its DCO registration came through on November 13, 2026, and the DCM designation followed on November 16.

With both in hand, Backpack can offer US traders leveraged crypto perpetual futures. The setup supports cross-margining and accepts both crypto and fiat as collateral.

Advertisement

Perpetual futures, or “perps,” are the subscription model of the derivatives world. Traditional futures contracts expire on a set date, but perps never do, and they trade continuously around the clock, every day of the week.

Selig’s position is that new technology gets no discount on old obligations. Firms building on blockchain rails must meet the same standards as traditional markets, including customer protections and anti-money laundering (AML) controls.

How the CFTC got here

Perpetual futures trading was previously dominated by offshore venues, which often operated outside the reach of US rules. The CFTC under Selig has been working to bring that activity onshore, and to do so without waiting for Congress to pass new legislation.

Backpack is the latest step in a sequence. On May 29, the agency approved Kalshi’s bitcoin perpetual futures contract, and in November 2026 it issued clarifications covering equity perpetuals.

Backpack also was not alone in its timing. tZERO received its own DCM and DCO approvals just before Backpack’s announcement, suggesting a small queue of firms now moving through the same regulatory pipeline.

What this means for traders and platforms

For onchain perp platforms, the register-or-partner framing defines the playing field. A protocol that wants US retail flow now has a clear, if demanding, path: become a DCM, or plug into one that already is.

There is also a tension worth watching for decentralized finance. Many onchain perp protocols were built around permissionless access, and requirements like AML controls and customer protections sit awkwardly with that design philosophy.

Selig’s framework effectively forces a choice for projects that want American retail users. They can adapt their architecture to fit inside the regulated perimeter, route US users through a licensed partner, or keep serving the rest of the world while leaving the US retail market alone.

Backpack is positioning itself as the first answer to that question. The company aims to offer US retail participants a reliable alternative to offshore venues while extending compliant DeFi-style products to mainstream traders.

The key signals to watch from here are straightforward. First, whether more firms follow tZERO and Backpack through the DCM and DCO approval process. Second, whether major onchain perp protocols choose to register directly or line up partnerships with licensed exchanges.

Third is how the CFTC handles enforcement against platforms that keep serving US retail traders without taking either path. Selig has drawn the line clearly, and the agency’s next moves will show how firmly it intends to hold it.

Disclosure: This article was edited by John Chen. For more information on how we create and review content, see our Editorial Policy.