Deployment Addresses V2
Always verify addresses against the official kleros-v2 repository before use. Addresses change with protocol upgrades. All core contracts use the UUPS proxy pattern - proxy addresses remain stable across upgrades.Arbitrum One (Chain ID: 42161)
Core Contracts
RNG Contracts
Tokens
Gated Court Eligibility (SBT) Contracts
These soulbound token contracts are used as eligibility gates for specific courts. Jurors must hold the corresponding SBT to stake in those courts.Governance Override Contracts
KlerosCoreRuler and DisputeResolverRuler are governance and testing tools that allow manual ruling overrides without jury participation. They are not part of the standard dispute flow.
Snapshot Proxy
Ethereum Mainnet (Chain ID: 1)
For full V1 contract addresses on Ethereum (KlerosLiquid Court, PolicyRegistry, ArbitrableProxy, Realitio proxies, T2CR, Proof of Humanity, Governors, etc.), see V1 Deployment Addresses.
Polygon (Chain ID: 137)
Paired with the Realitio Cross-chain Polygon Foreign Proxy on Ethereum (see V1 Deployment Addresses). Used by Polkamarkets and other Polygon prediction markets.
Arbitrum Sepolia (Chain ID: 421614) - Official Testnet
Core Contracts
RNG Contracts
Test Tokens & Faucets
Ethereum Sepolia (Chain ID: 11155111) - Testnet
Chiado / Gnosis Testnet (Chain ID: 10200) - Official Testnet
Notes
- Proxy vs Implementation: All core contracts use the UUPS proxy pattern. Always interact with the proxy address. Implementation addresses are only needed for direct ABI inspection.
- Testnet parameters: Testnet court parameters (minStake, feeForJuror, timesPerPeriod) differ significantly from mainnet - see Court Hierarchy for details.
- Dispute Kits: The General Court on Arbitrum One supports all four kits (Classic, Shutter, Gated, GatedShutter). The active kit for a dispute is determined by the
extraDatapassed at dispute creation. - Canonical source: Always cross-reference with kleros-v2/contracts/deployments for the most up-to-date addresses.