Resolution walk-throughs
For how a market becomes yours in the first place, see Market acceptance.
Non-disputable resolver
Disputable resolver
Changing a standing proposal
Calling resolve with an outcome different from the standing proposal returns 409 proposal_mismatch;
change the proposal first. Non-disputable resolvers never hold a standing proposal, so this section does not
apply to them unless a previous resolve transaction was only partially confirmed (see
Failure modes).
Void
Void is available while the market is live or has a standing proposal, from its earliestProposalTs on the
current program (see Contract versions).
Platform void
Melee never voids a market for time. A market that is late, or whose status polls fail, stays yours to resolve. Melee voids a market only for one of these reasons:
platformVoidReason | When |
|---|---|
AuthorityDrift | The market’s on-chain resolution or proposer authority no longer matches the keys you accepted. |
DefinitionDrift | The market’s on-chain outcome count no longer matches the definition you accepted. |
Operator | Melee intervenes: an admin voids the market, or Melee suspends its resolver and voids its open markets. |
The program lets Melee’s timeout authority void a market only from its timeoutTs, so a planned void never lands
earlier: Melee sends it once timeoutTs plus a 24-hour grace has passed. Until then you can still resolve or void
the market yourself. While a transaction Melee issued to you for that market (propose, resolve or void) is
outstanding or submitted, the void waits. On a live market with no proposal, Melee proposes and resolves void in
one transaction; with a standing proposal, it resolves void. See
Lifecycle notifications.