Indian Premier League: Sunrisers Hyderabad vs Rajasthan Royals
Platform
Polymarket
Outcome (as resolved)
Sunrisers Hyderabad
Reported volume
$3.0M
Closed
2026-04-13
About
IPL
Opened
2026-04-08
Resolved: platform · on-chain
2026-04-13 · 2026-04-13
Data quality
MEDIUM
Price history
Market price of “Sunrisers Hyderabad” (3 observations, as served by Polymarket Data API v2). A price is a market-implied estimate, not an objective probability.
What did the market price, and when?
Price of “Sunrisers Hyderabad” at fixed times before the earlier of the scheduled end and the actual close. A price is only used once its time bucket had ended, so nothing here peeks ahead.
30 days before
market not yet listed
14 days before
market not yet listed
7 days before
market not yet listed
72 hours before
market not yet listed
48 hours before
finer than stored data
24 hours before
finer than stored data
12 hours before
finer than stored data
6 hours before
finer than stored data
1 hour before
finer than stored data
Last available price
100%
Outcome
Sunrisers Hyderabad
No causal relationship is established between any price movement and any news event. Temporal order is not causation.
Settlement record on Polygon
Positions in this market are redeemed against a payout record written to the Conditional Tokens contract on Polygon. ARGUS reads that record directly and compares it with what Polymarket reports.
MATCHOn-chain record matches the platform's outcome
Outcome implied on-chain
Sunrisers Hyderabad (payout numerators [1, 0])
Settled
Polygon block 8,54,97,831 · 2026-04-13 21:28:19 UTC
Three readings are compared: Gamma final prices, the Data API's resolution row, and the Conditional Tokens contract's settlement record on Polygon. VERIFIED means all available readings imply the same outcome.
This does not establish
that the real-world event did or did not happen — this is the platform's oracle determination under its own rules text
Polygon block 85,497,831 (2026-04-13T21:28:19Z) records the Conditional Tokens contract's settlement of the condition behind “Indian Premier League: Sunrisers Hyderabad vs Rajasthan Royals”: payout numerators [1, 0], i.e. “Sunrisers Hyderabad”.
The CTF contract emits ConditionResolution once per condition, when the oracle reports payouts; it is the record positions are redeemed against. The payout numerators map to the market's outcomes in order.
This does not establish
that the real-world event happened as the question describes — the chain records what the oracle reported
who held or traded positions in this market, or where they are
agreement of a second, independent RPC provider (this record was read from one provider)
Resolution rules (Polymarket's text)
Quoted from the platform for this market only; the rules, not the title, decide the outcome. Source page ↗
This market refers to the cricket match between Sunrisers Hyderabad and Rajasthan Royals scheduled for April 13 2026 in Indian Premier League.
This market resolves according to the finalized match result as published by https://www.espncricinfo.com/.
DLS/DRS, over-rate penalties, forfeit/walkover, or any other on-field ruling that leads the competition to declare a winner are treated as ordinary wins.
If the match ends tied and the playing conditions provide an on-field tiebreak (e.g., Super Over), the winner determined by that tiebreak will be used for resolution. If the match ends tied and no on-field tiebreak is used or available under the playing conditions (e.g., group-stage ODI with no Super Over), the market will resolve 50-50.
If the match is postponed/rescheduled, the market remains open until the listed fixture is completed. If the match is permanently canceled or abandoned or otherwise is completed without a winner, the market resolves 50-50.
The primary resolution source for this market is the official statistics of the event as recognized by the governing body or event organizers. However, if the governing body or event organizers have not published final match statistics within 2 hours after the event's conclusion, a consensus of credible reporting may be used instead.