Skip to main content

Resolution and disputes

RuneMarket uses an optimistic resolution process. A proposed result is accepted when it survives its challenge period without a dispute. Contested results move through the Oracle Council and, if necessary, a bonded external escalation.

Challenge-period lengths and bond amounts are configurable protocol values captured by each market. Always use the values displayed for the specific market; RuneMarket does not promise a universal duration or fixed dollar bond.

Proposing a result​

Once a market is open for resolution, any wallet can propose:

  • YES;
  • NO; or
  • CANCELED.

The proposer supplies the configured resolver bond in the market's USDC payment token. The USDC payment token must be approved to the Oracle Bonds contract, which holds resolution and dispute bonds.

A proposal should follow the market's complete onchain question, source, and additional information. CANCELED is a distinct outcome intended for circumstances covered by the market's rules, not a substitute for an uncertain YES or NO result.

Opening a dispute​

During the first challenge period, a different participant can challenge the proposal by:

  1. entering a non-empty reason;
  2. approving the USDC payment token to Oracle Bonds; and
  3. posting the market's configured disputer bond.

One wallet cannot maintain more than one open disputer bond for the same market. More than one dispute may exist for a market, and unclosed disputes can have separate bond-return handling when the market's dispute state moves on.

Oracle Council review​

Oracle Council members vote on an open dispute. A majority can choose one of three decision types:

  • Accept — accept the challenge and choose a different YES, NO, or CANCELED result;
  • Reset — return the market to resolution so a new proposal can be made; or
  • Refuse — reject the challenge and preserve the original proposed result.

Council members also vote on punishment. This allows a result to be corrected or reset without automatically assuming that every incorrect participant acted in bad faith.

Escalating a Council result​

A Council decision that selects or preserves an outcome is followed by a second challenge period. A reset also receives a second challenge period when the Council chooses to punish the resolver; otherwise, the market reopens for resolution immediately and the selected resolver and disputer bonds are returned.

While a second challenge period is open, a participant may post the market's escalation bond and submit a written escalation reason.

RuneMarket then associates the market with an external proposal identifier. The external process determines the outcome and bond-treatment instructions. An authorized operator submits those instructions onchain. The RuneMarket development team currently serves as that authorized operator.

RuneMarket does not currently use a RuneMarket governance token or token-holder voting contract. Attester arbitration is not part of the current resolution path.

Finality and resets​

If a selected YES, NO, or CANCELED result survives its applicable challenge period, it becomes final. An accepted escalation can finalize a selected outcome. A rejected escalation applies the Council result. Any reset path returns the market to Open for Resolution and clears the prior proposed winner so the resolution process can begin again.