The US Senate has passed the DEATH BETS Act. If enacted, the bill would bar federally regulated prediction markets from listing contracts tied to war, terrorism, assassination, US military operations, and certain events determined by a person's death. Next, it goes to the House of Representatives. Until that happens and the bill is fully passed, it is not federal law.
The vote raises a tough question for prediction-market operators, traders, and policymakers: how do you stop markets from creating financial incentives around violence without shutting down legitimate forecasting? The concern isn't just that traders might profit from bad news. It's that contracts tied to military operations or an individual's death could reward people for using confidential information - or, in the worst case, for trying to influence those events.
This article looks at what the Senate-approved bill would cover, why lawmakers introduced it, how it could affect regulated exchanges and users, and what's still up in the air. The Senate's action matters, but it's also only a step. For now, the bill signals where regulation may be headed - not a rule traders should treat as already in force.
What would the DEATH BETS Act prohibit?
The DEATH BETS Act would amend the Commodity Exchange Act. Under the proposal, exchanges registered with the Commodity Futures Trading Commission (CFTC) would be prohibited from listing or clearing specified event contracts. The bill describes contracts tied to war, terrorism, assassination, US military operations, and events primarily determined by a person's death.
This is not the same thing as a broad ban on prediction markets. The bill, as described, doesn't ban all event contracts or all forms of forecasting. For example, contracts on elections, economic indicators, or sports results wouldn't be automatically covered just because they're traded through a prediction-market interface. What matters is the category of event the contract is designed to settle on, and how that settlement works.
A key test would be whether a contract is reasonably expected, at the time it is listed, to settle primarily based on a person's death. That timing matters because it points to how an exchange would evaluate the contract up front, rather than judging it only after the event happens.
The bill would also give the CFTC authority to identify similar activities that should fall under the prohibition. That's aimed at contract designs that don't use an obvious label like "assassination" or "war," but are functionally tied to the same kind of event. The practical question is how broad that "similar activities" category will be.
For users, the main point is that the proposal targets specific contracts and the regulated venue's role in listing or clearing them. The source material does not claim that every platform, every jurisdiction, or every contract involving a public figure would automatically be covered. The final bill language - and any CFTC guidance - would set the exact boundary. Until then, claims that the DEATH BETS Act bans prediction markets wholesale go further than what the Senate vote itself establishes.
Why did lawmakers target prediction markets?
The bill was introduced by Democratic Sen. Adam Schiff in March, amid concerns about possible insider trading linked to US military activity. Those concerns followed reports that six Polymarket traders made about $1 million betting on the timing of US strikes against Iran. Several wagers were reportedly placed only hours before the first reported explosions in Tehran.
That timing understandably raised eyebrows. But suspicion is not proof. The reported profits and timing, on their own, don't show that any trader had classified information, broke the law, or influenced an event. That distinction matters for two reasons: it affects how responsibly the story is reported, and it shapes what a real policy response should try to prevent. Lawmakers are pointing at a risk, not declaring wrongdoing by specific traders.
Schiff's stated concern is that letting people profit from violent events could create incentives to misuse confidential information, harm national security, or encourage violence. The policy issue isn't limited to one set of suspicious trades. Market design matters. Even if markets aggregate information quickly, the way a contract is structured determines what behavior it rewards. When a payout depends on a military strike or a person's death, the risk may be higher than with ordinary event forecasting.
This is also why a simple "markets are efficient" argument isn't enough. Prediction-market prices can reflect what participants believe, but they're not automatically reliable intelligence. Prices can move on public information, speculation, liquidity constraints, or a small number of concentrated positions. In sensitive areas, the cost of a bad incentive may outweigh the informational value of the contract.
There's another side, too: broad restrictions can be hard to define, and they may catch contracts that have legitimate analytical value. Any workable policy needs a way to separate forecasting from wagering structures that create unacceptable incentives - while giving exchanges a clear compliance path. The Senate's action pushes this debate forward, but it doesn't settle how regulators will draw every line.
How could the bill affect exchanges and traders?
If enacted, the bill would mainly affect CFTC-registered exchanges that list or clear covered contracts. Those exchanges would need a process to review proposed markets before launch. They'd have to document settlement mechanics and assess whether a contract fits within the prohibited categories. A label alone wouldn't be enough if the contract's economic substance points to a covered event.
In practice, review could involve questions like:
- What exact event determines whether the contract pays out?
- Does settlement depend primarily on a person's death or a military operation?
- Could the contract be viewed as tied to war, terrorism, or assassination, even if its wording avoids those terms?
- Is the resolution method clear enough to apply consistently?
- Does the contract create a compliance or integrity risk that can't be handled through normal controls?
Those examples show the kind of review an exchange might do, but they are not a complete legal checklist pulled directly from the source material. The actual requirements would depend on the final bill text and, where relevant, CFTC interpretation.
For traders, the likely impact would be that certain markets aren't available on covered exchanges, or are removed before settlement. That's different from a blanket ban on owning digital assets, using blockchain technology, or trading every prediction-market contract. This proposal is aimed at specific event contracts on federally regulated venues, not at crypto "as an asset class."
Blockchain doesn't answer the legal question by itself. A market might use blockchain for trading, settlement, or recordkeeping. But whether it falls under the bill would still depend on the contract and on whether it's listed or cleared by a regulated exchange. It would also be premature to assume that on-chain markets are automatically exempt - or that every decentralized market is automatically covered.
There's also a trade-off in market design. Removing sensitive contracts may reduce harmful incentives, but it can also shrink the range of information a platform aggregates. Exchanges would need rules that are consistent enough to handle edge cases without treating every uncertain or politically charged event as prohibited. Too much caution can suppress useful markets; too little can leave the original risk in place.
What happens next, and what remains uncertain?
The bill is headed to the House of Representatives. It has to pass there before it can go to President Donald Trump for signature. The Senate's procedural step - a voice vote after an amendment by unanimous consent - moves things forward, but it doesn't finish the job. The House could approve the bill as-is, amend it, delay it, or decide not to advance it.
For now, exchanges and traders should keep three buckets separate: the Senate-passed proposal, whatever final version emerges if the House changes it, and the practical rules or interpretations that follow. Each of those stages can shift obligations or clarify the scope. Treating the Senate vote like an active ban risks making decisions based on rules that aren't in force yet.
Several details will shape what comes next. First is how "covered contracts" are defined. Terms like "war," "military operations," and "events primarily determined by death" can be tricky when contracts bundle outcomes or use indirect settlement criteria. Second is how the CFTC uses its authority to identify "similar activities." That could help close loopholes, but market participants will still need clear guidance to evaluate contracts before listing.
Third is how compliance works in real-world operations. Exchanges often have to review lots of proposals, and they can't rely on ad hoc judgments every time. A vague rule may lead to inconsistent outcomes across similar contracts. A rigid checklist may miss new designs that create the same underlying incentive. The final text and any subsequent regulatory action will determine where discretion sits - on the exchange side, the regulator side, or both.
For now, the sensible takeaway is limited. The Senate has approved a bill aimed at specific categories of prediction-market contracts, in part because of concerns about insider trading around military events. This isn't yet an enacted federal ban. And the reported Iran-related bets don't, by themselves, prove wrongdoing. The next real signal will be what the House does - and whether the bill's language changes before it becomes law.
Key takeaways
- The Senate passed the DEATH BETS Act, but it still needs House approval and presidential action before it becomes law.
- The proposal targets specified contracts tied to war, terrorism, assassination, US military operations, and events primarily determined by a person's death.
- The reported bets before US strikes on Iran raised concern, but they don't, by themselves, prove insider trading.
- The bill is not described as a blanket ban on prediction markets, crypto, or blockchain technology.
- The final scope will depend on the final legislation and any relevant CFTC interpretation.
Conclusion
The DEATH BETS Act is a targeted effort to address the risks posed by prediction-market contracts tied to violence and military activity - not a blanket "ban prediction markets" move. The Senate vote suggests lawmakers are focused on how these markets handle sensitive events, especially when there's a concern about nonpublic information or harmful incentives.
The next decision point is the House. Until the bill completes the legislative process, exchanges and users should treat the proposal as distinct from current law - and not treat trading reports as proof of misconduct. The real question isn't whether prediction markets should exist. It's how to draw enforceable boundaries around contracts whose payouts depend on events with serious human and national-security consequences.
