If you list, route or build on event contracts, your product review process just got a deadline risk. The Senate has passed a bill that would bar CFTC-registered exchanges from offering contracts tied to war, terrorism, assassination and death. It is not law yet, but operators should treat the contract catalogue as a compliance surface now, not after the House votes.
What happened
According to Cointelegraph, the Senate passed the DEATH BETS Act on Thursday by voice vote, after lawmakers adopted an amendment by unanimous consent. Democratic Sen. Adam Schiff introduced the bill in March. It now goes to the House, and would then need President Donald Trump’s signature.
The bill amends the Commodity Exchange Act. CFTC-registered exchanges could not list or clear contracts tied to war, terrorism, assassination or events primarily determined by a person’s death. It also covers contracts referencing US military operations, and it lets the CFTC identify similar activities that fall under the ban. A contract is barred if, when listed, it is reasonably expected to settle primarily on an individual’s death.
Cointelegraph reports the bill followed insider-trading concerns, after six Polymarket traders reportedly earned $1 million betting on the timing of US strikes against Iran. Some wagers were reportedly placed hours before the first reported explosions in Tehran. CoinDesk and The Block also reported the Senate vote.
Why it matters
The bill targets a category of contract, not a technology. That matters because prediction markets have largely grown by letting users trade on almost any resolvable question. A statute that names whole classes of events, and hands the CFTC power to extend the list, moves the line from regulator discretion to written law.
The stated rationale is also telling. Backers frame the issue as misuse of nonpublic information and incentives for violence, not consumer protection alone. The likely effect is closer scrutiny of any market where a small group could know the outcome in advance. A voice vote suggests little organised opposition in the Senate, though the House is untested.
The scope is limited to federally regulated venues, as the bill is written. How it would apply to offshore or onchain platforms is not something the reporting settles, so crypto teams should not assume they sit outside the debate. Our crypto coverage has tracked how US rules keep reaching new product types, including stock perpetuals.
What it means for you
If you run or integrate a CFTC-registered venue, start with an inventory. Tag every live and planned contract by the event it settles on, and flag anything tied to conflict, military action, violence or a person’s death. The clause on contracts that settle primarily on a death is the hardest to judge, so ask counsel how it reads for borderline wording.
If you are a fintech, broker or wallet that distributes event contracts from a third party, ask your vendor three things: how it screens new listings, what it would do with open positions if a category were banned, and how fast it can delist. Put the answers in the contract, along with settlement and refund terms.
Engineering teams should make contract categories a first-class field, not free text. A structured taxonomy lets you disable a class of markets with a config change instead of a release. Add surveillance for unusual trading ahead of public events, since insider activity drove this bill.
Founders planning a prediction product should avoid building a roadmap around security or political-violence markets. Budget for legal review of each new contract type.
What to watch
- Whether the House takes up the bill, and whether it changes the text, which would force another Senate vote.
- Any CFTC statement on how it would use its authority to identify similar banned activities.
- Whether platforms pull or reword existing war and death contracts before the bill is final.
- Fresh insider-trading allegations, which would add pressure on lawmakers and regulators.


