Article
1 September 2026
What Do Historic Prediction-Market Resolution Disputes Teach Us?
Past cases show how ordinary words, evidence cut-offs, source conflicts, and unplanned events can become settlement problems—and what a drafter can specify before trading begins.
Semantics
“Winner,” “suit,” “perform,” “out,” and “agreement”
Evidence
Official declarations, filings, images, and datasets
Timing
Occurrence, publication, certification, and revision cut-offs
Procedure
Challenges, review, fallback outcomes, and finality
Short answer
Most hard resolution cases are specification failures before they are oracle failures. The market needs a controlled vocabulary, a ranked evidence policy, explicit timing and revision rules, and a review procedure that says when the result becomes final.
The historical record shows that most serious disputes are not caused by arithmetic. They arise at the boundary between words and reality: What does “win” mean before certification? What is a “suit”? Does dancing and mouthing lyrics constitute “performing”? Does death count as leaving office? Does a military raid constitute an “invasion”? Is an announced political understanding an “agreement”? Which of two conflicting official COVID datasets controls? These are problems of semantics, ontology, evidence and procedure, not merely oracle technology.
An oracle is the person, committee, exchange process, or technical mechanism that supplies or confirms the settlement answer. Better oracle machinery can make a decision auditable. It cannot, by itself, decide which meaning the contract should have had.
The examples below separate formal disputes—cases recorded by the venue as challenged or disputed—from resolution controversies, where the public record shows serious disagreement even if the venue page records no formal challenge. A lawsuit citation identifies allegations made in a filed complaint, not a judicial finding.
1. Historic cases that illustrate it
“Winner”: Venezuela’s 2024 presidential election
Polymarket asked who would win Venezuela’s 2024 presidential election. Its market pages preserved the candidate questions, while the resolution controversy turned on competing ideas of victory: the result announced by the state-controlled electoral authority, the vote reflected in opposition-held tally sheets, and international recognition. The original Polymarket event is the exact market record. A contemporaneous Atlantic account of the resolution reports that Universal Market Access (UMA) arbiters selected Edmundo González even though the market’s primary wording referred to official information from Venezuela. The Inter-American Commission on Human Rights record documents that the National Electoral Council announced Nicolás Maduro as winner while the election result was contested.
Drafting lesson: define whether “winner” means the person with the most valid votes, the person certified by a named electoral authority, the person recognized by specified institutions, or the person who actually assumes office. If an early media call can resolve the market, state whether later certification or a successful legal challenge can reverse it.
Occurrence time versus publication time: Strategy’s Bitcoin sale
The Polymarket “MicroStrategy sells any Bitcoin” event records two disputes and a final “No” outcome for the 31 May 2026 iteration. Strategy had sold 32 Bitcoin between 26 and 31 May, but the sale became public on 1 June. The contemporaneous dispute report describes the disagreement, and Strategy’s sale period is documented in reporting based on its regulatory filing.
Drafting lesson: say whether the underlying act must occur before the deadline, whether qualifying evidence must also be published before it, or both. Add a defined evidence-lag window for events that are routinely disclosed later.
“Suit”: Zelenskyy’s clothing
The exact Polymarket market page asked whether Volodymyr Zelenskyy would be photographed or videotaped wearing a suit before July 2025. It records a final “No” outcome and more than $242 million in volume. The public dispute was not about whether an image existed; it was about whether the photographed outfit belonged to the category “suit.” The archived resolution record preserves the successive votes and final result.
Drafting lesson: do not leave a decisive visual category to ordinary-language intuition. Define required garments and excluded near-matches, state whether tailoring, colour, tie, and matching fabric matter, and name the image evidence that qualifies.
“Perform”: Cardi B at the 2026 Super Bowl halftime show
The Polymarket Cardi B contract required a live, in-person performance. Cardi B appeared, danced, and mouthed words. The Associated Press report documents that Kalshi treated the conduct as too ambiguous for a normal binary settlement, while Polymarket initially treated it as a performance and faced a challenge.
Drafting lesson: define whether singing, audible live vocals, playing an instrument, rapping, dancing, lip-syncing, a cameo, or merely appearing on stage counts. Say whether broadcast audio, production credits, or an organizer’s classification controls.
“Out of office”: Ali Khamenei and the death carve-out
Kalshi listed an “Ali Khamenei out as Supreme Leader?” market. After Khamenei’s death, traders disputed whether being dead necessarily meant being out of office for purposes of the contract. A federal complaint filed in March 2026 records the plaintiff’s allegation that the displayed proposition and the death carve-out led to different payout expectations. Those statements are allegations in pending litigation, not findings by the court.
Drafting lesson: list the exhaustive ways a person may leave office—resignation, removal, term expiry, incapacity, disappearance, or death—and assign an outcome to each. Put a non-binary or refund mechanic in the display-adjacent rules if it can replace the apparent Yes/No payout.
“Invasion”: the January 2026 U.S. raid in Venezuela
The exact Polymarket invasion contract defined invasion as a military offensive intended to establish control over territory. U.S. forces entered Venezuela and captured Nicolás Maduro, but the contract records “No” and no formal oracle dispute because the raid did not satisfy that control test. The Associated Press account of the raid confirms the underlying operation. This is best described as a public resolution controversy, not a formal dispute on the market page.
Drafting lesson: replace the label “invasion” with observable elements: entry by whose forces, into which land, sea, or air territory, for how long, with what scale, purpose, and degree of control. State whether raids, strikes, blockades, reconnaissance, proxy forces, and consented deployments are excluded.
“Agreement”: the 2025 U.S.–Ukraine minerals arrangement
The Polymarket minerals-deal market said that an announcement of a deal would qualify even if the deal had not yet been enacted. The page records two disputes and a final “Yes” outcome in March 2025. The final reconstruction investment agreement was later described by the White House on 1 May 2025.
Drafting lesson: distinguish a statement of intent, joint announcement, memorandum of understanding, initialled text, signed agreement, ratified agreement, entry into force, and implementation. If an announcement alone qualifies, define whose announcement and the minimum terms it must confirm.
COVID data: changing releases, revisions, and source failure
COVID-era questions show why “official data” is not one self-defining object. A 2021 Metaculus vaccination question records a change in the Centers for Disease Control and Prevention (CDC) measure from “receiving two doses” to “fully vaccinated” and a sequence of revisions to the value for the same date. A separate Good Judgment Open resolution discussion records a COVID breakthrough-case question being voided after the CDC stopped publishing the data required by the specified source. Kalshi’s CFTC-filed daily COVID-case terms addressed the same class of risk by naming the exact CDC table, treating missing daily data as zero, and excluding post-expiration revisions.
I have not found a preserved public adjudication proving one particular cash market was formally disputed between two named official COVID datasets. The documented record does show the underlying problem clearly: official measures changed, historical values were revised, and specified feeds disappeared. A claim about a particular formal dispute should cite that dispute record rather than infer it from general COVID data conflict.
Drafting lesson: identify the publisher, dataset, table, field, geography, observation date, publication vintage, access time, and revision cut-off. Rank fallbacks. Never write only “official COVID data.”
2. The recurring failure patterns
- Category ambiguity: an ordinary word has several reasonable boundary cases.
- Ontology mismatch: the real event does not fit the contract’s assumed boxes—for example, death within an “out of office” market or a raid within an “invasion” market.
- Evidence ambiguity: official declaration, underlying facts, media consensus, and later correction point in different directions.
- Timing ambiguity: occurrence, observation, publication, certification, expiration, and settlement are treated as if they were the same moment.
- Procedure ambiguity: the rules do not explain who may challenge, which record is reviewed, what interim state applies, or when the answer becomes irreversible.
3. How to prevent the next dispute
- Write the resolution sentence first. Before naming the market, write the complete Yes condition and the complete No condition.
- Define every decisive noun and verb. Add inclusions, exclusions, and at least two near-boundary examples.
- Separate event time from evidence time. State whether occurrence time or publication time controls and how long delayed evidence remains admissible.
- Freeze the data vintage. Say whether first release, latest release at expiration, or a later final release controls, and which revisions are ignored.
- Use a ranked source hierarchy. Name the exact primary page, dataset, table, or document and the conditions for moving to each fallback. State what happens when sources conflict.
- Plan for broken assumptions. Assign outcomes for cancellation, postponement, material transformation, impossibility, source failure, ties, partial completion, and events that become unclassifiable.
- Lock rules once risk is live. Permit only narrow, logged clarifications that do not change the economic meaning. A material change should trigger the pre-agreed cancellation or migration procedure, not an improvised rewrite.
- Publish the review procedure. Define the challenger, evidence window, reviewer, conflict policy, possible decisions, reasons, notice, appeal, settlement delay, and finality rule.
- Run adversarial examples before listing. Ask independent readers to resolve an ordinary case, a boundary case, a source conflict, a late publication, a revision, and an impossible or transformed event.
A compact pre-listing test
Give the terms and the same evidence packet to three readers. If they disagree, do not ask the oracle to repair the ambiguity later. Change the definitions, source hierarchy, timing rule, revision policy, or contingency outcome before the market opens.
Sources and limits
The links above point to the exact market page where available, plus a primary public record or contemporaneous report explaining the underlying event or dispute. Venue pages can change after settlement, so a durable research file should also preserve the retrieved terms, timestamp, market identifier, and any on-chain or exchange review record. This article is a specification analysis, not legal advice and not an assessment that any venue or participant acted unlawfully.