CFTC cites CME data to argue against challenge to perpetual futures

CME Group Inc. logo (public domain, Wikimedia Commons)

CFTC cites CME data to argue against challenge to perpetual futures

The regulator is using CME's own trading volumes and executive statements to dismantle the exchange's case for standing in a lawsuit over Kalshi's Bitcoin perpetual futures.

The Commodity Futures Trading Commission has found an unusual weapon in its legal fight against CME Group: CME’s own numbers. In court filings defending its approval of Kalshi’s Bitcoin perpetual futures contract, the CFTC is pointing to CME’s trading data and statements from its own executives to argue that the exchange hasn’t actually been hurt by the new product.

What happened and why it matters

The CFTC approved Kalshi’s BTCPERP contract on May 29, 2026, making it the first US-regulated Bitcoin perpetual futures product. CME Group filed suit on June 18, 2026, challenging both the product’s classification as a futures contract and the process the agency used to approve it.

CME’s core argument is that the CFTC bypassed standard regulatory procedures and that the approval threatens competition in the futures market. The lawsuit is being heard by Judge Colleen Kollar-Kotelly, and the CFTC has moved to dismiss the case, though the court had not yet ruled as of mid-October 2026.

The immediate legal question isn’t about the merits of perpetual futures regulation. It’s narrower than that: whether CME has legal standing to challenge the approval in the first place. To establish standing, CME needs to demonstrate a concrete, imminent injury. The CFTC says the evidence doesn’t support that claim.

Advertisement

CME’s Bitcoin futures volumes actually grew after Kalshi got the green light. In August 2026, CME recorded 298,958 Bitcoin futures contracts traded, a 15.3% increase from May 2026, the same month Kalshi’s contract was approved.

CME’s own executives made the CFTC’s argument for it

According to CFTC court filings, CME executives stated on July 22, 2026, that there was no customer demand for perpetual contracts from institutional clients. The executives also noted that CME could launch its own perpetual futures product if it chose to do so.

The CFTC’s argument threads these two points together neatly. Volumes are up, demand for the competing product is reportedly absent according to CME’s own people, and CME could enter the perpetual market itself. Under that reading, the harm CME describes isn’t just speculative, it may not exist at all in any legally cognizable form.

What the ruling could mean for crypto derivatives

Perpetual futures are already the dominant derivative instrument in global crypto markets, largely because offshore exchanges have offered them for years. Unlike standard futures, perpetual contracts have no expiration date and use a funding rate mechanism to keep the contract price close to the underlying asset’s spot price.

US traders have largely been cut off from these products for regulatory reasons. Kalshi’s approval was the first crack in that wall. If the CFTC successfully defends the approval and the court dismisses CME’s lawsuit, it would signal that the regulatory framework can accommodate perpetual contracts, potentially opening the door for other exchanges to seek similar approvals.

The classification question matters beyond this one product. Perpetual futures occupy a gray zone in US financial law because they don’t expire in the traditional sense, which raises questions about whether they fit neatly into the statutory definition of a futures contract under the Commodity Exchange Act. The CFTC’s decision to approve Kalshi’s product represents a regulatory interpretation that has not yet been tested in court. Judge Kollar-Kotelly’s eventual ruling, even if it’s limited to the standing question, could shape how regulators and courts approach that classification debate going forward.

CME’s response to the CFTC’s motion to dismiss was due by October 2, 2026.

Disclosure: This article was edited by John Chen. For more information on how we create and review content, see our Editorial Policy.
CFTC cites CME data to argue against challenge to perpetual futures
CFTC cites CME data to argue against challenge to perpetual futures

The regulator is using CME's own trading volumes and executive statements to dismantle the exchange's case for standing in a lawsuit over Kalshi's Bitcoin perpetual futures.

Share

Add us on Google

CME Group Inc. logo (public domain, Wikimedia Commons)

The Commodity Futures Trading Commission has found an unusual weapon in its legal fight against CME Group: CME’s own numbers. In court filings defending its approval of Kalshi’s Bitcoin perpetual futures contract, the CFTC is pointing to CME’s trading data and statements from its own executives to argue that the exchange hasn’t actually been hurt by the new product.

What happened and why it matters

The CFTC approved Kalshi’s BTCPERP contract on May 29, 2026, making it the first US-regulated Bitcoin perpetual futures product. CME Group filed suit on June 18, 2026, challenging both the product’s classification as a futures contract and the process the agency used to approve it.

CME’s core argument is that the CFTC bypassed standard regulatory procedures and that the approval threatens competition in the futures market. The lawsuit is being heard by Judge Colleen Kollar-Kotelly, and the CFTC has moved to dismiss the case, though the court had not yet ruled as of mid-October 2026.

The immediate legal question isn’t about the merits of perpetual futures regulation. It’s narrower than that: whether CME has legal standing to challenge the approval in the first place. To establish standing, CME needs to demonstrate a concrete, imminent injury. The CFTC says the evidence doesn’t support that claim.

Advertisement

CME’s Bitcoin futures volumes actually grew after Kalshi got the green light. In August 2026, CME recorded 298,958 Bitcoin futures contracts traded, a 15.3% increase from May 2026, the same month Kalshi’s contract was approved.

CME’s own executives made the CFTC’s argument for it

According to CFTC court filings, CME executives stated on July 22, 2026, that there was no customer demand for perpetual contracts from institutional clients. The executives also noted that CME could launch its own perpetual futures product if it chose to do so.

The CFTC’s argument threads these two points together neatly. Volumes are up, demand for the competing product is reportedly absent according to CME’s own people, and CME could enter the perpetual market itself. Under that reading, the harm CME describes isn’t just speculative, it may not exist at all in any legally cognizable form.

What the ruling could mean for crypto derivatives

Perpetual futures are already the dominant derivative instrument in global crypto markets, largely because offshore exchanges have offered them for years. Unlike standard futures, perpetual contracts have no expiration date and use a funding rate mechanism to keep the contract price close to the underlying asset’s spot price.

US traders have largely been cut off from these products for regulatory reasons. Kalshi’s approval was the first crack in that wall. If the CFTC successfully defends the approval and the court dismisses CME’s lawsuit, it would signal that the regulatory framework can accommodate perpetual contracts, potentially opening the door for other exchanges to seek similar approvals.

The classification question matters beyond this one product. Perpetual futures occupy a gray zone in US financial law because they don’t expire in the traditional sense, which raises questions about whether they fit neatly into the statutory definition of a futures contract under the Commodity Exchange Act. The CFTC’s decision to approve Kalshi’s product represents a regulatory interpretation that has not yet been tested in court. Judge Kollar-Kotelly’s eventual ruling, even if it’s limited to the standing question, could shape how regulators and courts approach that classification debate going forward.

CME’s response to the CFTC’s motion to dismiss was due by October 2, 2026.

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