diff --git a/court/court-hierarchy.mdx b/court/court-hierarchy.mdx index a824cb5..41f1fee 100644 --- a/court/court-hierarchy.mdx +++ b/court/court-hierarchy.mdx @@ -174,7 +174,7 @@ The following table shows the production court configuration as deployed. Values | 32 | Corte de Defensores del Cliente | 29 | 8,400 | 0.0054 | 15 | No | -Courts 29 and 32 (Argentina Consumer Protection courts) use `DisputeKitGated` and require specific SBT eligibility tokens. See [Deployment Addresses](/reference/contracts/deployment-addresses) for SBT contract addresses. +Courts 29 and 32 (Argentina Consumer Protection courts) use `DisputeKitGated` and require specific SBT eligibility tokens. See [Deployment Addresses V2](/reference/contracts/deployment-addresses) for SBT contract addresses. ### Testnet Parameters (Arbitrum Sepolia) diff --git a/court/how-it-works.mdx b/court/how-it-works.mdx index f3d0eab..916d2b7 100644 --- a/court/how-it-works.mdx +++ b/court/how-it-works.mdx @@ -212,7 +212,7 @@ Kleros V2 introduces modular dispute resolution through pluggable Dispute Kits. | 3 | **Gated** | Classic voting restricted to jurors holding a specific eligibility token (SBT). Used for courts requiring verified credentials. | Live | | 4 | **GatedShutter** | Gated eligibility combined with Shutter encryption. | Live | -All four kits are deployed and registered on the General Court on Arbitrum One. Specialized courts (e.g., courts 29 and 32 for Argentina Consumer Protection) use DisputeKitGated and require specific SBTs - see [Deployment Addresses](/reference/contracts/deployment-addresses). The dispute kit architecture is extensible; new kits can be added through governance. +All four kits are deployed and registered on the General Court on Arbitrum One. Specialized courts (e.g., courts 29 and 32 for Argentina Consumer Protection) use DisputeKitGated and require specific SBTs - see [Deployment Addresses V2](/reference/contracts/deployment-addresses). The dispute kit architecture is extensible; new kits can be added through governance. --- diff --git a/developers/arbitrable-apps/arbitrable-guide.mdx b/developers/arbitrable-apps/arbitrable-guide.mdx index 70fbfda..93343b9 100644 --- a/developers/arbitrable-apps/arbitrable-guide.mdx +++ b/developers/arbitrable-apps/arbitrable-guide.mdx @@ -3,6 +3,10 @@ title: "Arbitrable Apps V2" description: "Step-by-step guide to building a Kleros V2 arbitrable smart contract, from IArbitratorV2 integration to dispute creation, evidence, and ruling." --- + +This guide is specific to Kleros V2: it uses the `IArbitrableV2` and `IArbitratorV2` interfaces and KlerosCore on Arbitrum. To build against Kleros V1 (ERC-792 and ERC-1497), see [V1 Arbitrable Apps](/developers/arbitrable-apps/v1-arbitrable-apps). + + ## Interface Reference Before building, understand the two interfaces your contract interacts with. diff --git a/developers/arbitrable-apps/arbitrable-overview.mdx b/developers/arbitrable-apps/arbitrable-overview.mdx index f03ef36..259ae0c 100644 --- a/developers/arbitrable-apps/arbitrable-overview.mdx +++ b/developers/arbitrable-apps/arbitrable-overview.mdx @@ -5,7 +5,7 @@ description: "Design patterns and interface choices for building arbitrable smar ## What is an Arbitrable Contract? -An arbitrable contract is any smart contract that can create disputes and enforce rulings from Kleros. Your contract implements the `IArbitrableV2` interface, which defines two things: +An arbitrable contract is any smart contract that can create disputes and enforce rulings from Kleros. Your contract implements an arbitrable interface (`IArbitrableV2` in Kleros V2, ERC-792 in V1), which defines two things: 1. **How disputes are created**: your contract decides when conflicts arise 2. **How rulings are enforced**: your contract executes the outcome @@ -90,9 +90,13 @@ Decide how evidence reaches jurors: - **Separate module** Use the `EvidenceModule` contract - **Cross-chain** Evidence from foreign chain via gateway -## Interface Requirements +## Interface Requirements (V2) -Your contract must implement: + +This section is specific to Kleros V2. For V1, contracts implement [ERC-792](/developers/arbitrable-apps/erc-792) and [ERC-1497](/developers/arbitrable-apps/erc-1497) instead, and must emit a `MetaEvidence` event so the Court interface can display the dispute. + + +To integrate with Kleros V2, your contract must implement: ```solidity interface IArbitrableV2 { diff --git a/developers/arbitrable-apps/arbitrable-testing.mdx b/developers/arbitrable-apps/arbitrable-testing.mdx index 4e89c4e..09fe0d6 100644 --- a/developers/arbitrable-apps/arbitrable-testing.mdx +++ b/developers/arbitrable-apps/arbitrable-testing.mdx @@ -9,18 +9,19 @@ Testing arbitrable contracts requires simulating the full dispute lifecycle. You ```mermaid graph TB - subgraph Testing Layers + subgraph TL["Testing Layers"] direction TB - L1["1. Unit Tests
Your contract logic in isolation
with MockArbitrator"] - L2["2. Integration Tests
With mock arbitrator + dispute lifecycle"] - L3["3. Testnet
With real Kleros on Arbitrum Sepolia"] - L4["4. Mainnet Fork
Simulate with production KlerosCore state"] + L1["Layer 1: Unit Tests
Contract logic in isolation with MockArbitrator"] + L2["Layer 2: Integration Tests
Mock arbitrator plus full dispute lifecycle"] + L3["Layer 3: Testnet
Real Kleros on Arbitrum Sepolia"] + L4["Layer 4: Mainnet Fork
Production KlerosCore state"] + L1 --> L2 --> L3 --> L4 end - L1 --> L2 --> L3 --> L4 - style L1 fill:#e8e0f0,stroke:#7b5ea7 - style L2 fill:#d8ccf0,stroke:#7b5ea7 - style L3 fill:#c4b0e8,stroke:#7b5ea7 - style L4 fill:#7b5ea7,color:#fff,stroke:#5a3d8a + style TL fill:transparent,stroke:#7b5ea7 + style L1 fill:#ede7f6,stroke:#7b5ea7,color:#1a1a2e + style L2 fill:#d1c4e9,stroke:#7b5ea7,color:#1a1a2e + style L3 fill:#9575cd,stroke:#5a3d8a,color:#ffffff + style L4 fill:#5e35b1,stroke:#4a2d91,color:#ffffff ``` ## Unit Testing with Mock Arbitrator diff --git a/developers/arbitrable-apps/centralized-arbitrator.mdx b/developers/arbitrable-apps/centralized-arbitrator.mdx index abf3103..4145020 100644 --- a/developers/arbitrable-apps/centralized-arbitrator.mdx +++ b/developers/arbitrable-apps/centralized-arbitrator.mdx @@ -9,6 +9,10 @@ description: "Developer guide to deploying and operating the Centralized Arbitra The Centralized Arbitrator dashboard allows anyone to quickly deploy and operate a centralized arbitrator from a graphical interface. It serves as a testing and debugging tool for arbitrable apps integrating with Kleros Court. + +This is a V1 tool. The dashboard deploys an `AutoAppealableArbitrator` contract that implements the [ERC-792](/developers/arbitrable-apps/erc-792) arbitrator interface, so it is used for testing V1 (ERC-792) arbitrable contracts. + + --- ## How It Works diff --git a/developers/architecture.mdx b/developers/architecture.mdx index d45de8a..ce625ab 100644 --- a/developers/architecture.mdx +++ b/developers/architecture.mdx @@ -22,10 +22,14 @@ graph TB | **KlerosLiquid** | Staking, juror drawing, voting, appeals, ruling execution | | **PNK** | Staking token | | **PolicyRegistry** | Court policy storage | -| **Arbitrable contracts** | Implement ERC-792 to create disputes and receive rulings | +| **Arbitrable contracts** | Implement ERC-792 to create disputes and receive rulings, and ERC-1497 to provide dispute context | V1 uses the ERC-792 (arbitration) and ERC-1497 (evidence) standards, blockhash-based randomness, commit-reveal plurality voting, and a hierarchical subcourt tree. For V1 contract addresses, see [Deployment Addresses](/reference/contracts/deployment-addresses-v1). + +A V1 arbitrable contract must implement [ERC-1497](/developers/arbitrable-apps/erc-1497) in addition to ERC-792. In particular, it must emit a `MetaEvidence` event and link disputes to it with a `Dispute` event. The Court interface relies on `MetaEvidence` to display the dispute and its ruling options to jurors. An arbitrable that never emits `MetaEvidence` produces disputes that cannot be adjudicated properly. + + ## V2 System Overview Kleros V2 uses a modular architecture where specialized contracts handle specific responsibilities: diff --git a/developers/products/curate/curate-classic.mdx b/developers/products/curate/curate-classic.mdx index d88ed9a..cdd6583 100644 --- a/developers/products/curate/curate-classic.mdx +++ b/developers/products/curate/curate-classic.mdx @@ -84,7 +84,7 @@ Call `executeRequest()` after the challenge period passes without a challenge. Source code - - Curate subgraph on The Graph + + legacy-curate-mainnet subgraph on Graph Explorer \ No newline at end of file diff --git a/developers/subgraph/endpoints.mdx b/developers/subgraph/endpoints.mdx index 8b81ac9..241cc52 100644 --- a/developers/subgraph/endpoints.mdx +++ b/developers/subgraph/endpoints.mdx @@ -7,6 +7,8 @@ description: "GraphQL endpoints for Kleros V2 core, DRT, and V1 subgraphs on Arb All Kleros subgraphs are deployed on The Graph. Use these endpoints to query Kleros data via GraphQL. +Every subgraph published by Kleros on The Graph decentralized network is listed on the [Kleros deployer profile on Graph Explorer](https://thegraph.com/explorer/profile/0x7f3a845bf7aa9eb6da3dc53518ff22a2f65612e6?chain=arbitrum-one&view=Subgraphs). Each Explorer page shows the subgraph ID and the exact query URL. + **Infrastructure:** Subgraphs were migrated from Alchemy to Goldsky following Alchemy's subgraph service shutdown (December 2025–January 2026). The core subgraph 0.18.1 and DRT subgraph 0.14.0 were deployed on Goldsky (November 2025), and the GTCR Indexer reached v0.1.7 with an Envio branch (April 2026). Some applications use Envio HyperIndex as the primary indexer with a subgraph as fallback. @@ -24,25 +26,23 @@ Subgraph endpoints on the decentralized network require a **Graph API key**. Get -| Environment | Network | Studio Page | -| --- | --- | --- | -| Mainnet | Arbitrum One | [kleros-v2-coreneo](https://thegraph.com/studio/subgraph/kleros-v2-coreneo/) | -| Testnet | Arbitrum Sepolia | [kleros-v2-core-testnet](https://thegraph.com/studio/subgraph/kleros-v2-core-testnet/) | -| Devnet | Arbitrum Sepolia | [kleros-v2-core-devnet](https://thegraph.com/studio/subgraph/kleros-v2-core-devnet/) | +| Environment | Network | Explorer Page | Subgraph ID | +| --- | --- | --- | --- | +| Mainnet | Arbitrum One | [kleros-v2-coreneo](https://thegraph.com/explorer/subgraphs/3U95wXKP8fBpkMNn8mbroVkUTuh6KtHGa456pTixx9B2) | `3U95wXKP8fBpkMNn8mbroVkUTuh6KtHGa456pTixx9B2` | +| Testnet | Arbitrum Sepolia | [kleros-v2-core-testnet](https://thegraph.com/explorer/subgraphs/77xeh3UeBCzHokbVtkeaH42vXsFh6MRe4JpZSPddoXZo) | `77xeh3UeBCzHokbVtkeaH42vXsFh6MRe4JpZSPddoXZo` | +| Devnet | Arbitrum Sepolia | [kleros-v2-core-devnet](https://thegraph.com/explorer/subgraphs/4Rg3NAW99hX8RDD281ycfeRWxp92k6RdqpW3pf6imGTS) | `4Rg3NAW99hX8RDD281ycfeRWxp92k6RdqpW3pf6imGTS` | **Decentralized network query URL pattern:** ``` https://gateway.thegraph.com/api/{YOUR_API_KEY}/subgraphs/id/{SUBGRAPH_ID} ``` -Get the `SUBGRAPH_ID` (deployment hash) from the Studio pages linked above - it is shown on the subgraph's Overview tab. - ### Dispute Template Registry Subgraph -| Environment | Network | Studio Page | -| --- | --- | --- | -| Mainnet | Arbitrum One | [kleros-v2-drt](https://thegraph.com/studio/subgraph/kleros-v2-drt/) | -| Testnet | Arbitrum Sepolia | [kleros-v2-drt-arbisep-testnet](https://thegraph.com/studio/subgraph/kleros-v2-drt-arbisep-testnet/) | +| Environment | Network | Explorer Page | Subgraph ID | +| --- | --- | --- | --- | +| Mainnet | Arbitrum One | [kleros-v2-drt](https://thegraph.com/explorer/subgraphs/FktCcvKHN9mdcyNMK1jgnKwf5AwmVXka4kATxXX3HmKT) | `FktCcvKHN9mdcyNMK1jgnKwf5AwmVXka4kATxXX3HmKT` | +| Testnet | Arbitrum Sepolia | [kleros-v2-drt-arbisep-testnet](https://thegraph.com/explorer/subgraphs/EZjJCfxBiQ9B9RtfQDTzNKx34nckSnBWDNaLZPficnHp) | `EZjJCfxBiQ9B9RtfQDTzNKx34nckSnBWDNaLZPficnHp` | --- @@ -50,10 +50,10 @@ Get the `SUBGRAPH_ID` (deployment hash) from the Studio pages linked above - it ### Escrow V2 -| Environment | Network | Subgraph ID | -| --- | --- | --- | -| Mainnet | Arbitrum One | `96vpnRJbRVkzF6usMNYMMoziSZEfSwGEDpXNi2h9WBSW` | -| Devnet | Arbitrum Sepolia | `3aZxYcZpZL5BuVhuUupqVrCV8VeNyZEvjmPXibyPHDFQ` | +| Environment | Network | Explorer Page | Subgraph ID | +| --- | --- | --- | --- | +| Mainnet | Arbitrum One | [escrow-v2-neo](https://thegraph.com/explorer/subgraphs/96vpnRJbRVkzF6usMNYMMoziSZEfSwGEDpXNi2h9WBSW) | `96vpnRJbRVkzF6usMNYMMoziSZEfSwGEDpXNi2h9WBSW` | +| Devnet | Arbitrum Sepolia | [escrow-v2-devnet](https://thegraph.com/explorer/subgraphs/3aZxYcZpZL5BuVhuUupqVrCV8VeNyZEvjmPXibyPHDFQ) | `3aZxYcZpZL5BuVhuUupqVrCV8VeNyZEvjmPXibyPHDFQ` | Full query URL (mainnet): ``` @@ -62,7 +62,7 @@ https://gateway.thegraph.com/api/{YOUR_API_KEY}/subgraphs/id/96vpnRJbRVkzF6usMNY ### Curate V2 -Curate V2 subgraph is under active development. Check the [curate-v2 repository](https://github.com/kleros/curate-v2/tree/master/subgraph) for the latest deployment. +Curate V2 subgraph is under active development. A devnet deployment is published as [curate-v2-devnet](https://thegraph.com/explorer/subgraphs/H93eWJbDpYKAtkLmsMn7Su3ZLZwAwLN5VoyvQH4NbGAv). Check the [curate-v2 repository](https://github.com/kleros/curate-v2/tree/master/subgraph) for the latest deployment. --- @@ -70,24 +70,38 @@ Curate V2 subgraph is under active development. Check the [curate-v2 repository] These index V1 Kleros products still in active use. + +The Graph hosted service (`thegraph.com/hosted-service/...` URLs) has been shut down. Old hosted-service endpoints no longer work. + + ### Curate V1 -| Network | Endpoint | -| --- | --- | -| Ethereum Mainnet | `https://thegraph.com/hosted-service/subgraph/kleros/curate` | -| Gnosis Chain | `https://thegraph.com/hosted-service/subgraph/kleros/legacy-curate-xdai` | +| Network | Explorer Page | Subgraph ID | +| --- | --- | --- | +| Ethereum Mainnet | [legacy-curate-mainnet](https://thegraph.com/explorer/subgraphs/A5oqWboEuDezwqpkaJjih4ckGhoHRoXZExqUbja2k1NQ) | `A5oqWboEuDezwqpkaJjih4ckGhoHRoXZExqUbja2k1NQ` | +| Gnosis Chain | [legacy-curate-gnosis](https://thegraph.com/explorer/subgraphs/9hHo5MpjpC1JqfD3BsgFnojGurXRHTrHWcUcZPPCo6m8) | `9hHo5MpjpC1JqfD3BsgFnojGurXRHTrHWcUcZPPCo6m8` | + +The Curate application at [curate.kleros.io](https://curate.kleros.io) queries these public Goldsky endpoints, which require no API key: + +``` +https://api.goldsky.com/api/public/project_cmgx9all3003atlp2bqha1zif/subgraphs/pgtcr-mainnet/0.0.3/gn +https://api.goldsky.com/api/public/project_cmgx9all3003atlp2bqha1zif/subgraphs/pgtcr-gnosis/0.0.3/gn +https://api.goldsky.com/api/public/project_cmgx9all3003atlp2bqha1zif/subgraphs/pgtcr-sepolia/0.0.3/gn +``` ### Proof of Humanity V1 -| Network | Endpoint | -| --- | --- | -| Ethereum Mainnet | `https://thegraph.com/hosted-service/subgraph/kleros/proof-of-humanity-mainnet` | +The Proof of Humanity application at [app.proofofhumanity.id](https://app.proofofhumanity.id) queries this public Studio endpoint: + +``` +https://api.studio.thegraph.com/query/61738/proof-of-humanity-mainnet/version/latest +``` -You can also query PoH V1 directly: call `isRegistered(address)` on `0xC5E9dDebb09Cd64DfaCab4011A0D5cEDaf7c9BDb` on Ethereum Mainnet. +You can also query PoH V1 directly on-chain: call `isRegistered(address)` on `0xC5E9dDebb09Cd64DfaCab4011A0D5cEDaf7c9BDb` on Ethereum Mainnet. ### Other V1 Products -For Escrow V1, Linguo, Tokens, and other V1 apps, see the [Kleros subgraph list on GitHub](https://github.com/orgs/kleros/repositories?q=subgraph). +For Escrow V1, Linguo, Tokens, and other V1 apps, see the [Kleros deployer profile on Graph Explorer](https://thegraph.com/explorer/profile/0x7f3a845bf7aa9eb6da3dc53518ff22a2f65612e6?chain=arbitrum-one&view=Subgraphs) and the [Kleros subgraph repositories on GitHub](https://github.com/orgs/kleros/repositories?q=subgraph). --- diff --git a/developers/subgraph/queries.mdx b/developers/subgraph/queries.mdx index 710cbdc..b680955 100644 --- a/developers/subgraph/queries.mdx +++ b/developers/subgraph/queries.mdx @@ -226,7 +226,7 @@ Batched query to fetch address tags from the three Kleros address tag registries } ``` -Endpoint: `https://thegraph.com/hosted-service/subgraph/kleros/legacy-curate-xdai` +Subgraph: [legacy-curate-gnosis](https://thegraph.com/explorer/subgraphs/9hHo5MpjpC1JqfD3BsgFnojGurXRHTrHWcUcZPPCo6m8) on Graph Explorer (subgraph ID `9hHo5MpjpC1JqfD3BsgFnojGurXRHTrHWcUcZPPCo6m8`) --- diff --git a/docs.json b/docs.json index 028f629..f4d0246 100644 --- a/docs.json +++ b/docs.json @@ -217,14 +217,24 @@ "group": "Arbitrable Apps", "pages": [ "developers/arbitrable-apps/arbitrable-overview", - "developers/arbitrable-apps/v1-arbitrable-apps", - "developers/arbitrable-apps/arbitrable-guide", - "developers/arbitrable-apps/erc-792", - "developers/arbitrable-apps/erc-1497", - "developers/arbitrable-apps/centralized-arbitrator", - "developers/arbitrable-apps/arbitrable-proxy", - "developers/arbitrable-apps/arbitrable-testing", - "developers/arbitrable-apps/arbitrable-production" + { + "group": "Building on V2", + "pages": [ + "developers/arbitrable-apps/arbitrable-guide", + "developers/arbitrable-apps/arbitrable-testing", + "developers/arbitrable-apps/arbitrable-production" + ] + }, + { + "group": "Building on V1", + "pages": [ + "developers/arbitrable-apps/erc-792", + "developers/arbitrable-apps/erc-1497", + "developers/arbitrable-apps/v1-arbitrable-apps", + "developers/arbitrable-apps/centralized-arbitrator", + "developers/arbitrable-apps/arbitrable-proxy" + ] + } ] }, { @@ -309,27 +319,36 @@ ] }, { - "group": "Contracts", + "group": "Architecture", + "pages": [ + "reference/architecture/v2-architecture", + "reference/architecture/arbitrator-v2", + "reference/architecture/sortition-module-spec", + "reference/architecture/vea-overview" + ] + }, + { + "group": "Contracts (V2)", "pages": [ - "reference/contracts/deployment-addresses-v1", "reference/contracts/deployment-addresses", - { - "group": "Reference V2", - "pages": [ - "reference/contracts/kleros-core", - "reference/contracts/dispute-kit-classic", - "reference/contracts/sortition-module", - "reference/contracts/dispute-template-registry", - "reference/contracts/policy-registry", - "reference/contracts/kleros-governor", - "reference/contracts/gateways" - ] - }, + "reference/contracts/kleros-core", + "reference/contracts/dispute-kit-classic", + "reference/contracts/sortition-module", + "reference/contracts/gateways", + "reference/contracts/kleros-governor", + "reference/contracts/policy-registry", + "reference/contracts/dispute-template-registry", "reference/contracts/moderated-evidence-module" ] }, { - "group": "Data Formats", + "group": "Contracts (V1)", + "pages": [ + "reference/contracts/deployment-addresses-v1" + ] + }, + { + "group": "Data Formats (V2)", "pages": [ "reference/data-formats/dispute-templates", "reference/data-formats/evidence-format", @@ -339,7 +358,7 @@ ] }, { - "group": "SDK", + "group": "SDK (V2)", "pages": [ "reference/sdk/kleros-sdk" ] diff --git a/enterprise/enterprise.mdx b/enterprise/enterprise.mdx index 5eccf3f..059a6a6 100644 --- a/enterprise/enterprise.mdx +++ b/enterprise/enterprise.mdx @@ -5,8 +5,12 @@ description: "Kleros Enterprise offers companies, institutions, and governments # Kleros Enterprise - - Kleros Enterprise, screenshot to be added + + + + + + **Kleros Enterprise** is a neutral dispute resolution system for businesses and governments, designed for speed, fairness, and transparency. Companies, institutions, and governments use Kleros dispute resolution technology to resolve disputes within their own platforms or services. The blockchain complexity is abstracted away: neither the organization nor its users need to handle crypto or interact with smart contracts directly. @@ -110,6 +114,12 @@ Specific use cases include protocol governance disputes, on-chain moderation, or ## Get Started + + Kleros Enterprise overview and customer complaint resolution offering + + + Resolución de disputas para empresas, in Spanish + integrations@kleros.io diff --git a/images/Enterprise-hero1.png b/images/Enterprise-hero1.png new file mode 100644 index 0000000..a1aab02 Binary files /dev/null and b/images/Enterprise-hero1.png differ diff --git a/images/Enterprise-hero2.png b/images/Enterprise-hero2.png new file mode 100644 index 0000000..829d058 Binary files /dev/null and b/images/Enterprise-hero2.png differ diff --git a/reference/contracts/deployment-addresses-v1.mdx b/reference/contracts/deployment-addresses-v1.mdx index a5a3a1c..b2b0157 100644 --- a/reference/contracts/deployment-addresses-v1.mdx +++ b/reference/contracts/deployment-addresses-v1.mdx @@ -3,7 +3,7 @@ title: Deployment Addresses V1 description: "KlerosLiquid V1 contract addresses on Ethereum Mainnet and Gnosis Chain: Court, Curate, Escrow, Governor, and arbitrable app deployments." --- -This page lists the V1 (KlerosLiquid) contract addresses, organized by product. For V2 (KlerosCore on Arbitrum) addresses, see the [Deployment Addresses](/reference/contracts/deployment-addresses) reference page. For cross-chain infrastructure, see [Vea Deployment Addresses](/developers/crosschain/vea-deployment-addresses). +This page lists the V1 (KlerosLiquid) contract addresses, organized by product. For V2 (KlerosCore on Arbitrum) addresses, see the [Deployment Addresses V2](/reference/contracts/deployment-addresses) reference page. For cross-chain infrastructure, see [Vea Deployment Addresses](/developers/crosschain/vea-deployment-addresses). Base and Arbitrum Vea routes were deployed in June 2026. The `veashi-sdk` is available on npm as `@kleros/veashi-sdk` v0.0.2. @@ -43,7 +43,7 @@ Base and Arbitrum Vea routes were deployed in June 2026. The `veashi-sdk` is ava ### V2 (Arbitrum) -See [Deployment Addresses](/reference/contracts/deployment-addresses) for KlerosCore, SortitionModule, and other V2 contracts. +See [Deployment Addresses V2](/reference/contracts/deployment-addresses) for KlerosCore, SortitionModule, and other V2 contracts. --- @@ -69,7 +69,7 @@ These registries power Kleros Scout and are consumed by block explorers for addr ### V2 (Arbitrum) -See [Deployment Addresses](/reference/contracts/deployment-addresses). +See [Deployment Addresses V2](/reference/contracts/deployment-addresses). --- @@ -83,7 +83,7 @@ See [Deployment Addresses](/reference/contracts/deployment-addresses). ### V2 (Arbitrum) -See [Deployment Addresses](/reference/contracts/deployment-addresses). +See [Deployment Addresses V2](/reference/contracts/deployment-addresses). --- diff --git a/reference/contracts/deployment-addresses.mdx b/reference/contracts/deployment-addresses.mdx index 4b6868d..8e044ea 100644 --- a/reference/contracts/deployment-addresses.mdx +++ b/reference/contracts/deployment-addresses.mdx @@ -1,9 +1,9 @@ --- -title: "Deployment Addresses V2" -description: "Kleros V2 smart contract addresses on Arbitrum One: KlerosCore, DisputeKitClassic, Sortition Module, PolicyRegistry, and UUPS proxies." +title: Deployment Addresses V2 +description: Smart contract addresses for Kleros V2 on all supported networks --- -# Deployment Addresses +# Deployment Addresses V2 Always verify addresses against the [official kleros-v2 repository](https://github.com/kleros/kleros-v2/tree/master/contracts/deployments) before use. Addresses change with protocol upgrades. All core contracts use the UUPS proxy pattern - proxy addresses remain stable across upgrades. diff --git a/reference/overview.mdx b/reference/overview.mdx index 902c62f..81bc69b 100644 --- a/reference/overview.mdx +++ b/reference/overview.mdx @@ -8,8 +8,11 @@ description: "Kleros V2 technical reference index: contract interfaces, architec Complete technical reference for Kleros V2: contract interfaces, data format specs, protocol architecture, and SDK documentation. - - Contract addresses on all networks + + V2 contract addresses on all networks + + + V1 (KlerosLiquid) contract addresses Core arbitrator contract