Skip to main content

​
Delayed

Market moves to DELAYED when oracle can’t determine outcome safely:
  • 0-of-3 consensus.
  • Primary source disagrees with majority, not explainable (SOP §8.2).
  • Data feed outage during expected resolution window.

​
Your trading effect

  • New orders: rejected (409 market_not_open).
  • Existing locked balances: preserved.

​
Recovery

  1. Secondary source cross-check by Settlement Ops.
  2. If resolved → returns to PENDING_RESOLUTION.
  3. If not resolved in reasonable time → CO decides on void (CO + CTO joint approval).

​
Void

Returns all collateral to all users. Grounds (SOP §9.1):
  • Event cancelled / abandoned with no standing result.
  • Resolution criteria insufficient / ambiguous.
  • Dispute review concluded void is the only safe outcome.

​
Approval

CO + CTO joint written approval. Board notification within 24 hours. Admin multi-sig on-chain transaction.

​
What you observe

  • Market status → VOIDED.
  • oracle.market_resolved WebSocket event with equal-split payouts.
  • Users: balance locked → available; position tokens redeemable 1:1 their original cost basis.

​
Challenger bond on void

Returned in full. Void = “original proposal was wrong, but dispute was also not the correct path”.

​
Emergency proposal clear

If the oracle signer posted a mistaken proposal: 
initiateProposalClear(questionId)      // starts 7-day clock
executeProposalClear(questionId)       // after 7 days
Timelock gives users / Settlement Ops a window to challenge the cleared proposal if the “fix” was itself incorrect. Used only when the original proposal was a bug, not a disagreement.