Skip to main content
The dispute system provides human oversight over AI-powered market resolutions. While Claude 4.5 Sonnet resolves markets automatically, stakeholders can challenge outcomes they believe are incorrect and vote to override the AI’s determination.
This mechanism ensures that market outcomes reflect reality, even if the AI makes an error in analyzing evidence or applying resolution criteria.

When Disputes Occur

A dispute can be initiated when:
  1. A market has been resolved by the AI with a proposed outcome
  2. A participant believes the AI’s determination is incorrect
  3. The dispute window is still open
Disputes require staking collateral. If the dispute is found to be invalid (the AI was correct), the staker’s bond may be slashed.

Dispute Lifecycle

1

Voting

The dispute is open for votes. Stakeholders cast weighted votes for or against the dispute.
  • Voting weight is based on position size
  • Threshold: >50% of pool weight must vote to activate
  • Duration: Defined by protocol parameters
2

Active

The dispute threshold has been met. Discussion and evidence gathering occur.
  • Messages can be posted on-chain
  • Messages can be boosted with stake
  • Voting continues
3

Resolved

The dispute period has ended. The final outcome is determined by vote weight.
  • If dispute wins: Original outcome is overturned
  • If dispute loses: Original outcome stands
  • Redemption is enabled
4

Expired

The voting period ended without reaching the threshold.
  • Original resolution stands
  • No changes to outcome

Dispute Data Structure


Voting

To vote on a dispute, a user must have a position in the market. Their voting weight equals their position value.

Messages

Dispute discussions happen on-chain via messages. Messages are weighted by the author’s position and can be boosted by other participants.

Posting a Message

Boosting a Message

Boosting signals agreement and increases a message’s visibility.

Message Sorting

Messages are sorted by total weight (author weight + boost amount) by default. This surfaces the most credible arguments.
Alternative: sort_by=timestamp for chronological order.

Fetching Disputes


Next Steps

Resolution

Learn about the resolution process.

API Reference

Full dispute endpoint documentation.