> ## Documentation Index
> Fetch the complete documentation index at: https://docs.testnet.dev.adipredictstreet.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Void & delayed markets

> What happens when automated settlement cannot proceed safely.

## Delayed

Market moves to `DELAYED` when the configured data source(s) cannot
yield a safe, unambiguous outcome:

* Provider data is unavailable or stale at the expected resolution
  window.
* Provider data is ambiguous (e.g. event status not yet decisive).
* When multi-source is configured, no safe majority across the
  configured providers.

(Earlier docs described a "primary-source disagrees with majority"
rule — that rule is not implemented today; routing to `DELAYED` is
driven by the unavailable / ambiguous / no-safe-majority cases
above.)

### 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

Void is a **payout-vector outcome**: the contract resolves the
market with a vector that returns equal payouts across the
outcomes (rather than a winner-takes-all vector). Redemption then
follows that **void payout vector** through normal
`ConditionalTokens.redeemPositions` — partners do not need a
separate refund flow. The amount returned to a holder is determined
by the void payout vector + their token holdings at resolution
time, **not** by the original trade price they paid to acquire those
tokens.

Grounds (SOP §9.1):

* Event cancelled / abandoned with no standing result.
* Resolution criteria insufficient / ambiguous.
* Dispute review concluded void is the only safe outcome (binary
  markets).

### Approval

CO + CTO joint written approval, tracked off-chain via SOP. Board
notification within 24 hours. The on-chain authorisation model is an
admin role — the repo does not currently prove an active multisig
integration on this path.

### What you observe

* Market status → `VOIDED`.
* `oracle.market_cancelled` WebSocket event published (separate from
  `oracle.market_resolved`).
* Users: position tokens redeem against the **void payout vector**
  via `ConditionalTokens.redeemPositions`. Lock release follows
  redemption, not the original trade-cost basis.

### Challenger bond on void

Returned in full (binary markets, where the challenge path applies).
Void = "original proposal was wrong, but dispute was also not the
correct path".

## Emergency proposal clear (binary markets)

If the oracle signer posted a mistaken proposal on a **binary**
market:

```
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.

Neg-risk markets do not have an analogous proposal-clear path —
recovery from a wrong winner-index report goes through the admin
void path above.