What the Kalshi vs Polymarket feud means for legal risk

Risk Digest status

Current as of Aug. 4, 2026, Q3 2026. This is a legal-risk record, not legal advice. The practical question is not which founder won a public-relations exchange; it is which filings, enforcement theories, state actions, and rulemaking records now affect platforms, clients, funds, employees, and counterparties.

The exposure map below separates docketed or official events from estimates, advocacy letters, and reported feud material. That distinction matters: a letter to the CFTC is not an enforcement action; a behavioral study is not an agency finding; a criminal complaint is not a conviction; and a regulated-exchange posture does not, by itself, extinguish state gambling theories.

The feud is a jurisdictional boundary fight

The cleanest legal description is a contest between a CFTC-facing event-contract exchange model and an offshore platform model that says U.S. users are excluded. The public rhetoric is loud because the boundary is economically important, but the filings matter because the legal consequences turn on narrower questions: where the user is, what the contract is, whether the platform offered it into the United States, whether the contract is a swap, and whether a state can still characterize the activity as unlawful gambling.

Kalshi’s posture is not simply “legal” in the abstract; it is a regulated-exchange posture that still depends on contract review, federal-state allocation, market surveillance, and product-specific limits. Polymarket’s posture is not simply “offshore” in the abstract; it depends on whether U.S. access is actually blocked and whether U.S.-facing conduct can be shown. That is why the Lopes Lara letter and the Crane study are not side material. They are attempts to make the offshore-access question concrete.

The D.C. Circuit’s KalshiEX v. CFTC opinion sits in the background as part of Kalshi’s federal regulatory path, but it does not answer every question now showing up in state suits or offshore-access arguments. [13] Counsel should resist reducing the map to a binary label. The operative risk assessment has to ask which authority is being invoked, against whom, for which contracts, in which forum, and based on which conduct.

CFTC and offshore access

The Apr. 30 Lopes Lara letter is important because it converts feud rhetoric into an agency-facing enforcement request. As reported by Sportico, the letter urged the CFTC to act against offshore venues that allegedly allow U.S. users to access prediction markets through VPNs. Sportico’s Jun. 11 report also matters for what it did not show: by that date, the push had not yet moved the CFTC into the requested action. [1]

That leaves the letter in a middle category. It is not a complaint filed by the agency, and it is not an order. It is still a risk event. For an offshore or offshore-adjacent platform, the letter identifies the facts a competitor wants regulators to test: IP location, VPN patterns, payment rails, affiliate or influencer messaging, user attestations, account reopening, and whether exclusion controls work in practice.

The Crane study, as reported by Wired, supplies the number most likely to be quoted carelessly: about 30% of Polymarket volume characterized as U.S.-based, with estimated trading volume of $10.6 billion to $26.7 billion from May 2025 through April 2026. Wired framed the method as a behavioral proxy, not direct regulatory proof, and reported the funding context: the Coalition that funded the study included Kalshi, Coinbase, and Crypto.com as members, while Polymarket was excluded. [2]

That does not make the study irrelevant. It makes it a diligence and enforcement-pressure document rather than a settled factual finding. A regulator, state attorney general, plaintiff, counterparty, or bank risk team could use the study to justify asking for access logs, geolocation controls, KYC procedures, VPN detection, sanctions screening, and marketing files. A careful memo should not state that the CFTC has found 30% U.S. volume unless an agency record actually says so.

The historical anchor is the Jan. 3, 2022 CFTC order against Blockratize, Inc., doing business as Polymarket.com. The CFTC said Polymarket offered off-exchange event-based binary options contracts and failed to obtain required designation or registration, and ordered a $1.4 million civil monetary penalty. [6] That order is the reason “offshore” should not be written as a complete answer in a risk memo.

The June 2026 rulemaking report adds a different kind of pressure. Reuters reported on Jun. 10, 2026 that the CFTC proposed new rules to govern prediction markets. [7] A proposal does not decide existing cases, but it changes the drafting environment for product approvals, customer disclosures, surveillance procedures, and board-level risk reporting. It also makes stale advice more dangerous: a 2024 contract analysis may not answer a 2026 launch question.

Van Dyke is the enforcement fact counsel should not bury

The Van Dyke matter is the strongest current example tying prediction-market trading to an insider-trading-style theory. DOJ announced on Apr. 23, 2026 that a U.S. soldier had been charged with using classified information to profit from prediction-market bets, and DOJ stated that the alleged profit was approximately $409,881. [3] A contemporaneous Lowenstein client alert described related CFTC and Kalshi enforcement actions and used the formulation “more than $404,000,” which is close but not identical. [4]

That discrepancy is small in business terms and significant in legal writing terms. If a memo cites DOJ, use DOJ’s figure and label it as DOJ’s allegation. If a memo cites the CFTC posture through a client alert, do not silently swap in DOJ’s number. The larger point is not the exact dollar amount; it is that prediction-market positions can be treated as the economic instrument through which allegedly confidential or classified information is monetized.

The reported motion-to-dismiss issue is even more important for platform risk. DeFi Rate reported on Jul. 7, 2026 that the Van Dyke motion challenged whether Polymarket trades were swaps. [5] Because that report is secondary coverage of court filings, the docket should be checked directly before filing or publishing a litigation memo. But the legal significance is clear enough: the classification dispute is no longer only a policy debate or marketing distinction. It is being used as a defense line in an enforcement context.

If an event contract is treated as a swap, CEA antifraud, manipulation, registration, platform, and reporting theories become easier to frame. If it is treated as a bet outside that framework, federal derivatives law may not supply the same route, while state gambling and criminal theories may become more prominent. The current record does not resolve that fork. It makes the fork operational.

For employers, funds, crypto firms, political-risk shops, government contractors, and media organizations, the lesson is immediate. A prediction-market account can create a personal-trading problem even when the platform question remains unsettled. Policies that already cover securities, derivatives, confidential information, and restricted lists should be checked for event contracts, classified or MNPI-adjacent information, and employee use of offshore venues.

State gambling suits are the preemption flank

The state litigation lane shows why Kalshi’s regulated-exchange posture does not end the jurisdictional fight. On Jun. 23, 2026, CNBC reported that the CFTC sued Kentucky over actions against prediction markets. [8] The CFTC also identified a Wisconsin-related action in Press Release 9220-26. [9] Those federal actions belong in the same risk file as state attorney general actions, because they ask who gets to police the same products when federal derivatives oversight and state gambling law collide.

New York then made the point still sharper. On Jul. 31, 2026, Governor Hochul and Attorney General James announced that New York had sued Kalshi. [10] For a deeper state-specific record, see the New York Kalshi lawsuit risk digest. The key point for this record is narrower: a CFTC-facing exchange can still face a state attorney general’s gambling theory, and a preemption argument remains a litigation position rather than an automatic shield.

This is the flank that counterparties often underestimate. A platform may be comfortable with its federal regulatory theory and still create state-by-state distribution, marketing, payment-processing, and customer-support exposure. Counsel reviewing sports, elections, macroeconomic, entertainment, or geopolitical contracts should ask not only whether the exchange has a federal pathway, but also whether particular states have taken a contrary gambling-law position.

Adjacent records are useful because the state-law posture is moving faster than most product teams’ launch calendars. The Washington gambling injunction analysis and the Kalshi student-loan contracts legality note are relevant not because every contract is identical, but because each dispute tests the same habit of mind: avoid treating federal registration, product novelty, or contract terminology as dispositive.

What to do with the feud material

The influencer campaign, deleted podcast segment, trademark skirmishes, and personality coverage are not irrelevant. They are just not the legal center of the file. TechCrunch reported that Kalshi’s CEO admitted enlisting influencers to criticize Polymarket in a now-deleted podcast segment. [11] NPR later framed the rivalry through controversy over Iran-war prediction markets. [12] Those accounts help explain the escalation environment, especially why public pressure and competitor positioning moved toward the CFTC.

They do not, on their own, establish a regulatory violation. A deleted clip may become relevant if it bears on intent, market messaging, communications with influencers, or unfair-competition allegations. A trademark filing may matter if it produces a registration dispute or litigation. Public criticism may matter if it becomes part of an agency submission or investor diligence file. Without that bridge, feud color is noise.

Exposure frame for counsel and compliance teams

As of Q3 2026, the practical review should be organized by role rather than by allegiance to Kalshi or Polymarket.

• For a platform: document registration status, contract-listing basis, geofencing controls, U.S. access testing, VPN detection, sanctions and KYC procedures, market-surveillance rules, influencer and affiliate controls, and state-by-state availability.
• For an offshore venue or service provider: assume that user-location evidence, payments, marketing, customer support, and account-reopening workflows may be requested if the CFTC or a state attorney general tests U.S. access.
• For a fund, employer, government contractor, or media organization: update personal-trading, confidential-information, restricted-list, and outside-account policies so event contracts are not left outside the compliance perimeter by accident.
• For banks, payment processors, custodians, market-data vendors, and API partners: diligence should distinguish CFTC registration, offshore exclusion, state gambling exposure, and contract category. A vendor answer on one of those points does not answer the others.
• For litigators and KM teams: keep a source hierarchy. Agency orders, complaints, court filings, and official press releases outrank rivalry profiles and trade coverage. Secondary reporting can be useful, but the docket controls.

Two adjacent risk comparisons may help if the review extends beyond these two platforms: the June 2026 CFTC sports prediction-market rulemaking compliance read and the Robinhood prediction-markets legal-threats analysis map the same federal, state, product, and intermediary issues in neighboring contexts.

The current legal record supports a limited conclusion. The Kalshi-Polymarket feud has already produced concrete consequences: an enforcement request to the CFTC, a contested offshore-access narrative, a prior Polymarket CFTC penalty order, the Van Dyke criminal and civil enforcement posture, state gambling litigation against Kalshi, federal actions against state interference, and a live CFTC rulemaking environment. It does not yet resolve the central classification vulnerability. Regulated status reduces some risks; offshore exclusion creates others; both platforms remain exposed while the swaps-versus-bets boundary and the state-federal jurisdiction fight remain live.

References

1. Kalshi's Push to Punish Polymarket Has Yet to Move CFTC, Sportico, Jun. 11, 2026
2. Americans Are Trading Billions of Dollars on Polymarket's Banned Offshore Platform, Wired
3. U.S. Soldier Charged with Using Classified Information to Profit from Prediction Market Bets, U.S. Department of Justice, Apr. 23, 2026
4. CFTC and Kalshi Announce Enforcement Actions Targeting Prediction Markets, Lowenstein Sandler, Apr. 24, 2026
5. CFTC’s First Event Contract Insider Trading Lawsuit Challenged Whether Polymarket Trades Are Swaps, DeFi Rate, Jul. 7, 2026
6. CFTC Orders Event-Based Binary Options Markets Operator to Pay $1.4 Million Penalty, CFTC, Jan. 3, 2022
7. CFTC proposes new rules to govern prediction markets, WSJ reports, Reuters, Jun. 10, 2026
8. CFTC sues Kentucky over actions against prediction markets, CNBC, Jun. 23, 2026
9. CFTC v. Wisconsin, CFTC Press Release 9220-26
10. Governor Hochul and Attorney General James Announce New York Has Sued Kalshi, New York Attorney General, Jul. 31, 2026
11. Kalshi CEO admits enlisting influencers to dis Polymarket in a now-deleted podcast segment, TechCrunch, Dec. 13, 2024
12. Iran war Kalshi Polymarket feud, NPR, Mar. 6, 2026
13. KalshiEX LLC v. CFTC, Justia, Oct. 2, 2024