DisputeTracker
DisputesUpdatesPro
Community
X CommunityXTelegram
TokenSwap
fixtureCLOSEDuma unavailable
Track with Pro

Fixture: fixture-first-dispute-reset

Will this fixture market resolve to YES under the listed rules?

Current stageCurrent stageThe app maps Polymarket and UMA data into one dispute path. This stage is the best current read from cached market, oracle, and voting data.

Second proposal

First dispute reset

YES

Beginner mapBeginner mapA plain-English layer over the raw UMA and Polymarket data. It explains the current stage, likely next step, and what signal matters most.

Second proposal

50% through visible path

What is happening

A second answer was proposed after the first dispute.

Likely next

Second dispute: If this second answer is disputed, the case escalates to UMA DVM voting.

What to watch

This is the important fork: no dispute means acceptance, dispute means validator vote.

Trader readoutTrader readoutA short summary of the next meaningful event. It is not advice; it tells you what process step can change the dispute next.

Second proposal finalizes if undisputed, or second dispute escalates to UMA

Can end after this stage if the second proposal is not disputed.

Open main Polymarket market
ESTIMATED

Time leftTime leftEstimated or exact time until the current stage can move. Exact means timestamped data was available; estimated means the app inferred it from the stage.

est. 24h

Timing qualityTiming qualityShows whether timing comes from concrete timestamps or from a stage-based estimate.

Estimated from current stage

Data freshnessData freshnessHow fresh the cached market and oracle data is. Cards open from cache first, then scheduled sync keeps them updated.

fixture data updated at 2026-07-21T12:43:28.411Z

CoverageCoverageTells you whether the app has indexed on-chain data, Gamma fallback data, or partial coverage for this market.

Fixture scenario; not live market coverage.

Resolution timelineResolution timelineThis turns raw Polymarket and UMA events into a single beginner-friendly path. Green steps are passed, blue is current, grey is still ahead.

Second proposal

PassedPassedStages already detected as complete.

5

LeftLeftKnown stages still ahead if the dispute follows the full path.

4

TotalTotalTotal stages in the app's dispute model.

10

OpenMarket openThe market is still trading or waiting for close. No final dispute decision is happening yet.

complete

complete

ReviewClosed / in reviewThe market is closed or being reviewed before an oracle proposal becomes visible.

complete

took 6h

Proposal 1First proposalA proposer submitted an answer. This can still be challenged during the dispute window.

complete

took 2h

WindowFirst dispute windowThe proposal is waiting through its challenge period. If no one disputes, it may become accepted.

complete

took 30m

Dispute 1First disputeThe first proposal was challenged, so the process resets and needs another proposal.

complete

took 1m

Proposal 2Second proposalA second answer is proposed. If this one is disputed, the case can escalate to UMA token voting.

active

elapsed 6.3h / est. 24h

Dispute 2Second disputeThe second proposal was disputed. This is the handoff into UMA DVM voting.

pending

est. <1h

UMA ReviewUMA final reviewUMA voters commit and reveal votes. Before reveal, the actual outcomes are hidden.

pending

est. 24-72h

SettledUMA settledUMA has produced a result, but the Polymarket market may still need final settlement plumbing.

pending

est. 24h

ResolvedResolvedThe market has applied the final result and the dispute path is complete.

pending

final

Open

The market is still trading or waiting for close. No final dispute decision is happening yet.

complete

complete

Review

The market is closed or being reviewed before an oracle proposal becomes visible.

complete

took 6h

Proposal 1

A proposer submitted an answer. This can still be challenged during the dispute window.

complete

took 2h

Window

The proposal is waiting through its challenge period. If no one disputes, it may become accepted.

complete

took 30m

Dispute 1

The first proposal was challenged, so the process resets and needs another proposal.

complete

took 1m

Proposal 2

A second answer is proposed. If this one is disputed, the case can escalate to UMA token voting.

active

elapsed 6.3h / est. 24h

Dispute 2

The second proposal was disputed. This is the handoff into UMA DVM voting.

pending

est. <1h

UMA Review

UMA voters commit and reveal votes. Before reveal, the actual outcomes are hidden.

pending

est. 24-72h

Settled

UMA has produced a result, but the Polymarket market may still need final settlement plumbing.

pending

est. 24h

Resolved

The market has applied the final result and the dispute path is complete.

pending

final

Path duration

est. 8.1d

Current phase

6.3h

Next phase

est. <1h

50% completetiming: estimatedFixture scenario; not live market coverage.

Pro function

Final Time Left

Pro shows the estimated time remaining until the market reaches final resolution.

Unlock Pro

UMA DVM vote

Validator voting not indexed yet

This dispute is not in an indexed UMA voting round yet. If it reaches validator voting, commit/reveal analytics will appear here.

WAITING

Source-backed data

Oracle, bond and evidence details

Normalized records persisted from Polygon, UMA subgraphs, Gamma and the Polymarket CLOB.

86% complete · 2 missing

Proposal

Proposer
0x1111...1111
Proposed outcome
YES
Bond
500 USDC
Challenge deadline
Jul 21, 2026, 8:43 PM
Custom liveness
Not available
Event-based request
Not available

Bond flow

Amounts use the raw source units returned by UMA.

Proposer bond (raw)

500 USDC

Disputer bond (raw)

500 USDC

Reward (raw)

not_available

Final fee (raw)

Not available

Settlement payout (raw)

Not available

Settlement recipient

Not available

UMA voting data is not available for this market yet.
Missing or not-yet-public fields (2)
  • umaVoting.voterCount:not_available
  • umaVoting.votingPower:not_available

Evidence

Persistent source records attached by an authorized administrator.

Fixture evidence for fixture-first-dispute-reset

DisputeTracker fixture - MIXED

source evidence-fixture-first-dispute-reset

This fixture evidence exists to demonstrate source-linked summaries. It is not live external evidence.

Indexed chain events (0)
[]

Start date

Not available

End date

Jul 21, 2026, 12:43 PM

Updated

Jul 22, 2026, 3:28 AM

Volume

$125,000

Liquidity

$15,000

Condition

0xfixturefirstdisputereset0000000000000000000000000000000000000000