Polymarket resolution isn’t just “read the rules and apply them.” Every market ends up leaning on a body of precedent — decisions from prior UMA proposals and disputes that settle how ambiguous cases get handled. Traders who don’t know the precedents regularly get blindsided by resolutions that felt “obvious” their way but came out the other way.
This article covers the 8 precedents I’ve seen matter most, each with a real market they came from. It’s not comprehensive — the community archive runs to dozens of categories — but these 8 cover the cases that come up again and again.
A quick note before diving in: market-specific rules always take priority over precedent. If a market explicitly says “resolves based on consensus of credible reporting,” you don’t need to wait for official certification. Precedents fill the gaps that the rules don’t cover, not the ones they do.
1. Market Intention Beats Literal Reading
When a market’s literal text and its obvious intent conflict, intent wins.
The canonical case is “MicroStrategy changes name to ‘Strategy’.” Strictly speaking, the company’s official legal name and its consumer-facing brand are different things, and you could argue the market had to resolve one way or the other based on which definition you picked. The oracle went with intent: the market was asking about the widely-publicized rebrand, and that’s what resolved it YES.
A related principle covers typos and minor errors in the proposal or UMA request. When the Super Bowl Championship 2026 market saw a proposal that mis-referenced “2025,” the market still resolved per the interface — the typo didn’t matter because the intent was unambiguous. Similarly, misspelled names (like “Zohran Mamdan” for a NYC Mayor primary market) resolved correctly based on who was obviously meant.
Trader takeaway: If a market’s literal text leaves a technical escape hatch but the intent is clear to anyone reading the interface, the intent is almost certainly how it resolves.
2. Official Sources Required for National and Federal Events
For high-stakes national events — presidential elections, Senate votes, Federal Register publications, CPI releases — the oracle typically requires official confirmation, not media consensus.
This is the opposite of the precedent in #3 below, and the distinction matters. Markets like “Did candidate X win Senate race Y?” generally don’t resolve on election night based on a concession or an AP call. They resolve when the state certifies results.
The “Has Georgia certified the vote?” type of market has historically required statewide certification, not county-level rollups. For executive orders, the requirement is publication in the Federal Register — a White House press release or press briefing alone isn’t enough.
Trader takeaway: Read national-level markets carefully for the phrase “consensus of credible reporting may suffice.” If that clause isn’t there, official sources are required, and markets can’t resolve until the official source publishes — even if the outcome is obvious by then.
3. Early Resolution via “Consensus of Credible Reporting”
When a market’s rules explicitly include the “consensus of credible reporting may suffice” clause AND the real-world consensus is overwhelming, the oracle will resolve early — before official certification.
The clearest use case is a candidate who concedes, or a path to outcome that becomes mathematically impossible, with media reporting uniformly treating the race as decided. Under those conditions, a market can close without waiting for the official certification that will eventually formalize the result.
But: the clause has to be present, and the consensus has to be overwhelming and unambiguous at the moment of proposal. “Most outlets think so” isn’t enough. “Every major credible outlet has called it, the candidate has conceded, and no outlet is disputing” is enough.
Trader takeaway: “Consensus of credible reporting” is a powerful clause but also inconsistently applied. When it’s present, it enables early resolution. When it’s absent, markets wait for the formal source no matter how obvious the outcome is.
4. Preliminary vs. Final Data
A lot of data sources publish preliminary numbers first and revise them later. Markets that depend on those sources expect proposers to know the difference.
NASCAR is the classic example: race results can be revised after post-race technical reviews, so “who won the race?” doesn’t actually resolve at the moment the checkered flag falls. USGS earthquake magnitudes get revised for up to 24 hours after the initial reading. BLS employment data has an initial release followed by revisions.
When a market asks for “the result” without specifying preliminary or final, the oracle generally defaults to the final version — which means proposing too early based on preliminary data can get your proposal overturned, even if the preliminary number looked correct.
Trader takeaway: If you’re trading around a data release where revisions are common, don’t price the market as if the first release settles it. And if you’re proposing, wait for the final data point unless the market explicitly calls for preliminary.
5. Event Deadline vs. Data Availability Deadline
Related to #4 but more specific: some markets have two implicit deadlines — the event deadline, and the data availability deadline — and the distinction determines how the market resolves.
Executive orders are the cleanest example. A market asking “will the President sign X order before June?” requires both: (1) the order must be signed by the deadline, AND (2) it must appear in the Federal Register by 12:00 PM ET the day after the listed date. If the order is signed before the deadline but doesn’t publish within the grace window, the market can still resolve NO.
Earthquake markets work the other way: if a qualifying earthquake registers before the market’s deadline, the market stays open for 24 hours to allow for USGS magnitude revisions. The event happened in time; the data is allowed to firm up afterward.
Trader takeaway: Read carefully for any publication, release, or confirmation requirement tied to the deadline. The event happening in time isn’t always enough.
6. Mention Markets: Noun-Only Unless Stated
“Mention” markets — will someone say a specific word or phrase during a specific event — have their own dense ruleset, and it’s one of the most common sources of bad trades.
The defaults:
- Noun form only, unless the market explicitly says otherwise. If the word can function as both a noun and a verb, only the noun usage counts.
- Spoken only. Written references — prepared text that wasn’t read aloud, social media posts, captions — don’t count.
- Within the specified timeframe. Mentions before or after the event don’t count, even if they’re adjacent.
- Plurals and possessives generally qualify as the base word.
- Compound words that contain the target word generally qualify.
For example, a “will Trump say [X]” market is about spoken X, in noun form, during the specific event — not what he tweets beforehand, and not a verb form like “to [X].”
Trader takeaway: If you’re trading a mention market, read the exact phrasing and assume the defaults apply unless the market explicitly overrides them.
7. Word-Level False Equivalence: The Zelenskyy Suit Precedent
When a market asks about a specific word or thing, the oracle interprets it at the technical level, not the loose colloquial level — and that technical definition sticks across subsequent versions of the same market.
The canonical case is the “will Zelenskyy wear a suit by X?” family of markets. A suit jacket worn casually over different trousers is not a “suit.” A suit means a matching jacket and trousers of the same material, typically worn with a dress shirt and tie. That technical definition was established in early disputes and has been reapplied in every subsequent version of the market, even when public interpretation of what “counts” as a suit has arguably softened.
Two related patterns to watch for:
- Event-level false equivalence. “Will Iran close the Strait of Hormuz?” (see #8) had some traders treating a slowdown or GPS jamming as “closure.” The oracle generally rejects that kind of scale-flattening.
- Phrase-level false equivalence. “Severely restricts” doesn’t mean “any major disruption.” Loose interpretation of resolution phrasing is almost always rejected when tested.
Trader takeaway: If a precedent already established how a word or phrase is interpreted in one version of a market, assume that definition carries forward. Don’t trade as if “public opinion has shifted” — the oracle won’t shift with it.
8. The Strait of Hormuz Closure Precedent
During the 2025 Iran-Israel-US flare-up, a family of markets asked whether Iran would “close” or “severely restrict” traffic through the Strait of Hormuz. Real-world conditions got weird: Iranian GPS jamming caused tanker traffic to slow meaningfully, with some shipping lanes seeing 50%+ traffic drops on peak disruption days.
Some traders argued this satisfied “closure” or “severe restriction.” The oracle disagreed. The markets resolved NO because the criteria required halting or severely restricting traffic in a clear, observable way — not merely making passage more expensive or slower. A disrupted but functioning strait isn’t a closed strait.
The precedent generalizes beyond this specific market: for geopolitical “has X happened” markets, the bar is usually high and concrete. “Signs of impending X” and “partial X” generally don’t satisfy a market that asks about X itself.
Trader takeaway: When a geopolitical market starts seeing heavy news flow about “tensions escalating” or “early signs,” ask yourself what the market’s resolution criteria actually require. The gap between “escalating” and “happened” is usually where disputes live — and where money gets made or lost.
How to Use These Precedents as a Trader
Three practical applications:
Before entering a position, read the market’s resolution rules against these 8 precedents. If the market is ambiguous on any of them, you’re looking at a resolution risk that may not be priced into the current market price.
When the market price diverges from what looks obvious to you, one of these precedents is often the reason. “Why isn’t this trading at $0.99 when the outcome is obvious?” is a question with specific answers: maybe official certification hasn’t happened, maybe preliminary data looks different from final, maybe the word you’re focused on has a technical definition you didn’t know about.
When proposing, treat these precedents as the minimum you need to know. Most bad proposals come from proposers who assumed the “obvious” interpretation applied, without checking whether a precedent says otherwise. If you’re thinking about proposing, internalize all 8.
Bottom Line
Resolution precedent is the invisible second layer of Polymarket’s rulebook. The community archive at polymarketguide.gitbook.io has dozens more precedents beyond these 8, and serious traders should read the archive in full once they’re comfortable with the basics.
But these 8 cover the cases you’ll hit most often, and knowing them turns “this market resolved weirdly” into “this market resolved predictably, and I should have priced that in.”
If you’re building a trading workflow that depends on this level of detail, make sure you’re on the platform first — sign up for Polymarket and start pattern-matching your own market reads against how the oracle actually behaves.
Learn More
- How Polymarket Markets Resolve — The full UMA Optimistic Oracle process
- How to Propose Polymarket Resolutions — The practical guide to becoming a proposer
- Understanding Odds on Polymarket — How to read prices in light of resolution uncertainty
- Polymarket Review 2026 — Full in-depth review