a resolution source that can lag, contradict, or update
an oracle process that can dispute / delay / clarify
You don’t need to predict disputes to care about resolution.
You need to predict what the contract will settle on.
2) The Resolution Surface Area (What to Inspect)
Published: March 11, 2026 · 11 min · Whale Team
Before you trade, inspect these fields:
A) The question and the end date
Wording often encodes:
what counts as “happened”
the timestamp window
whether late events count
B) The resolution source(s)
Markets often specify a source (“AP”, “official website”, “regulator”, “on-chain metric”).
Different sources can disagree on timing or definition—even when reality is clear.
C) The outcome mapping
Binary markets hide a trick: “YES” often means “the event occurs under the contract definition,” not “the vibe is true.”
D) The oracle / dispute process
Even with clean wording, resolution can involve an oracle workflow and disputes.
Polymarket’s documentation describes resolution processes and UMA-based mechanisms for some markets, including dispute handling and clarifications (bulletin board).
External sources:
5) How to Verify Wording and Sources (Public, Reproducible)
You can fetch market metadata via Polymarket’s public Gamma API.
External source (Gamma markets API, including fields like slug, endDate, and resolutionSource depending on the market object):