Skip to main content
The Dispute Resolver (formerly “Resolve”) is a V1 web app at resolve.kleros.io that lets users create disputes in Kleros Court V1 directly, without building a custom arbitrable contract. Users define the dispute question, options, and evidence, then submit it to Court for resolution. Under the hood, disputes are created through the V1 ArbitrableProxy. Evidence submission and appeal management happen through the Dispute Resolver interface.
“Dispute Resolver” refers to different things in V1 and V2:
  • V1 (this page): the standalone Dispute Resolver app at resolve.kleros.io, backed by the ArbitrableProxy contract on Kleros Court V1. The V1 IDisputeResolver interface (NPM package) lets custom V1 arbitrable contracts use this app for evidence and appeal funding.
  • V2: there is no separate app. Dispute creation is built into the Court V2 interface and backed by the V2 DisputeResolver contract (see Arbitrable Overview and Deployment Addresses).

​
Technical notes

  • File uploads: evidence uploads go through Atlas to IPFS, with a SIWE info message at the upload step
  • Evidence display: the interface fetches data from dynamic scripts for flexible evidence display, and normalizes PoH evidence payloads (including older submissions and non-object payloads)
  • MetaEvidence: fetched via an API-based approach
  • Realitio cases: ruling options display correctly for Realitio disputes
  • Dispute creation: the create-dispute form validates inputs before submission

​
Supported networks

The Dispute Resolver can create and manage disputes only on chains where the Kleros V1 Court is deployed (a local arbitrator plus an Arbitrable Proxy):
The network selector also lists several other chains — including Polygon, Arbitrum One, Optimism, Base (and Base Sepolia), zkSync Era, Unichain, and Redstone — that come from a shared Kleros network configuration. These are cross-chain entries with no V1 Court and no Arbitrable Proxy deployed, so they appear in the list but creating a dispute on them does not work. Use one of the supported networks above.
For the history of changes, see the Changelog and the Kleros blog developer updates.