Skip to main content

Overview of Governance

Verax governance exists to coordinate a shared protocol that spans contracts, subgraph, SDK, explorer, documentation, and deployments across several networks.

Why governance matters here​

Unlike a single-application stack, Verax has shared protocol surfaces:

  • common registries;
  • canonical schemas;
  • public infrastructure;
  • deployment operations;
  • mainnet allowlist policy.

Those shared surfaces create decisions that are broader than one team or one app.

Governance and product docs​

For most developers, governance is background context. The primary documentation paths remain:

  • Build with Verax
  • Research Verax

Governance becomes important when you need to:

  • understand mainnet issuer onboarding;
  • propose a protocol or operational change;
  • reason about who maintains shared deployments.

Live source of truth​

Because governance changes faster than static documentation, the community forum should be treated as the live source of truth for active proposals and current process details.