Skip to main content

Networks and Addresses

Verax currently ships default SDK and explorer support for the following networks.

NetworkChain IDPrefixRouterAttestationRegistryModuleRegistryPortalRegistrySchemaRegistryAttestationReaderSubgraph
Linea Sepolia591410x00000xAfA952790492DDeB474012cEA12ba34B788ab39F0xDaf3C3632327343f7df0Baad2dc9144fa4e1001F0x3C443B9f0c8ed3A3270De7A4815487BA3223C2Fa0xF35fe79104e157703dbCC3Baa72a81A99591744D0x90b8542d7288a83EC887229A7C727989C3b56209Not deployedverax-v2-linea-sepolia v0.0.3
Linea Mainnet591440x00000x4d3a380A03f3a18A5dC44b01119839D8674a552E0x3de3893aa4Cdea029e84e75223a152FD083151380xf851513A732996F22542226341748f3C9978438f0xd5d61e4ECDf6d46A63BfdC262af92544DFc190830x0f95dCec4c7a93F2637eb13b655F2223ea036B590x40871e247CF6b8fd8794c9c56bB5c2b8a4FA3B6cverax-v2-linea v0.0.1
Arbitrum Sepolia4216140x00010x374B686137eC0DB442a8d833451f8C12cD4B5De40xee5e23492bf49C1F4CF0676b3bF49d78A6dD61c50xEC572277d4E87a64DcfA774ED219Dd4E69E4BDc60x1ceb52584B6C45C7049dc7fDC476bC138E4beaDE0x025531b655D9EE335B8E6cc4C118b313f26ACc8FNot deployedverax-v2-arbitrum-sepolia v0.0.3
Arbitrum Mainnet421610x00010xa77196867bB03D04786EF636cDdD82f37A1248a90x335E9719e8eFE2a19A92E07BC4836160fC31cd7C0x3acF4daAB6cbc01546Dd4a96c9665B398d48A4ba0x4042D0A54f997EE3a1b0F51e4813654199BFd8bD0xE96072F46EA0e42e538762dDc0aFa4ED8AE6Ec270x324C060A26444c3fB9B93e03d31e8cfF4b1715C1verax-v2-arbitrum v0.0.2
Base Sepolia845320x00050xE235826514945186227918325D3E5b5f873861A60x374B686137eC0DB442a8d833451f8C12cD4B5De40xEC572277d4E87a64DcfA774ED219Dd4E69E4BDc60x025531b655D9EE335B8E6cc4C118b313f26ACc8F0x66D2F3DCc970343b83a6263E20832184fa71CFe70xbCcC37Ea3bEeAE614817f53542F1F4FfAE5E19c7verax-v2-base-sepolia v0.0.3
Base Mainnet84530x00050x63b2d528805Fc9373586366705852FA89debd4d00xA0080DBd35711faD39258E45d9A5D798852b05D40xAd0C12db58098A6665CBEf48f60eB67d81d1F1ff0xcbf28432C25B400E645F0EaC05F8954e8EE7c0d60x8081dCd745f160c148Eb5be510F78628A0951c310xbEDd72a8cCfBEC4e575dCdC1659A891018051a5Cverax-v2-base v0.0.1
BSC Testnet970x00060x90b8542d7288a83EC887229A7C727989C3b562090x5Cc4029f0dDae1FFE527385459D06d81DFD50EEe0x6c46c245918d4fcfC13F0a9e2e49d4E2739A353a0xA4a7517F62216BD42e42a67dF09C25adc72A58970x51929da151eC2C5a5881C750E5b9941eACC46c1dNot deployedverax-v2-bsc-testnet v0.0.2
BSC Mainnet560x00060x7a5C1fAC7fF9908a8b2ED479e060619213116A470x3D8A3a8FF21bD295dbBD5319C399e2C4FD27F2610xD70a06f7A0f197D55Fa841fcF668782b2B8266eB0xb2553A7E443DFA7C9dEc01D327FdDff1A5eF59b00x29205492435E1b06B20CeAeEC4AC41bcF595DFFdNot deployedverax-v2-bsc v0.0.2

How to use this page​

  • For SDK integrations, use the matching VeraxSdk.DEFAULT_* configuration documented in Using the SDK.
  • For manual contract interaction, use the registry addresses above.
  • For cross-chain lookups, use the subgraph names and URLs documented by the SDK defaults and subgraph package.

Notes​

  • The chain prefix is injected by AttestationRegistry and is derived from contracts/script/utils.ts.
  • AttestationReader is only deployed on chains where Verax currently maintains EAS-reading compatibility.
  • Standard-library module addresses exist per network, but the primary addresses most integrators need are the registry and reader addresses above.