Share article

Washington is trying to pull a hard plug on "war odds" markets, and the line to watch is simple: can this thing clear a 60 vote Senate reality check, or does it stall as another headline risk for crypto-adjacent prediction apps?

On Tuesday, Democratic Rep. Greg Casar (Texas) and Sen. Chris Murphy (Connecticut) unveiled legislation framed as a direct response to what they described as "highly unusual" conflict related wagers on prediction platforms, specifically tied to tensions involving Israel and Iran. [1] In parallel coverage and Hill chatter, the push is being branded by some lawmakers and staff as the "DEATH BETS Act", a blunt label meant to capture the core target: markets that let users bet on wars, assassinations, and other sensitive state actions. [2]
Crypto markets mostly shrugged. Bitcoin$62,492.80 hovered near $74,529 (up about 0.34%) and Ethereum$1,686.33 around $2,328 (up about 0.96%) at the time of the report, a reminder that this is not a price candle story yet. It is a regulatory overhang story, and those tend to matter only when they start turning into subpoenas, delistings, or platform geofencing.

Enjoy articles without ads?

Register for free and get unlimited access to all articles.

What lawmakers are trying to ban, and why "prediction" is not the shield it used to be

The bill's formal framing is the BETS OFF Act (short for "Banning Event Trading on Sensitive Operations and Federal Functions"). The practical effect is to restrict event contracts tied to sensitive government functions and operations, with a heavy emphasis on armed conflict and assassination style outcomes. [3]
The political argument is not subtle: if you can trade "yes/no" contracts on whether a strike happens, whether a leader dies, or whether a conflict expands, the market can become a magnet for bad incentives. Even if most users are just punting small size, lawmakers are signaling they believe these products can create perverse financial motivation, and worse, a venue for insiders to monetize nonpublic information.
That last point is the real wedge. "Free speech" and "information markets" narratives are easier to defend when the contract is "Will inflation print above X?" They get much harder when the contract is "Will a military operation occur?" and the flow looks like someone traded it with unusually good timing.

The catalyst: "highly unusual" conflict wagers and the insider information problem

Casar and Murphy pointed to unusual bets tied to the US-Israel conflict dynamics with Iran, suggesting the kind of trading pattern that raises two uncomfortable questions at once:

  1. Did someone have advance knowledge of state action, or privileged signals from government channels?
  2. If yes, what agency is responsible for stopping that, and what rulebook applies?

Prediction markets sit in a messy overlap between gambling regulation, commodities derivatives oversight, and platform terms of service. The lawmakers' posture here is to treat sensitive event contracts less like novelty bets and more like a corruption vector, especially when federal employees, contractors, or politically connected actors could theoretically participate.

This is also a reputational fight. Even if a platform can prove it blocks certain users, it still has to answer the broader question: should these markets exist at all?

Who gets hit first: regulated venues, crypto rails, and "information market" startups

If the bill advances, the immediate pressure concentrates in three places:

1) US-facing prediction platforms

Any platform operating with US exposure, or trying to, could be forced to delist sensitive contracts, tighten geoblocking, or rework their entire product taxonomy. The definition game matters. "War" is an obvious target, but lawmakers are telegraphing interest in a broader category of national security and federal function contracts.

2) Onchain primitives that mirror the same bets

Decentralization is not a magic cloak. Even if a smart contract is unstoppable, the ecosystem around it is not: front ends, stablecoin rails, app teams, and liquidity sources can all become pressure points. If regulators get clearer statutory language, it becomes easier to argue that facilitating these markets is not just "neutral tech."

3) Market makers and liquidity providers

Liquidity is the kill switch. If market makers decide the legal and reputational risk is not worth it, spreads widen, depth thins, and volumes slide. That is how regulation bites in practice, not just through courtroom wins.

The political reality check: passage risk versus enforcement risk

Two paths matter, and traders should separate them:

  • Passage risk: The bill must survive committee, horse-trading, and Senate math. Sixty votes is the real "resistance level" if it gets filibustered. If it cannot build bipartisan cover, it may never become law.
  • Enforcement risk: Even without a new statute, the attention itself can invite investigations, guidance, or aggressive interpretations of existing authority. Platforms can get rekt by process costs long before a judge rules.

The nearer-term catalyst is not the final vote. It is whether agencies or lawmakers start naming platforms, markets, or specific contracts in letters, hearings, or referrals.

What would invalidate the crackdown narrative?

The crackdown thesis weakens if two things happen:

  • Platforms credibly prove strong controls (tight KYC where applicable, explicit contract bans, rapid delist policies) and policymakers accept that as sufficient.
  • The bill's language gets narrowed into something symbolic that only targets an extreme corner case, leaving most event contracts untouched.

The opposite is also true. If another set of "too well-timed" bets hits the tape, especially tied to national security events, expect this issue to go from "ethics debate" to "must-pass optics" fast. [4]

Watchlist takeaway

  • Legislative momentum: Committee scheduling and any bipartisan co-sponsors. That is your tell on whether this is real law risk or just narrative pressure.
  • Platform response: Delistings of conflict-related markets, tighter contract review, and changes to US access.
  • Regulatory spillover: Any signs of agency inquiries or public letters that turn "concern" into compliance costs.
  • Second-order impact: Liquidity drying up is the canary. If market makers step back, these contracts become illiquid and effectively dead even without a ban.