CFTC argues CME perpetual futures case lacks legal standing

CFTC tells federal court CME's perpetual futures label dispute lacks standing

On May 29, the CFTC approved Kalshi's Bitcoin perpetual contract — the first of its kind to enter the regulated U.S. market. CME announced its legal challenge three weeks later. The CFTC's response, filed Wednesday, was four words before the argument even began: "much ado about nothing."

The agency's motion to dismiss rests on two claims. First, that CME has not demonstrated financial harm from the approval. Second, and more consequentially, that CME could list the identical product tomorrow under the same order it is challenging. The CFTC's registered designated contract market framework extends to all DCMs, not only Kalshi. CME's own executives, the agency noted, had said publicly that their customers had not requested perpetual futures and did not view them as substitutes for existing products. That statement, made before the lawsuit was filed, does not help CME's injury argument.

The substantive dispute is narrower than the filings suggest. CME is not arguing the CFTC lacked authority to approve perpetual futures. It is arguing the agency used the wrong label. Perpetual contracts — which carry no expiration date and no delivery obligation — meet the Commodity Exchange Act's definition of a swap, CME contends, and therefore should have gone through swap approval procedures rather than futures certification. The CFTC's position is that the label does not determine the harm, and that CME has not identified any legal consequence that flows from the classification itself.

This is where I think the consensus reading of this dispute is incomplete. Commentators have focused on the competitive dimension — Kalshi gaining first-mover advantage in a product category CME wanted to control. That is real, but it is not the legal weight-bearing wall. The classification question matters because swap and futures approval processes carry different documentation standards, different counterparty requirements, and different disclosure obligations. If CME is right that perpetuals are swaps and the CFTC approved them as futures, then every contract certified under that order rests on a procedural foundation the CEA did not authorize. The CFTC's copper perpetual filing, which the agency has already signaled requires individual review outside the digital commodity framework, suggests the commission itself is not entirely settled on where the category ends.

The judge has not signed the proposed order. That is not unusual at the motion-to-dismiss stage, but it means the case has not resolved and the classification question is still formally open. Kalshi has also filed to certify perpetuals on twelve additional digital assets, including Ethereum and Solana. Each certification compounds the exposure if CME's procedural argument eventually finds traction.

The Commodity Exchange Act requires that a futures contract involve a commodity with a defined delivery mechanism or cash settlement tied to a reference price on a specific date. Whether a contract with no expiration date and no delivery obligation satisfies that definition is not answered by the CFTC's approval — it is answered by the statute, and ultimately by a court reading the statute against the record.