Skip to main content
This page describes the current live implementation. Other pages may describe later-version features, but this page is the reference for what is live today.

Scope

The current implementation focuses on validating the core mechanics of Justly:
  • Human juries
  • Commit-reveal voting
  • Tier-based dispute configuration
  • Automated on-chain finalization
  • Fast and bounded dispute resolution for online conflicts
All features outside this scope are intentionally excluded from the current version and will be introduced in later versions.

Supported Dispute Type

Public adversarial dispute The live version supports public adversarial disputes between two parties:
  • Claimer: the party initiating the dispute
  • Defender: the counterparty
Both parties:
  • submit evidence,
  • must have their side of the dispute fully funded,
  • and accept the outcome enforced by the protocol.
Those required amounts may be paid by the parties themselves or by a sponsor or platform on their behalf. The dispute is resolved by a group of anonymous human jurors.

Dispute lifecycle

Each dispute follows a deterministic on-chain lifecycle:
  1. Created
    The dispute is created with the parties, tier, and timing parameters.
  2. Evidence
    Once both sides are fully funded, evidence submission opens.
  3. Commit
    Evidence is frozen, juror assignment starts, and selected jurors submit commitments.
  4. Reveal
    Jurors reveal committed votes.
  5. Finished
    The ruling is finalized, incentives are settled, and an optional callback may be attempted.
Current implementation: once finalized, the outcome is final. Later version: appeals add escalation rounds as a first-class escalation mechanism.

Jurors

  • Jurors are human participants selected through protocol-defined assignment.
  • Identity and anti-Sybil layers are part of the broader roadmap.
  • Jurors are pseudonymous to disputing parties.
  • Jurors must stake funds to participate.
  • Stake size influences selection economics, but rulings are not stake-weighted.

Liveness and assignment

Justly is designed to keep disputes moving toward finalization even when juror participation is imperfect. This means:
  • juror assignment begins when Commit starts,
  • the dispute can proceed with fewer selected jurors than the target panel,
  • and finalization remains bounded by the voting deadlines.
Selection details may evolve over time, but these liveness guarantees remain part of the architecture.

Voting and security

  • Voting is executed fully on-chain.
  • A commit-reveal scheme is used to prevent vote manipulation.
  • Shutter-based reveal automation is planned to improve juror UX while preserving the same protocol flow.
  • All state transitions and outcomes are verifiable on-chain.

Tiers

Tiers are the public-facing dispute profiles exposed to platforms and integrators. They package the main economic and procedural values a platform cares about, such as juror stake amounts and arbitration fees. Each tier defines:
  • number of jurors,
  • juror stake requirements,
  • party-side funding requirements,
  • and arbitration fee levels.
Internally, live deployments may still map tiers to court or category configuration. For integrators, tiers remain the simpler abstraction.

Economics

  • Both sides of the dispute must be fully funded before activation.
  • Jurors stake funds to vote.
  • Jurors who vote coherently are rewarded.
  • Jurors who vote incoherently, or fail to complete participation, are penalized according to protocol rules.
  • Tier parameters define the main fee and stake values exposed to integrators.
All economic flows are enforced automatically by smart contracts.

Limitations of the current implementation

The following features are not included in the current implementation:
  • Appeals or dispute escalation
  • Rating or decision-based disputes
  • Automatic reveal via Shutter API integration
These features are planned for later versions. The live version today is focused on adversarial disputes with a single finalized round.

Design philosophy

The current implementation prioritizes:
  • correctness over completeness,
  • reliability,
  • and enforceable outcomes over subjective mediation.
This approach allows Justly to validate its core assumptions while preserving a clear path toward later-version features.