Settlement should end a trade—unless someone argues the result does not match the rules. Dispute resolution is the enforcement layer behind every product in this module: binaries, slates, scalars, spreads, props, conditionals, trees, and bundles all pay only after an authority (or game) says what happened. You always trade the event and the enforcer.
Two families of enforcement
Centralized paths put final say with the exchange and its supervised rulebook—fast USD credit, narrow appeals, house interpretation on edge cases. Decentralized paths export fights to bonds, optimistic assertions, and token votes—slower, transparent on-chain, but invalid and void are first-class outcomes.
Neither removes ambiguity; they price it differently.
Centralized exchanges: speed and trade-offs
Determination typically applies listed data sources—wire calls, government releases, official sports statistics. An appeal window exists in customer agreements but overturns are rare for retail traders. Strength is predictable clocks and supervised infrastructure; weakness is opaque judgment on quirky props without a public bond war.
Bet when the appendix maps cleanly to a feed; avoid “wins the debate” without a measurable criterion.
Optimistic oracles on crypto-native markets
Many global platforms propose outcomes through an optimistic oracle: an asserter posts a bond and a claim; challengers post counter-bonds; escalation may go to a token vote. Traders wait while capital is frozen. Strength is a visible challenge trail; weakness is ambiguous props becoming bond politics—late entrants face dispute gamma after the headline feels obvious.
Asserters profit when correct; disputers profit when the assertion is wrong—retail edge is usually picking markets, not litigating them without expertise.
Decentralized reporting and invalid outcomes
Permissionless designs let communities list anything—and pay for bad wording with invalid resolutions that refund or split per protocol rules. Censorship resistance pairs with slower UX and higher invalid rates on poorly designed questions. Product and oracle are one risk bucket.
What triggers disputes
Ambiguous wording on props. CPI or jobs revisions after a first print. Conditionals where X was not official when Y was scored. Candidate withdrawals reshaping trees. One bad leg in a bundle. Early media calls versus rulebooks that demand certificates or specific agency PDFs.
Scalar and prop chapters are dispute magnets; binaries on clean feeds are the calmest—until they are not.
Dispute economics in plain numbers
You bought YES at 80¢ on “Agency publishes Report Z by December 31.” A PDF appears January 2; asserter says NO under “publish means on-time public PDF”; holder disputes YES citing leaks.
While redemption is frozen, your mark is uncertain. If NO upheld, you lose 80¢; if YES upheld, you gain 20¢; if invalid, you may refund near entry. Tail risk is not only probability—it is rule politics.
Dispute-aware habits
Score ambiguity before entry; shrink or skip at the top of the scale. Screenshot rules at trade time. Calendar challenge windows before redeploying capital. Prefer exiting at 97¢ when invalid risk dominates the last few cents of hold-to-$1.
Compare the same headline across venue classes: centralized finality versus on-chain challenge is a different tail, not a different belief about the world.
How this module fits together
Binaries lean on clean feeds; categoricals fight over exclusivity; scalars fight over revisions; spreads fight over reference institutions; props fight over English; conditionals fight over timing of X; trees cascade invalid parents; bundles poison on one leg; settlement clocks collide with challenge clocks. Good resolution design prevents disputes; when clarity fails anyway, the enforcer decides.
Manipulation may target assertion rather than mid-price on thin markets—incentivized reporting is a scoring game with bonds at stake.
Calibration after disputes
Forecast scores should use final settled outcomes, treating voids as missing data where appropriate. A market that voided was not “wrong at 50%”—it was undefined.
Side-by-side enforcement styles
| Style | Final say | Typical speed | Invalid/void |
|---|---|---|---|
| Regulated exchange | Ops + rulebook | Hours–days | Rare, rulebook-defined |
| Optimistic oracle | Assertion + challenge | Hours–weeks | Market-specific |
| Decentralized reporting | Token votes | Days–weeks | More common on bad design |
You trade the column, not only the event.
Props and bundles as dispute magnets
Mention definitions, index revisions, and one bad bundle leg drive challenges. Binaries on AP calls and BLS releases are calmer—until wording is vague.
Retail edge is selection
Posting dispute bonds without expertise is a different game than buying mispriced YES. Prefer skipping ambiguous markets to litigating them.
Module arc closure
From binary complements through bundles and settlement clocks, Module 05 is the rulebook for instruments. Module 06 asks how each major venue implements trading, liquidity, and trust under the hood.
Core concepts to remember
You trade rules and enforcers, not slogans. Centralized paths favor speed; decentralized paths export fights to bonds and votes. Invalid and void belong in expected value. Ambiguous props and bundles are dispute magnets—selection beats litigation.
Common mistakes
Assuming headlines equal determination. Posting dispute bonds without understanding escalation. Ignoring invalid in expected value. Trading ambiguous bundles for “yield.”
What comes next
Module 05 defined the instruments. Platform Deep Dives walks through how major venues implement trading, liquidity, and trust in practice.
Next: Module 06 Platform Deep Dives — Polymarket architecture and peers