Who decides how a prediction market resolves? This guide explains oracle types, single-source risk, dispute windows, and how Kalshi, Polymarket, and ForecastEx
Every prediction market has an oracle — the source that decides the final outcome. Most traders never think about it until something goes wrong.
Oracle failures aren't rare. Mention markets, pre-taped show markets, and single-source weather contracts have all produced disputed resolutions. This guide explains who decides, how they decide, and where the risk is highest on each major platform.
Outcome determined automatically by a data feed (price, weather station, government release). Fast but vulnerable to source outages, stale data, or single-point failures.
Examples: Weather markets (NOAA feed), crypto price markets (single exchange close)
A panel of researchers or operations staff reviews multiple sources and makes the final call. Slower, but more resilient to single-source failures and ambiguous outcomes.
Examples: ForecastEx macro and political markets
Automated feed triggers initial resolution; a human team or decentralized oracle (e.g., UMA) can override or dispute. Balances speed with error correction.
Examples: Kalshi politics (AP call + ops override), Polymarket (UMA dispute mechanism)
Each platform handles resolution differently. The same event type may carry different oracle risk depending on where you trade it. Compare platform fees and Kalshi vs Polymarket alongside oracle risk.
When a market resolves based on one data source or one reporter, you have no recourse if that source:
How to spot it:
Look for "will resolve to [single source]" language in the contract rules. If only one source is named with no fallback, that's single-source risk.
Categories with highest single-source exposure: Weather markets (NOAA ASOS only), crypto price markets (single exchange close), mention markets (one human reviewer).
From event to payout, seven things have to happen. Each step is a potential failure point.
Event Occurs
The underlying event happens in the real world.
Source Reports
The oracle data source (API, publication, committee) reports the outcome.
Platform Reads Source
The platform retrieves the data — automatically or via human review.
Resolution Check
Automated logic or operations staff verify against contract criteria.
Resolution Posted
Platform marks the market resolved Yes or No.
Dispute Window Opens
Traders have a limited window to challenge the resolution.
Funds Distributed
Winning positions receive payouts after dispute window closes.
Event Occurs
The underlying event happens in the real world.
Source Reports
The oracle data source (API, publication, committee) reports the outcome.
Platform Reads Source
The platform retrieves the data — automatically or via human review.
Resolution Check
Automated logic or operations staff verify against contract criteria.
Resolution Posted
Platform marks the market resolved Yes or No.
Dispute Window Opens
Traders have a limited window to challenge the resolution.
Funds Distributed
Winning positions receive payouts after dispute window closes.
Even when the underlying event is clear, different platforms can post different resolutions — because each contract names a different source. The display chart is not the settlement source, and when they diverge, the contract wins every time.
The #1 source of "feels rigged" complaints on Coinbase and Robinhood: the display chart is NOT the settlement source. They're separate systems — and when they diverge, the contract wins every time.
What You See
What Determines Your Payout
These are the same number 95% of the time. When they differ, you lose money.
What traders see
Weather.com app shows 72°F for the day — traders assume this is the settlement reading.
What the market uses
NOAA station KPHL hourly reading at the specified time — NOT the forecast, NOT the peak, NOT your local app.
"I checked the weather all day, it never hit 75°F. Then the market settled YES. How?"
Kalshi & Polymarket
Resolution sources are clearly documented in each market contract. Weather = NOAA station. Politics = AP call. Finance = official closing price. Verify once per new market category — the pattern is consistent. For the April 2026 Polymarket Paris temperature incident (oracle swapped from Roissy-CDG to Le Bourget), see our dedicated explainer at the Roissy incident page.
Coinbase & Robinhood
The display UX often obscures the settlement source. An extra verification step is required before trading. See how settlement sources are chosen for the 60-second pre-trade check.
You held the right position. The event happened. But the platform resolved the wrong way — or you didn't get paid what you expected. Here's what's actually going on, and what (limited) recourse you have.
Most resolution disputes fall into one of four buckets. Understanding which one you're in changes what you can do about it.
Platform disagreed with public facts
The event clearly happened one way, but the platform resolved differently. This is the rarest case — and the one you have the most recourse on.
→ File a formal dispute. Document your sources.
Rule carveout you didn't read
The platform's resolution criteria had an edge case (death, weather station outage, etc.) that changed the payout. Legally correct by their terms, but feels wrong.
→ Limited recourse. Read market rules before trading large.
Ambiguous event outcome
The underlying event was genuinely unclear — contested news, timing dispute, ambiguous criteria. Both sides have a legitimate case.
→ Dispute mechanism is your path. Outcome uncertain.
You misread the contract terms
The market resolved correctly per the rules, but it didn't match what you expected. This is more common than most traders admit.
→ No recourse. Learn the resolution criteria before next trade.
Real Example: Kalshi Khamenei Market (Feb 28, 2026)
Khamenei died in US-Israeli strikes. Kalshi invoked a "death carveout" on the $54M+ market, resolving at last-traded-price instead of YES. Kalshi reimbursed all fees and net losses — at a total cost to Kalshi of approximately $2.2M — so no trader ended net-negative on their original cost. However, traders who held YES contracts did not receive the full $1.00 payout they expected. Kalshi later codified a new death-settlement rule on March 17, 2026. Traders were made whole on cost, but not on expected winning upside.
How risky is each scenario on the major platforms?
| Scenario | Kalshi | Polymarket | Others | Risk |
|---|---|---|---|---|
| Oracle data source goes offline | Low — internal team reviews manually | Medium — UMA token-holder vote required | High — no fallback defined | Medium Risk |
| News event is ambiguous / disputed | Low — Kalshi Ops makes final call | Low-Med — 2-hour dispute + UMA escalation | High — no formal process | Higher Risk |
| Payout is delayed past expected date | Low — CFTC-regulated, contractual obligation | Low — USDC on-chain, auditable | High — recourse unclear | Medium Risk |
| Platform resolves YES when you think NO | Medium — no formal dispute, support only | Low — $750 USDC bond to escalate to UMA | High — varies widely | Higher Risk |
| Platform reverses resolution after payout | Low — happened once (Khamenei market, refunded) | Very Low — on-chain immutability after UMA | Unknown | Lower Risk |
Identify which bucket you're in
Is this a clear factual error, a rule carveout, an ambiguous event, or a misread contract? Your bucket determines your options. If you misread the contract, recourse is essentially zero.
Document everything immediately
Screenshots of the market page, resolution notice, and your position. Contemporaneous news sources showing the event outcome. Timestamps matter. Most dispute windows are short.
File through official channels — then escalate if needed
Kalshi: Contact support + Discord, then CFTC (cftc.gov/complaint) if no resolution. Polymarket: Post $750 USDC bond to escalate to UMA within the 2-hour window. Others: Support email + public pressure. Never pay third-party "dispute services" — they're scams.
CFTC-regulated platforms (Kalshi) have real accountability. Your dispute isn't ignored — it could become a regulatory matter.
Polymarket's UMA system is decentralized and auditable. If the resolution is verifiably wrong, the bond system rewards you for disputing.
Most resolution disputes are lost by traders, not platforms. Platforms write the rules. Edge cases almost always favor the house interpretation.
"I was right about the outcome" does not mean "I should have won the contract." Market resolution criteria and real-world outcomes are not always identical.
Can a prediction market platform change resolution rules mid-market?
Yes. Under CFTC DCM rules, Designated Contract Markets can invoke existing contract terms that traders may not have noticed — and can also amend rules after the fact. This happened — Kalshi invoked a 'death carveout' clause on the $54M+ Ali Khamenei market (Feb 28, 2026), resolving it at last-traded-price instead of YES despite Khamenei's confirmed death. Kalshi later codified a new death-settlement rule effective March 17, 2026. Always read the full contract rules before entering a position, not just the market title.
What happens if the oracle data source goes offline at resolution time?
This depends on the platform. Kalshi's operations team would make a judgment call, which introduces human discretion. Polymarket would pause the UMA oracle dispute window. The risk is highest in single-source markets (weather, some crypto) where there's no named fallback. Check the contract's Resolution Source field for fallback instructions.
Are pre-taped show markets different from live-event markets?
Yes, structurally. For live events (elections, sports), information emerges publicly in real time. For pre-taped shows (Survivor, The Bachelor, award shows), the outcome is fixed before the market closes — only cast, crew, and their contacts know the result. This creates an inherent structural advantage for insiders. The market doesn't resolve faster with insider knowledge; it prices incorrectly from the moment trading opens.
How are mention markets resolved?
Mention markets (e.g., 'Will [person] be mentioned in [publication] by [date]?') rely on Kalshi Operations staff manually reviewing the named source. One human makes the call. This is the highest-risk oracle structure: no fallback, no multi-source check, no automated verification. If the wording is ambiguous, the operations team has full discretion. Read the exact contract wording on mention markets very carefully.
What is the dispute window on each platform?
Polymarket's UMA oracle gives anyone a 2-hour challenge window after a resolution is proposed; disputing usually requires a $750 USDC bond. Kalshi's rulebook includes an internal market outcome review process, but the platform does not publish a simple trader-facing dispute window in the way Polymarket does. ForecastEx publishes product and regulatory materials; traders should check the specific contract terms and member documentation for any dispute or correction process before trading.
Has a prediction market platform ever reversed a resolution?
Yes. Kalshi invoked its 'death carveout' clause on the Ali Khamenei market (Feb 28, 2026) — $54M+ in contracts resolved at last-traded-price rather than YES after Khamenei was killed in US-Israeli strikes. Kalshi paid ~$2.2M in refunds and later codified a new death-settlement rule. Polymarket has had UMA oracle disputes result in outcome challenges on geopolitical markets. Neither platform publicly tracks resolution controversy history in one place — this is a known transparency gap in the industry.
Why do display charts not match settlement sources?
Display charts are aggregated real-time feeds (TradingView, CoinGecko, platform UI). Settlement sources are contractually defined specific sources (NOAA station KPHL, Binance 1-minute candle, AP race call, BLS.gov release). They usually match. When they don't — in edge cases like exchange outages, timezone differences, or different measurement methodologies — you get a payout surprise. Being surprised by the settlement source is not grounds for reversal; the source was in the contract.
Can I dispute a prediction market resolution I disagree with?
On Polymarket (global markets), yes — you can dispute by posting $750 USDC within the 2-hour window. If successful, you get the bond back plus a portion of the losing side's bond. On Kalshi, there is no formal trader dispute process. You can contact support or post in Discord, but Kalshi's internal team makes all final decisions. For amounts that matter, you can file a CFTC complaint at cftc.gov/complaint.
Can I sue a prediction market platform if they resolve wrong?
For CFTC-regulated platforms like Kalshi, yes — you have legal recourse through CFTC dispute mechanisms. For unregulated platforms, it depends on your jurisdiction and whether you agreed to binding arbitration in their terms of service. For amounts under $5,000, legal action typically costs more than the dispute.
What if the platform is offline or goes bankrupt?
Kalshi (CFTC-regulated) is required to maintain segregated customer funds. Polymarket positions are on-chain USDC — the platform going offline doesn't affect your on-chain balance. Unregulated platforms have no such protections. This is a real risk for smaller platforms.
Resolution Dispute Audit
Per-platform evidence trails and dispute steps
How Markets Settle
Settlement rules and timing by platform
Contract Compare
Are two contracts actually the same bet?
Insider Trading Guide
When insider risk is real vs. overstated
How Concentrated Is Prediction-Market Profit?
Why account-level concentration is different from user-level profitability
How Prediction Markets Work
Fundamentals: contracts, pricing, and mechanics
All Platforms Directory
Compare every CFTC-regulated prediction market
Why Oracle Design Creates Ethical Risks
Single-source oracles, journalist threats, and structural problems
Why Did My Payout Drop?
Cash-out vs. resolution: two separate mechanisms that users conflate
How to Cite Prediction Market Data in Journalism
Timestamp requirements, cross-platform verification, and what prices not to cite