Links • Repo Organisation • Getting Started • Contributing • Contracts Addresses • Subgraphs Addresses • Linking Attestations • Off-chain Attestations • License

📚 Documentation
🔍 Subgraphs
🧱 Verax SDK
🌍 Verax Explorer (Coming soon)

.
├── contracts   # All smart contracts needed to run Verax
├── explorer    # Explorer frontend to discover the main objects
├── sdk         # An SDK to easily interact with the contracts and the subgraphs
├── snap        # A MetaMask Snap to leverage the attestions in transactions
├── subgraph    # The subgraph indexing all the data generated by the contracts
├── website     # Verax landing page and

• Node.js (>= 18)

pnpm i

Check the dedicated README for more details.

Check the dedicated README for more details.

Check the dedicated README for more details.

Check the dedicated README for more details.

Check the dedicated README for more details.

Check the dedicated README for more details.

Verax Attestation Registry is a community-lead 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:

• Linea Testnet
• Linea Mainnet
• Arbitrum Testnet
• Arbitrum Mainnet

Here are the addresses on those networks:

• Linea Testnet
• Linea Mainnet
• Arbitrum Goerli
• Arbitrum Mainnet

Verax Attestation Registry allows creating links ("relationships") between attestations.
🔗 Go to the official documentation for more details

Verax offers 2 Schemas to cover most use cases:

• The Relationship Schema, with ID 0x41b8c81288eebbf173b2f54b9fb2f1d37f2caca51ef39e8f99299b53c2599a3a
• The Named Graph Relationship Schema with ID 0x8f83a0ef7871f63455a506f6bca0db98a88721764ae6dbde2afddd8e12e442b8

To handle large payloads to attest and avoid increasing the gas cost for the attestation process, it is possible to host the attested payload off-chain. In this case, the on-chain attestation will only contain a link to the attested payload, based on a dedicated Schema called Offchain. It is available with ID 0xa288e257097a4bed4166c002cb6911713edacc88e30b6cb2b0104df9c365327d.

To use it, simply pass a payload with the following content:

{
  "schemaId": "0x41b8c81288eebbf173b2f54b9fb2f1d37f2caca51ef39e8f99299b53c2599a3b",
  "uri": "https://example.com/payload/123"
}

• schemaId: the ID of the Schema encoding the complete (off-chain) payload
• uri: the link to the complete (off-chain) payload

MIT