The Resolution Process
Step 1: Market Closes
At the specified bidding deadline, trading stops:Step 2: Outcome Determined
At resolution time, the actual outcome is reported:Step 3: Winning Range Identified
The system determines which bucket/range contains the outcome:Step 4: Winners Claim
Winners can claim their payouts:Oracle Sources
Different market types use different data sources:Price Markets (BTC, ETH, etc.)
- Single oracle can malfunction
- Aggregation prevents manipulation
- Decentralized = trustless
Weather Markets
Date/Event Markets
Resolution Criteria
Every market has clear resolution criteria defined at creation.Good Criteria Examples
Bad Criteria Examples
What Makes Good Criteria
| Property | Why It Matters |
|---|---|
| Specific | No ambiguity in interpretation |
| Measurable | Objective, not subjective |
| Verifiable | Can be independently confirmed |
| Time-bound | Clear when resolution happens |
Edge Cases
What if the outcome is exactly on a boundary?
What if the oracle fails?
What if the outcome is outside the market range?
Dispute Mechanism
Note: The decentralized dispute mechanism is currently a work in progress. For the Beta, disputes are handled via community governance channels. What if you disagree with the resolution?Step 1: Challenge Period
Step 2: Evidence Submission
Step 3: Resolution
Timing Guarantees
For Traders
| Event | Guarantee |
|---|---|
| Trading cutoff | Exactly at bidding_deadline |
| Resolution | After resolution_time is crossed |
| Claim availability | Immediately after resolution |
| Claim expiry | Never (claim anytime) |
For Market Creators
| Event | Guarantee |
|---|---|
| Market goes live | Immediately after creation tx confirms |
| LP withdrawal | Immediately after resolution |
Security Measures
Smart Contract Level
Oracle Level
Governance Level
Transparency
Whatβs Verifiable On-Chain
- β All bets and positions
- β Resolution outcome
- β Claim transactions
- β Fee distribution
- β Oracle data submitted
Whatβs Publicly Auditable
- β Resolution criteria (stored in market)
- β Historical resolutions (on-chain history)
- π§ Smart contract code (open source coming soon)
FAQ
βWho decides the winner?β
No human decides. The oracle reports data, the smart contract determines the winning bucket mathematically.βCan the protocol change the outcome?β
No. Once resolution is confirmed (after dispute period), itβs immutable on-chain.βWhat if I forget to claim?β
You can claim anytime. There is no expiry on claims. Your funds remain in the smart contract until you withdraw them.βHow do I know the oracle is honest?β
We use decentralized oracle networks (Pyth, Chainlink) that aggregate multiple data sources. No single party can manipulate.Best Practices
Before Betting
- Read the resolution criteria carefully
- Understand which oracle will be used
- Check the resolution time
After Resolution
- Verify the outcome matches public data
- Claim winnings promptly
- Report discrepancies during dispute window
Next Steps
| FAQ | Common questions answered | FAQ |
| Quick Start | Ready to make a prediction? | Quick Start |

