Deadlines, disputes and refunds

Read the market clock#

The market's opening time, plateau end, cut-off and resolution time come from its on-chain configuration. Pool entry and par-exit windows are separate. Reporting and dispute deadlines are also separate from transaction confirmation.

The UI has status labels for presenting the lifecycle; those labels do not introduce additional contract states or waiting periods. A published lane timer must not be read as a guaranteed payout time or a universal post-report lock.

Resolver deadlines#

• The chain reporter has a one-hour observation window; after an unanswered window its void path can be called.
• The optimistic reporter has two-hour challenge windows, six hours for an unanswered second proposal and 48 hours for an escalated court ruling.
• Attestations require evidence committed at least one hour earlier and a valid signature deadline. There is no optimistic challenge period on that lane.

See Optimistic challenges for bond outcomes. Court timeout can forfeit dispute bonds even when trading positions are refunded.

Unresolved-market backstop#

After the seven-day grace period measured from the resolution time, an unresolved condition or pool may be voided through its permissionless backstop. Already answered conditions cannot be overturned through this route. The router also has a timelocked void-override path subject to its checks; it cannot choose a different winning outcome.

Claims and bonds#

Voided pool positions refund principal without a trading fee. Claims are pull-based; gas is separate. Exchange shares and combos have their own payout rules.

A creator bond becomes refundable under the bond contract's finalization/series-close delay. A configured court can hold or forfeit bonds under separate rules. Check the deployed configuration rather than assuming a court is unset. See Payouts and void markets.