Documentation Index
Fetch the complete documentation index at: https://kleros-mintlify-changelog-2026-05-12-1778458371.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Testnet Deployments (Arbitrum Sepolia)
The Vea testnet runs on Arbitrum Sepolia → Chiado (Gnosis testnet) and Arbitrum Sepolia → Ethereum Sepolia. These replace the deprecated Goerli-based devnets.Goerli-based deployments (Arbitrum Goerli → Chiado, Arbitrum Goerli → Goerli) are deprecated as Goerli was sunset in September 2024. Migrate to Sepolia equivalents.
0x407DDEC61d69b212498B140a26da70AE1C879f5a
Arbitrum Sepolia → Chiado (Gnosis Testnet)
| Contract | Address |
|---|---|
| VeaInbox (ArbToGnosisDevnet) | 0x660daB9A6436A814a6ae3a6f27b309356a4bE78c |
| Router (ArbToGnosisDevnet) | 0xD4847f86Ed2E9D03839B15fd0818759861c063a8 |
| VeaOutbox (ArbToGnosisDevnet) | 0xdFd7aDEb43d46FA3f16FB3e27F7fe85c3f5BD89D |
Mainnet Deployments
Vea mainnet deployments (Arbitrum One → Ethereum Mainnet, Arbitrum One → Gnosis Chain) are currently in the process of being finalized. The Kleros V2 cross-chain arbitration system uses foreign gateways that communicate via Vea.
- Check Vea GitHub repository deployment artifacts
- Check Kleros V2 deployment addresses for the Foreign Gateway addresses that use Vea
Kleros Gateway Addresses
The Kleros cross-chain arbitration gateways are separate from Vea itself. See the full address list:Kleros V2 Deployment Addresses
KlerosCore, SortitionModule, DisputeKit, Gateway contract addresses on Arbitrum One and testnets
Finding Addresses Programmatically
Clone the Vea repository to inspect deployment artifacts:VeaInboxArbToEth.json) contains the address field with the deployed contract address and the ABI.
Related
Vea Bridge Architecture
How Vea works, epoch system, and supported routes
Getting Started with Vea
Integration guide and example contracts