Verax Attestation Registry
Links • Repository Organisation • Getting Started • Contributing • Contracts Addresses • Subgraphs URLs • Network Prefixes • License
📚 Documentation
🔍 Subgraphs
🧱 Verax SDK
🌍 Explorer
.
├── contracts # All smart contracts needed to run Verax
├── explorer # Explorer frontend to discover the main objects
├── governance # Governance NFTs
├── sdk # An SDK to easily interact with the contracts and the subgraphs
├── snap # A MetaMask Snap to leverage the attestations in transactions
├── subgraph # The subgraph indexing all the data generated by the contracts
├── website # Verax landing page and
Each package has its own README file for more details and installation process description.
pnpm i
Verax Attestation Registry is a community-led initiative, with developers from various companies and different backgrounds. While we are more than happy to get help from multiple sources, we need to rely on strong Ways of Working.
Don't hesitate to check our Contribution Guide before pushing your first code to the repo!
The main contracts (i.e. the "registries") and the helpers contracts are deployed on:
Here are the addresses on those networks:
Linea Sepolia
Linea Mainnet
Arbitrum Sepolia
Arbitrum Mainnet
Base Sepolia
Base Mainnet
BSC Testnet
BSC
To easily differentiate the networks on which an attestation has been made, we use network prefixes for the Attestation
ID. This prefix is defined in the contracts/script/utils.ts file.
0x00000x00000x00010x00010x00050x00050x00060x0006Deploying a new Verax instance requires four main steps to cover the four main parts of the stack. Even if these steps are independent, and must not be done right away, they should be done in order.
contracts folder)subgraph folder)sdk folder)explorer folder)$ claude mcp add linea-attestation-registry \
-- python -m otcore.mcp_server <graph>