Verax

• Name: Verax Attestation Registry
• URL: https://docs.ver.ax/
• Category: attestation registry / linked-data reputation infrastructure / schema-and-portal trust-routing layer
• Tags: ethereum-ecosystem
• Summary: Verax is a linked-data attestation rail, not just another claim log. The useful twist is reusable schemas, shared vocabularies, relationship attestations, and portal routing. Strong note. The leverage still sits with schema authors, vocabulary choices, and whichever readers surface the graph.
• What it does:
  • Provides a shared public registry on EVM chains for attestations of public interest
  • Encourages a single deployment per network so multiple dApps can publish into the same discovery and composition layer
  • Lets anyone create reusable schemas whose IDs are derived from the schema content, promoting counterfactual creation and schema reuse
  • Adds schema metadata such as context so attestation fields can map onto shared vocabularies and linked-data conventions
  • Supports relationship attestations and schema-extension patterns so attestations can be linked into richer semantic graphs rather than remaining isolated records
  • Ships a broader operating stack around the registry, including explorer, SDK, subgraphs, governance NFTs, and module / portal concepts surfaced in the docs and repository
• Key claims:
  • Verax wants to be shared infrastructure, not one app’s database. The docs explicitly frame it as a common public registry and recommend a single deployment per network.
  • This is not only a contract set. Explorer, SDK, subgraph, governance modules, and portal routing are part of the intended operating stack.
  • Schema identity is meant to be public and reusable. IDs derive from schema content rather than from one app’s local registry.
  • context metadata is the real differentiator. Verax pushes shared vocabularies and semantic interoperability deeper into the rail than simpler attestation systems usually do.
  • Relationship attestations matter because they let the graph express links between claims instead of just storing flat records.
  • The broader repo and governance surface shows the same ambition: Verax is trying to route contribution records, discovery, and interpretation through one shared attestation substrate.
• Whitepaper: No canonical standalone Verax whitepaper surfaced in this pass. The clearest current primary materials were the official docs pages and the main repository README; see ../whitepapers/verax-primary-sources-2026-05-08.md.
• Sources:
  • https://docs.ver.ax/
  • https://docs.ver.ax/verax-documentation/core-concepts/ecosystem
  • https://docs.ver.ax/verax-documentation/core-concepts/schemas
  • https://docs.ver.ax/verax-documentation/core-concepts/linked-data
  • https://docs.ver.ax/verax-documentation/get-involved/governance/overview-of-governance
  • https://raw.githubusercontent.com/Consensys/linea-attestation-registry/main/README.md

Internal linkages

• Strongest attestation-rail comparisons: ethereum-attestation-service and sign-protocol
• For document-native trust packaging rather than a linked-data registry, compare openattestation

Control surface

• Control sits with schema authorship, context vocabulary choices, relationship modeling, portal defaults, and whichever indexers or apps decide the graph counts.

• That is why Verax matters. It is not just storing claims; it is trying to standardize how claims relate and how downstream readers interpret them.

• Last reviewed: 2026-06-17 UTC