Resolution Rules
Every Arenaton Market must publish its Resolution Source, Invalid Path, and Correction Window before trading opens. These terms are part of the Market; they cannot be rewritten after users sign orders.
Required Market Terms
Section titled “Required Market Terms”| Term | Meaning | Launch requirement |
|---|---|---|
| Resolution Source | The official data source, oracle, resolver workflow, or on-chain fact used to decide the final outcome. | Must be visible on the Market detail page before order signing. |
| Invalid Path | The rule for a Market that cannot be resolved safely or validly. | Must state whether the Market resolves invalid through CTF payout vector [1, 1] or follows another published rule. |
| Correction Window | The review period after event close before finalization. | Must be category-specific and visible before trading opens. |
| Direct Redemption | The user path for redeeming resolved Outcome Shares. | Must remain available from Smart Accounts and Raw EOA Mode without an Arenaton-held balance. |
Category Rules
Section titled “Category Rules”Sports
Section titled “Sports”Sports Markets use approved official league or reputable final-result sources. Live trading can continue before and during games, but final resolution waits for the configured Correction Window after the game is complete.
Examples of material live updates that advance Live State Version:
- Score changes.
- Period or clock changes.
- Final whistle or official game completion.
- Official delay, postponement, cancellation, or abandoned event state.
- Data feed outage or conflict that affects trading safety.
Esports
Section titled “Esports”Esports Markets are limited to approved top-tier events and data sources. A Market must name the match, map, series, tournament, scoring rule, and source hierarchy before trading opens.
If feeds disagree or a match is remade, forfeited, or abandoned, the Market follows the published Invalid Path or goes to resolver review. Arenaton must not improvise a new rule after trading starts.
Crypto
Section titled “Crypto”Crypto Markets must use objective price, on-chain, or event sources. The Market terms must identify the venue, price index, timestamp, block range, oracle, or contract event used for resolution.
If a source is unavailable, manipulated, or ambiguous beyond the published tolerance, the Invalid Path applies. A feed outage cannot create a fake final result.
Valid And Invalid Payouts
Section titled “Valid And Invalid Payouts”First-launch binary Markets use Gnosis Conditional Tokens Framework payout vectors:
| Final state | Payout vector | Redemption result |
|---|---|---|
| YES wins | [1, 0] | YES Outcome Shares redeem, NO Outcome Shares redeem for zero Collateral. |
| NO wins | [0, 1] | NO Outcome Shares redeem, YES Outcome Shares redeem for zero Collateral. |
| Invalid Market | [1, 1] | Each binary Outcome Share redeems for 50% of one unit of Collateral. |
No internal refund balance is created for invalid Markets. Invalid resolution is a CTF payout rule, not an Arenaton custody promise.
Lifecycle Policy
Section titled “Lifecycle Policy”OPEN_PRE_EVENT or OPEN_LIVE Market is tradable under current Live State Version.
CLOSING New matches stop; eligible pre-close pending fills can settle only under deterministic rules.
CLOSED_PENDING_RESOLUTION Resolver reviews Resolution Source and waits through the Correction Window.
RESOLVED or INVALID Payout vector is finalized; users can redeem directly.Market terms cannot change after open. A Market cannot reopen after final resolution. Resolution Source and Invalid Path must match the terms shown before order signing.
Direct Redemption
Section titled “Direct Redemption”Direct Redemption means users redeem Outcome Shares through CTF redemption mechanics or a non-custodial transaction path. Arenaton can prepare transaction data, batch Smart Account calls, and index redeemable Markets, but it must not require a claim against an Arenaton internal balance.
Required redemption data:
marketIdconditionIdcollateralTokenparentCollectionIdindexSetspayoutVectorresolutionSourceinvalidPathredeemableFromSmart Accounts can use batched or sponsored redemption when available. Raw EOA Mode users must be able to redeem directly with their own POL gas if the Paymaster is unavailable.
Operator Rules
Section titled “Operator Rules”- Resolver/admin roles must stay separate from market-maker roles.
- Every resolution links to source data, resolver action, and final payout vector.
- Every Invalid Path action is audit logged.
- Incident controls can stop new exposure but cannot seize Collateral or Outcome Shares.
- Correction Window delays finalization; it does not permit changing Market terms.