Articles
CME vs CFTC: The Self-Certification Question with Perpetual Contracts
Maria Samson
July 16, 2026
The lawsuit filed by Chicago Mercantile Exchange ("CME") against the Commodity Futures Trading Commission ("CFTC") on June 18, 2026 in the U.S. District Court for the District of Columbia[1] is, on its face, a regulatory classification dispute. But for those operating at the intersection of crypto and financial infrastructure, it raises questions regarding the durability of regulatory approvals, the boundaries of agency authority, and what a favorable or unfavorable outcome means for digital asset market infrastructure.
On May 29, 2026, the CFTC, under one sole CFTC commissioner, issued an order approving KalshiEX, LLC ("Kalshi"), the prediction market platform, for the listing of the BTC PERP Contract, a perpetual contract that references the spot price of Bitcoin.[2] The order marked the first time perpetual contracts could be traded onshore in the United States under federal regulatory oversight, which was a significant regulatory first. In just three weeks, the CME filed suit arguing that the order violated the Commodity Exchange Act ("CEA"), and unlawfully reclassified instruments that Congress had designated as swaps under a different regime.
CME has been critical of the Kalshi approval, claiming that perpetual contracts should be classified as swaps under 7 U.S.C. § 1a(47)(A)(iii) of the 2010 Dodd-Frank Wall Street Reform and Consumer Protection Act.[3] Generally, a perpetual contract tracks an underlying asset's spot price, involves ongoing payment exchanges between counterparties based on price differentials, has no expiration date, and imposes no delivery obligations on either party.[4] CME is arguing that this structure is essentially a swap and that Congress already answered the classification question when it enacted the Dodd-Frank Act, which defined instruments with these characteristics as swaps subject to a more rigorous oversight and disclosure regime.
Notably, the CFTC itself had previously treated perps as swaps, having classified them as such in separate enforcement actions against KuCoin, Binance, Mango Markets, Deridex, and BitMEX between 2020 and 2024.[5] CME's complaint argues that the Kalshi approval represents an unexplained and unlawful reversal of the agency's own prior position.
Because the CFTC's order approved Kalshi's perpetuals as futures instead, it bypassed the swap regulatory framework entirely. This order also allows any futures exchange to self-certify similar cryptocurrency perpetual contracts going forward, without individual CFTC review, a broad delegation that amplifies the stakes considerably. CME also raises a procedural concern stating that the CFTC opened a public comment period on the swap-versus-futures question, received over 150 responses, and did not acknowledge such responses. In turn, the CFTC issued the Kalshi approval one day after receiving its application.
Our Read
Both the substantive and procedural arguments have some merit, and the outcome is far from certain. Regulated perps onshore are, in principle, beneficial. The United States has previously sat out, pushing trading activity to offshore venues with little protection and regulatory oversight. Bringing these instruments onshore, into a supervised, transparent framework, would in theory be a net positive for market quality, price discovery, and institutional participation.
Platform profile is worth considering alongside regulatory status. Kalshi's roots are in prediction markets, a category that has historically attracted retail-oriented, high-risk behavior and, before CFTC oversight, raised legitimate questions around business practices and consumer protection. Regulatory approval does confer legal standing but it does not necessarily speak to the quality or sophistication of the underlying client base. The distinction becomes more significant in light of the self-certification provision, which we see as the most consequential element of the CFTC's order.
Ordinarily, an exchange seeking to list a novel product like a crypto perpetual contract must submit it for CFTC review under Section 40.3, a process that can take up to 90 days. CME argues that the Kalshi approval effectively signals that future crypto perpetuals can instead proceed under Section 40.2, which only requires the exchange to self-certify compliance and give one business day's notice, with no individual agency review at all.
By allowing any futures exchange to self-certify similar perpetuals without individual CFTC review, the order effectively opens the door to a wave of new entrants. Kalshi has already used it, self-certifying more than a dozen additional crypto perpetuals that have collectively traded over a billion dollars in volume.[6] What comes next, and on what platforms, will matter as much as the legal outcome of this case.
Conclusion
The CME lawsuit will likely take months at least to resolve. In the interim, the crypto derivatives market has onshore perpetual contracts for the first time, significant volume has already traded, and the legal ground beneath that activity remains contested. The outcome will help define not just the regulatory treatment of perpetual contracts, but the broader question of how quickly and through what process U.S. regulators can adapt to instruments the digital asset market has been using at scale for years.
--
[1] Chicago Mercantile Exchange Inc. v. Michael S. Selig and Commodity Futures Trading Commission, Case 1:26-cv-02157 (D.D.C. 2026), available at https://storage.courtlistener.com/recap/gov.uscourts.dcd.293632/gov.uscourts.dcd.293632.1.0.pdf.
[2] https://www.cftc.gov/PressRoom/PressReleases/9240-26
[3] See supra note 1.
[4] See Chicago Mercantile Exchange Inc. v. Selig (Complaint), No. 1:26-cv-02157(D.D.C. filed June 18, 2026), 111-120; see also Jonathan Ching et al., CFTC Signals Regulation Shift as CME Challenges Classification of Perpetuals as Futures, McDermott Will & Emery (June 24, 2026), https://www.mcdermottlaw.com/insights/cftc-signals-regulation-shift-as-cme-challenges-classification-of-perpetuals-as-futures/.
[5] See CFTC v. HDR Global Trading Ltd. (Complaint), No. 20-cv-8132 (S.D.N.Y. Oct. 1,2020); CFTC v. Eisenberg (Complaint), No. 23-cv-173 (S.D.N.Y. Jan. 9, 2023); Inre Deridex, Inc. (Consent Order), CFTC No. 23-42 (Sept. 7, 2023); CFTC v. Zhao(Complaint), No. 23-cv-1887 (N.D. Ill. Mar. 27, 2023); see also Lowenstein Sandler, FCTM Breaking News: CME Sues CFTC Over Approval of Bitcoin Perpetual Futures Contract (June 2026), https://www.lowenstein.com/news-insights/publications/client-alerts/fctm-breaking-news-cme-sues-cftc-over-approval-of-bitcoin-perpetual-futures-contract-fctm(citing Ku Coin enforcement action).
[6] See CFTC, Policy Statement Concerning the Listing of Perpetual Contracts (May 29,2026); see also Courthouse News Service, CFTC Faces Suit Over Approving Kalshi Bid to List 'Perpetual' Futures Contracts (2026), https://www.courthousenews.com/cftc-faces-suit-over-approving-kalshi-bid-to-list-perpetual-futures-contracts/(noting Kalshi self-certified more than a dozen additional crypto perpetuals generating over $1 billion in trading volume).
--
DISCLAIMER: All views expressed are Hivemind’s own views. The information provided herein has been produced and issued by Hivemind Capital Partners UK LLP and/or Hivemind Capital Partners LLC (“Hivemind”) and is being provided for informational purposes only. This document is not to be distributed or reproduced in any way. This document does not constitute or contain an offer to purchase or sell securities. This document is confidential and intended for the person to whom this was delivered. If you have not received this document from Hivemind you are hereby notified that you have received it from a non-authorized source and you are prohibited from reading, using, retaining, disseminating or copying this material without the prior express written consent of Hivemind. Neither Hivemind nor any of its affiliates or representatives makes any representation or warranty, express or implied, as to the accuracy or completeness of the information contained herein or any other written or oral communication transmitted or made to the recipient. The information contained in this document is current as of the date indicated, and Hivemind undertakes no obligation to update, modify or amend this document or to otherwise notify a reader in the event that any matter stated herein changes or subsequently becomes inaccurate. This document has not been compiled, reviewed, or audited by an independent accountant. Past performance should not be construed as an indicator of future results, and there can be no assurance that historical trends will continue. This document does not include information regarding each investment or investment strategy pursued by the Funds. References to investments included herein should not be construed as a recommendation of any particular investment. Certain information contained herein may constitute “forward-looking statements,” which can be identified by the use of forward-looking terminology such as “may,” “will,” “should,” “expect,” “anticipate,” “project,” “estimate,” “intend,” “continue,” or “believe,” or the negatives thereof, other variations thereon or comparable terminology. All such forward-looking statements are solely statements of opinion, and there is no assurance that they will be predictive of actual events.