- how participants interact,
- how jurors evaluate information,
- and how outcomes are enforced on-chain.
This section describes the live dispute type and the additional dispute types planned for later versions.
| Types | Purpose | Outcome | Status |
|---|---|---|---|
| Adversarial Dispute | Resolve conflicts between two parties | Winner/Loser | Live |
| Decision Dispute | Validate proposals or decisions | Accept/Reject | Later version |
| Rating Evaluation | Evaluate quality or contribution | Aggregated Score | Later version |
Adversarial Dispute
Status: Live (Current Implementation) Resolves conflicts between two opposing parties: a Claimer and a Defender. Jurors evaluate evidence submitted by both sides and vote on a binding outcome that is enforced on-chain. Used for:- marketplaces,
- freelancer and contractor platforms,
- fintech and payment disputes,
- peer-to-peer conflicts.
Decision Dispute
Status: Later version Designed for collective decision-making rather than conflict resolution. Jurors evaluate whether a proposal or action should be accepted or rejected according to predefined rules. Used for:- governance processes,
- protocol-level decisions,
- structured human validation.
Rating Evaluation
Status: Later version A collective evaluation mechanism based on structured numerical input rather than binary outcomes. Jurors provide ratings that are aggregated to measure quality, performance, or contribution. Used for:- open-source contribution evaluation,
- content moderation,
- quality and performance scoring,
- reputation systems.
Some dispute types may support additional evaluation rounds under stricter conditions.