Disputes & Edge Cases
Understand review states and what to check when a result is challenged
A dispute challenges a proposed outcome before it becomes final. While the oracle process is active, positions cannot be claimed and the final result may still change.
Statuses you may see
| Status | Action |
|---|---|
| Dispute window | Review the proposal and the remaining challenge time |
| Disputed | Wait while the challenge is evaluated |
| Final review | Monitor the market timeline for the final result |
| Final | Claim a winning position when available |
When supported, Dreamsea shows a Dispute action linking to the oracle flow.
Before disputing
- Read the complete market rules.
- Confirm the relevant date, timezone, threshold, and named source.
- Gather public evidence that directly addresses the resolution criteria.
- Follow the oracle instructions and deadlines shown in the dispute flow.
A disagreement with the market price is not evidence of an incorrect resolution. Disputes must address the written rules and their resolution source.
Common edge cases
- A source publishes a correction after the first report.
- The event is delayed, canceled, or completed after the expected time.
- The title is ambiguous but the detailed rules are specific.
- Two platforms use similar titles with different criteria.
- An oracle review takes longer than the initial countdown.
If the timeline appears inconsistent, contact support with the market link, wallet address, relevant evidence, and transaction hash if an onchain action failed.