Loading shell…
SportsExpires Apr 24, 2026

Game 2: Both Teams Beat Roshan?

Probability

10¢

1h

-40.0pp

24h

-40.5pp

24h Vol

$17.17

Liquidity

$326.50

Probability (last 7 days)

+0.0pp 7d
Apr 23, 2026, 17:00Apr 25, 2026, 13:42
updated 0s ago·src:Polymarket CLOB

Why did it move?

Structured · 5 factors
  1. 1

    Down 41pp over 24h

    Now 10¢; -40.0pp in the last hour.

  2. 2

    Resolution-risk signal firing

    Market has reached expiry. Watch the UMA dispute window.

  3. 3

    Wide spread — 20.0¢

    Bid-ask spread is wide enough that intraday moves overstate any tradeable edge. Most of the headline pp move would be eaten by spread on a market order.

  4. 4

    Past expiry — awaiting resolution

    Market is past its end date. Any price move now is a settlement / dispute artefact, not new information.

  5. 5

    UMA status: proposed

    An open UMA dispute or pending oracle vote can move price independently of underlying odds. Wait for settlement before treating the line as the market view.

What to track next

  • Verify the resolution source on this page — exchange feed, official release, news consensus — before treating any move as new information.
  • Wait for the UMA proposal to settle (current status: proposed) — price moves now reflect oracle dynamics, not odds.

Verification actions only — never trade recommendations.

Each factor is grounded in a single named metric you can verify on this page — probability, volume, liquidity, signal, resolution state. No predictions, no prose hallucinations.

AI prose summary

 

Prose narration of the same metrics shown in the structured breakdown above. Cites only the market data on this page — no news, no predictions. Use the structured factors as the canonical answer; this is here for readability.

Timeline — news, trades, signals, price moves

AllTradesSignalsPrice
  • 13:42Signal

    Signal · Resolution risk

    Market has reached expiry. Watch the UMA dispute window.

    HIGH
  • 19:30Resolve

    Market resolved 18h ago

    HIGH
updated 0s ago·src:Polymarket CLOB·Polymarket Data

Active signals

Recent Trades

No recent trades visible from the Data API for this market.

updated 0s ago·src:Polymarket Data

Market Description

This market is about whether both teams kill Roshan at least once during Game 2. Roshan is a powerful neutral boss in Dota 2 that spawns at the start of the game and respawns 8–11 minutes after each death, dropping the Aegis of the Immortal and other valuable items. This market will resolve to "Yes" if both South America Rejects and 1win each kill Roshan at least once during Game 2. This market will resolve to "No" if either team (or both teams) does not kill Roshan during Game 2. If the match is canceled (not played at all) or is delayed beyond 7 days from the scheduled date, this market will resolve to 50-50. If Game 2 is never played due to forfeit, disqualification, or walkover, this market will resolve to 50-50. If Game 2 is not played because the series result has already been determined (e.g., a team clinches the series before Game 2 is needed), this market will resolve to 50-50. If Game 2 begins but is not completed and ends via forfeit, this market will resolve based on whether both teams had killed Roshan prior to stoppage. If the condition was not met, this market will resolve to "No". If Game 2 is remade, resolution will be based on the remade game only. The resolution source for this market will be official information from https://www.dotabuff.com. However, if https://www.dotabuff.com has not published final results within 2 hours after the event's conclusion, a consensus of credible reporting may be used instead including video evidence.

Resolution & Risk

HIGH risk
End date
Apr 24, 2026
UMA status
proposed
Resolution source
https://www.dotabuff.comNews consensus
Market type
Binary
  • UMA status: proposed
  • Market expires Apr 24, 2026 — dispute window active.
  • Wide spread (20.0¢) — liquidity risk on entry/exit.
Read full market rules on Polymarket

Alerts

¢
Deliver

In-app banners work now. Email / Telegram / Discord delivery lands when the backend alert dispatcher ships (needs RESEND_API_KEY + per-user webhook storage).