A Perpetual Doesn’t Have to Expire: The CFTC, CME, and the Quiet Fight Over Kalshi’s Bitcoin Contract

On a late-summer federal docket in Washington, D.C., the Commodity Futures Trading Commission asked a judge to dismiss CME’s challenge to Kalshi’s Bitcoin perpetual futures. There was no press conference, no new guidance, only a procedural motion asking the court not to define the instrument too carefully. That motion matters more than the product launch it is meant to protect, because it exposes something the market rarely wants to discuss: U.S. derivatives law still sorts financial instruments by expiration date, while the code that inspired Kalshi’s product sorts them by something else entirely. The contract at the center of the fight is Kalshi’s BTCPERP, which received CFTC approval on May 29, 2024. It is cash-settled, designed to track the price of Bitcoin, and, most importantly, it has no maturity date. Traders can hold positions indefinitely. To keep the perpetual price from drifting away from the spot price, the contract uses a funding rate: periodically, longs pay shorts, or shorts pay longs, depending on which side is crowded. The mechanism works as an economic pressure valve, not as a promise to deliver an asset on a specific day. This is standard equipment in crypto-native exchanges, but it is unfamiliar territory inside the regulatory walls that govern traditional futures markets. Let’s slow down and name the legal conflict clearly. Under the Commodity Exchange Act, a future is generally a standardized contract for delivery at a future date. A swap, by contrast, is a bilateral agreement that exchanges cash flows over time and often has no fixed delivery obligation. The two categories are governed by different clearing, reporting, and trading rules. CME argues that because Kalshi’s contract never expires, and because funding payments continue indefinitely, the product is functionally a swap rather than a future. If CME is right, then CFTC approval of the contract as a futures product exceeds the agency’s authority. If Kalshi and CFTC are right, the product is simply a new species of future that the law never anticipated. The easiest way to dismiss this fight is to call it a semantic quarrel. That would be a mistake. Legal categories are infrastructure. They determine which clearinghouse is responsible, what margin rules apply, who can trade, and what happens if a participant defaults. When a startup steps into the gap between code and law, the label attached to its product becomes as important as the product itself. Kalshi’s perpetual contract is not a technological breakthrough. The perpetual was invented years ago, and BitMEX gave it mainstream crypto visibility in 2016. The innovation here, if we can call it that, is packaging a proven crypto-native mechanism inside an existing CFTC-regulated product category. This is precisely why the dispute is so uncomfortable for regulators. The funding-rate formula that makes Kalshi’s product work is not exotic. It was shaped in markets with deep liquidity and round-the-clock trading. In those venues, arbitrageurs keep the price close to spot because their own profit depends on it. But when the same mechanism is transplanted into a newly regulated exchange with modest order flow, the formula suddenly needs a different kind of scrutiny. The market may be thinner. The arbitrage community may be smaller. The index that defines the spot price may be easy to game or slow to update. A funding-rate formula that behaves elegantly in normal conditions can become a silent tax on one side of the trade when liquidity disappears. I say this from experience, not from theory. During the DeFi summer of 2020, I spent hundreds of hours manually auditing interest rate models in lending protocols, including the early scripts that later became Aave. The formulas looked deterministic, even boring. They worked beautifully while liquidity was abundant. Then sharp liquidation cascades arrived, and the invisible assumptions inside those formulas suddenly mattered in ways the code’s documentation did not prepare users for. I have never forgotten that lesson: a formula can be mathematically correct and still fail when the market surrounding it stops cooperating. The same risk now lives inside Kalshi’s perpetual futures, not because the mechanism is fraudulent, but because no funding rate can save a market with insufficient depth. That market depth issue is one reason the CFTC’s dismissal bid deserves attention. The agency argues that CME’s complaint overstates the competitive harm, and it points out that CME could have listed a similar product itself. There is also a quieter data point buried in the briefing: CME’s own Bitcoin futures volumes were higher in June and August of 2024 than they were in May, the month Kalshi’s perpetual contract was approved. If Kalshi’s new product were truly draining CME’s business, the incumbent’s trading volumes should tell a different story. Instead, the launch seems to have expanded general attention to Bitcoin derivatives, benefiting the entire market while threatening CME’s status as the only venue offering regulated exposure. Behind the CFTC’s legal position, however, is another shadow. In 2024, the Supreme Court ended Chevron deference, meaning courts no longer automatically accept an agency’s interpretation of an ambiguous statute. That decision changed the risk calculation for every federal regulator. A CFTC approval of a novel product can now be challenged by any rival that disagrees with the agency’s reading of its own rules. In this environment, the CFTC’s desire to have the case dismissed without a merits ruling is not just strategic laziness. It is an attempt to avoid giving a future court the opportunity to define the word future in a narrower way. Sometimes regulatory silence is the most valuable form of regulatory protection. Now let’s consider the contrarian angle that most market commentary misses. The lawsuit may not be a moat defense by CME. It may be a roadmap-building exercise. If the court eventually confirms that a perpetual contract with a funding rate can lawfully be classified as a future, then CME is free to launch its own institutional-grade Bitcoin perpetual product. CME has deeper relationships, greater capital, and a customer base that already trusts its clearinghouse. A legal victory for Kalshi would not protect Kalshi from that outcome. It would instead create the very clarity that allows a larger competitor to enter the market and squeeze the startup out. If CME wins under a swap classification, the outcome is different, but CME has the balance sheet and legal team to adapt to either category. A small challenger cannot say the same. The lawsuit therefore works as a hedge: it either blocks a rival’s new category or confirms the legal foundation CME needs to build its own version. This should change how we evaluate the word victory. A ruling in Kalshi’s favor is not automatically a market win for Kalshi. Approval is merely permission to participate in a much larger competition. The real battlefield will be open interest, order book depth, price deviation from the spot index, and the behavior of funding rates under stress. Those are not matters a court can resolve. A judge can decide whether a perpetual contract is a future or a swap, but a judge cannot decide whether a new market has enough honest liquidity to survive its first serious drawdown. In my view, this is the heart of the matter. The legal language of futures and swaps was written for instruments with life cycles. A perpetual contract, by definition, refuses to die. It does not mature, it does not deliver, and it does not ask its holders to reckon with the future in the way traditional futures do. Instead, it creates an endless present. That is not inherently dangerous, but it demands more from its infrastructure rather than less. A contract that cannot expire must be able to withstand withdrawal, manipulation, and panic for as long as it remains open. The margin model must be strong. The funding-rate calculation must be transparent. The liquidation engine must not fail at the moment it is most needed. These are engineering problems, not legal classification problems. This is also where the deepest values of open-source culture become relevant. I have spent much of my career trying to teach non-technical users that code is not a promise, it is an argument. Code can be audited. Rules can be tested. But official approval is not the same as community verification. A regulator can approve a product without exposing its assumptions to adversarial review. A legal win can preserve a product’s right to exist without proving that the product deserves the user’s trust. Code is law, but ethics is soul. A contract can be perfectly classified and still ethically hollow if its inner mechanics are unintelligible to the people trading it. Transparency alone does not solve that problem. Too often we assume that open code or published settlement rules are enough. They are not. Transparency is the beginning of accountability, not a substitute for it. A transparently described flawed engine does not become safer simply because the flaw is visible. It only becomes easier to detect, and detection only matters if the people using the product are equipped to understand what they are seeing. This is why I keep returning to a simple conviction: trust is not made by disclosure. Trust is made by infrastructure that behaves decently when the market stops behaving predictably. Transparency isn’t the oxygen of trust; it is merely the window through which trust can be observed. So what should a responsible observer watch as this case unfolds? The first deadline is procedural but meaningful. CME must respond to the motion to dismiss by October 2. That response will tell us whether CME is genuinely trying to establish a broader legal principle or merely trying to slow down a competitor. More interesting than the legal language, however, is CME’s silence outside the courtroom. If CME announces its own Bitcoin perpetual contract, even quietly, then the litigation is not about defending an existing market. It is about creating the conditions for CME’s next act. The legal question will become irrelevant, because the court will have given both companies the same future, and the market will decide which product deserves to exist. The deeper lesson from this case is not about Kalshi or CME. It is about how slowly legal systems respond when technology outgrows their categories. Bitcoin was designed to be borderless. Perpetual contracts were designed to be timeless. When those designs meet a regulatory framework built around dates and settlement, the collision is inevitable. A court will eventually write a definition that resolves the conflict, but that definition will not be the final answer. Legal clarity can create a space for innovation, but it cannot force a product to be useful, honest, or dignified. The question before the judge is whether a perpetual future is still a future. The question before the market is more difficult. Should a financial instrument that never expires be trusted just because someone with authority decided what to call it? The judge will rule on language. The traders, the liquidity providers, and the next bear market will rule on everything else.