This tracker is a demonstration of the output this platform is being built to deliver. It came out of an ungoverned dry run — sourcing and review only, with no policy enforcement, evaluation gates or publish controls. Nothing here is verified, and none of it is legal advice.
← Back to the project
One court of appeals says the federal exchange licence wins. Six district courts say the states do. Nothing is settled, and the Supreme Court has not been asked yet — the deadline is 3 September.
Written for readers who are not lawyers. Every claim below is carried in the case records further down, each with a primary source.
A federally licensed exchange now sells contracts on who wins Sunday's game. Forty-eight states call that a bet. Congress never said which one is right.
You buy a contract that pays out if a stated event happens — a candidate wins, inflation lands above a number, a team covers. Kalshi, Polymarket US, Crypto.com and Robinhood Derivatives run these as federally regulated exchanges, licensed by the Commodity Futures Trading Commission the same way a soybean futures market is licensed.
The Commodity Exchange Act gives the CFTC “exclusive jurisdiction” over swaps and futures traded on federally licensed exchanges.
By every tool they have, often several at once in the same state.
Kalshi beats the CFTC over election contracts in federal court. The agency drops its appeal. Election markets go live.
Sports event contracts launch. Nevada, then a wave of other gaming regulators, issue cease-and-desist orders.
Maryland becomes the first federal court to side with a state. Nevada dissolves its own earlier injunction: these are not swaps.
The Third Circuit rules for Kalshi in Flaherty — still the only federal appellate decision on the merits.
The CFTC starts suing states. Arizona charges Kalshi criminally. Minnesota bans prediction markets outright.
Utah enters final judgment for the state; New York and Wisconsin deny relief; Minnesota's ban is enjoined. Six circuits now hold appeals.
Geography and doctrine disagree. The map colors states by the posture that controls them; the index colors the courts of appeals. Select either — the other follows.
Operational status answers the compliance question — can this platform take the order in this state today. Posture answers where the law is heading. They are not the same field, and they can disagree.
| Controlling case |
|---|
Every status and posture cell above links to at least one Tier‑1 source in the state panel. States with no tracked activity are absent from this table rather than shown as neutral — absence is not a finding.
Every matter carries a controlling issue and its secondary issues, drawn from a fixed vocabulary. Click anything below: the panel names the matters, and the case record further down filters to match.
One record per case, one posture per case. If a state and a circuit disagree on screen, that is a data error — report it.
The same order can reach one platform and not another. This view reads the record the other way round — by who is actually bound.
Qualitative only. No market-derived number ships in v1 — the space below the reading is deliberately held open for one, with its methodology and its reflexivity caveat.
Factors are the whole method. There is no weighting, no model and no score behind this reading — if a factor changes, the reading is re-argued in the open and the change appears as a draft on ops. before it appears here.
Not legal advice. This site publishes general legal information about pending litigation. Reading it creates no attorney-client relationship, and nothing here is a substitute for counsel licensed in your jurisdiction.
Built by AI, approved by a human. Every row on this page was drafted by an autonomous pipeline and published only after a named human cleared the Approval Gate. The gate is currently set to HITL; autonomous mode is off. Each published item carries its provenance label at the point of use, frozen at publish time.
Drafts are not here. Proposed changes — including two pending right now — live in full on ops., labelled not live. The tracker never renders an unapproved draft.
Powered by Bizmation.
PML‑C‑2026‑0184 — and the resulting draft, approved or rejected, is visible on
ops. with its reason attached.
The run log, full evidence for every run, the pending drafts in full text, the current approval mode and its audit trail, and the nine-layer governance explainer. No login. If you want to check whether this tracker deserves the trust it asks for, that is where you check.