CFTC Sues Utah to Shield Prediction Markets from State Law
The US Commodity Futures Trading Commission has filed suit against Utah state officials in federal court, seeking to block the state from pursuing a $60 million profit-clawback action against prediction market platform Kalshi. The filing, made in the US District Court for the District of Utah, frames the dispute as a straightforward preemption question: Congress designed a federal regulatory scheme for commodity derivatives markets, and no state has the authority to override it. For accounting firms, auditors, and CFOs serving clients with exposure to prediction markets, the case introduces a layer of legal uncertainty that demands careful attention in how event contracts are classified, recorded, and reported.
What the CFTC Actually Filed
Utah's attorney general, Derek Brown, announced plans to sue Kalshi and its affiliates over what the state described as illegally obtained profits from event contracts. The state's theory is that those contracts constitute unlicensed wagering or gambling under Utah law, and it sought to recover up to $60 million.
The CFTC responded by filing its own action in the same district court, naming Utah and Attorney General Brown as defendants. The regulator's core argument is that the event contracts at issue are "swaps" as defined under the Commodity Exchange Act (CEA), and that the exchanges offering them, including Kalshi, are CFTC-registered Designated Contract Markets (DCMs). Under the CEA's preemption provisions, state law cannot restrict a federally registered exchange from offering CFTC-approved products.
The Preemption Argument in Plain Terms
Federal preemption is not a new concept in financial regulation. Congress has repeatedly carved out exclusive federal jurisdiction over specific market structures, including national securities exchanges and futures markets, precisely to prevent a patchwork of 50 conflicting state regimes. The CFTC's lawsuit contends that prediction market event contracts fall squarely inside that carve-out.
CFTC Chair Michael Selig has publicly asserted the regulator's "exclusive jurisdiction" over prediction markets on multiple occasions. The Utah filing is the most direct enforcement of that position to date: a federal regulator going to court not to pursue a private market participant, but to restrain a state government.
Kalshi's Position in the Dispute
Kalshi is a CFTC-registered DCM, meaning it already operates under a federal licence and is subject to ongoing CFTC oversight. The CFTC's lawsuit quotes what appears to be a position from the exchange: "As a national derivatives market overseen by the CFTC, Kalshi answers to federal law, and no single state should have a veto over it." Whether or not the Supreme Court ultimately agrees, Kalshi's registered status is central to the CFTC's legal theory. If the platform were unregistered, the preemption argument would be far weaker.
A Widening Multi-State Conflict
Utah is not acting alone. As of the date of this filing, similar disputes involving prediction markets were pending in New Jersey, Michigan, Ohio, Kentucky, Nevada, Massachusetts, Wisconsin, and New York. In September 2026, New Jersey officials separately moved to intervene in their own case against Kalshi.
Why the Supreme Court May Have the Final Word
With at least nine states now in conflict with the federal regulator over the same jurisdictional question, the legal landscape is fragmented. The CFTC's view is consistent across filings: the CEA preempts state gaming and wagering laws when the contracts in question are CFTC-approved swaps on a registered DCM. But state officials argue that Congress never intended to legalise what are, in their view, gambling products by routing them through a commodities exchange.
As of 28 October 2026, the Supreme Court had not announced whether it would grant certiorari in any of the related cases. Until it does, the conflict will continue to be litigated in multiple district courts simultaneously, producing potentially inconsistent rulings. That uncertainty is itself a compliance risk that firms need to manage.
For broader context on how prediction markets are intersecting with stablecoin infrastructure and raising fresh accounting questions, see our earlier analysis of Phantom and Kalshi prediction markets: stablecoin accounting implications. The regulatory dimension of who controls access to these markets has also surfaced in other contexts, including the Pentagon's ban on insider betting on military operations, which raised parallel questions about information asymmetry and market integrity.
Accounting and Financial Reporting Implications
The legal classification of prediction market contracts matters enormously for how they appear on a balance sheet and in a tax return. The CFTC's position, that these are swaps under the CEA, carries specific accounting consequences.
Classification Under US GAAP
Under ASC 815 (Derivatives and Hedging), a contract that meets the definition of a swap must be recognised at fair value on the balance sheet, with changes in fair value recognised in earnings each period unless the contract qualifies for hedge accounting designation. If event contracts are ultimately confirmed as swaps by the courts, any accounting firm that has been booking client positions as simple wagers or contingent assets will need to revisit that treatment.
The practical challenge is that the legal classification is still contested. Accounting standards require entities to use their best judgement when authoritative guidance does not resolve the question definitively. Firms should document the basis for their chosen treatment now, referencing both the CFTC's stated position and the pending litigation, so that any future restatement or reclassification is defensible.
Revenue and Profit Recognition
Utah's action targets up to $60 million in profits that the state alleges were obtained illegally. Even setting aside the legal question of whether those profits will ultimately be returned, the contingent liability aspect is significant. Under ASC 450 (Contingencies), an entity must assess whether a loss is probable and estimable, and disclose the range of possible loss if it is at least reasonably possible. Kalshi and any affiliates with similar state-level exposure will need to assess each pending state action as a separate contingency.
For accounting firms auditing prediction market platforms or their institutional counterparties, this means requesting management's legal analysis of each state dispute and forming an independent view of whether the contingent liability disclosures in the financial statements are adequate. Robust crypto bookkeeping software that can tag transactions by instrument type, jurisdiction, and regulatory status will be essential for building that audit trail.
Tax Treatment: Swaps vs. Gambling Income
The federal-versus-state classification dispute also has tax consequences. Under US federal tax law, gains and losses on notional principal contracts, which include many swaps, are generally recognised on an accrual basis and reported as ordinary income or loss. Gambling winnings, by contrast, are reported differently, and losses are deductible only to the extent of winnings for most individual taxpayers.
If a court ultimately confirms the CFTC's swap characterisation, entities that have been reporting prediction market gains as gambling income may face amended return obligations. Equally, losses that were written off as gambling losses may need to be restated. The interaction between federal swap treatment and state-level gambling regulations adds another layer: even if the federal position prevails, state income tax returns filed in states that do not recognise the federal preemption argument may require separate analysis.
Practical Steps for Firms and CFOs
Immediate Actions
First, identify exposure. Any client or entity with open positions in CFTC-registered prediction market products should be flagged. The relevant question is not just whether they hold positions in Kalshi specifically, but whether the legal uncertainty affects any DCM-offered event contract.
Second, review accounting treatment. Document whether event contract positions are currently booked as derivatives under ASC 815 or under some other framework. If the treatment is not ASC 815, prepare a memorandum explaining why, referencing the current state of the law.
Third, assess contingent liabilities. For entities operating in any of the nine states currently pursuing or considering litigation, instruct legal counsel to evaluate exposure and provide a written assessment. That assessment feeds directly into the ASC 450 analysis and the notes to the financial statements.
Fourth, review digital asset accounting software configurations. If your firm or your clients use software to categorise and record digital asset or derivatives transactions, confirm that the system can handle the reclassification of event contracts if the legal position changes. A platform that locks in instrument classifications without audit trails will create problems if restatement becomes necessary.
Longer-Term Monitoring
The Supreme Court's decision on whether to hear any of the related cases is the key trigger event. Firms should set calendar alerts for SCOTUS order lists and ensure that their engagement letters for prediction market clients include provisions for additional work if the legal classification changes materially. Given the multi-state nature of the litigation, monthly monitoring of district court dockets in New Jersey, Michigan, Ohio, Kentucky, Nevada, Massachusetts, Wisconsin, and New York is warranted.
Frequently Asked Questions
What is a Designated Contract Market, and why does it matter here?
A Designated Contract Market is an exchange registered with the CFTC under the Commodity Exchange Act. Registration grants the exchange the right to offer futures and swaps to US market participants and subjects it to ongoing CFTC oversight. The CFTC's argument in the Utah case is that this federal registration, and the CFTC's approval of the specific event contracts, triggers preemption of state law. Without DCM status, the preemption claim would be far harder to sustain.
Does the CFTC's preemption argument mean prediction markets are now legal in all states?
Not necessarily. The CFTC's position is that state law cannot restrict a federally registered DCM from offering CFTC-approved products. That is a narrow claim about federal preemption, not a broad legalisation of prediction markets generally. Courts, and potentially the Supreme Court, will determine the limits of that preemption. In the interim, the legal status of specific event contracts varies by jurisdiction.
How should auditors treat the $60 million contingent liability claim against Kalshi?
Under ASC 450, auditors should request management's legal assessment of the probability that the loss will be realised and the range of possible outcomes. If the loss is probable and estimable, it should be accrued. If it is reasonably possible but not probable, disclosure in the notes is required. Given that the CFTC is actively contesting Utah's action, the probability assessment will depend heavily on the legal merits of the preemption argument and should be reassessed as the litigation progresses.
Are event contract gains reportable as swap income or gambling income for federal tax purposes?
This question is unresolved pending judicial clarification. The CFTC's characterisation of event contracts as swaps under the CEA points toward notional principal contract tax treatment, which generally means accrual-basis ordinary income or loss. However, the IRS has not issued specific guidance on prediction market contracts, and the outcome of the multi-state litigation may influence future IRS guidance. Firms should document their chosen treatment and monitor IRS publications closely.
What should firms using crypto bookkeeping software do right now?
Firms should verify that their digital asset accounting software can flag prediction market positions as a distinct instrument category, support reclassification workflows if the legal status changes, and generate audit-ready transaction logs. Any software that auto-classifies event contracts without human review is a risk. Building a manual review checkpoint into the workflow for this specific asset class is the prudent step until the legal position is settled.
Source: Cointelegraph