Infrastructure
The stack, module by module
Everything that runs Verana is open source: run the whole stack or any piece of it, in your own datacenter. The testnet instances below are live.
01
Run the network
The Verana L1 and its utilities. Validators are members of the Verana Council; anyone can run a non-validator node in their own datacenter.
Ledger
The Verana L1: trust registries, credential schemas, permissions, and trust deposits, on chain.
Faucet
Testnet VNA, dispensed by a conversational Hologram chatbot that is itself a Verifiable Service: it requests an AvatarID credential presentation to limit access to humans.
02
Serve the trust data
The permissionless read side: everything that only reads the ledger can be run by anyone.
Indexer
Tails the chain block by block, indexes all Verana ledger messages, and exposes them over HTTP APIs; feeds the resolver.
Resolver
The verification gate: resolves DIDs, dereferences the credentials presented as Linked VPs, and verifies accreditations per the Verifiable Trust spec. Exposes the trust-resolution REST API and a ToIP TRQP interface.
03
Discover and observe
Query, explore, and audit the network.
Trust Graph
The typed discovery graph built from verified trust results: find services and ecosystems by the credentials they hold.
MCP server
Operate Verana over MCP: the agent-native surface for the ledger, the indexer and resolver, and the Trust Graph.
Visualizer
Interactive frontend for exploring the trust layer: trust registries, versions, schemas, relationships as a network graph, and analytics computed from real on-chain state.
Explorer
Block explorer for the chain: blocks, transactions, validators.
04
Operate as an organization
The web UI to fully operate Verana as a corporation.
Frontend
Create and manage ecosystems, schemas, and accreditations; browse trust registries. Uses the ledger, the indexer and resolver, and the Trust Graph.
05
Build services
What a builder runs to put a Verifiable Service online: one VS-Agent per service.
VS-Agent
Container-based framework for building Verifiable Services: the service's cloud wallet. Supports DIDs, DIDComm, OpenID4VC and more (based on OpenWallet Foundation credo-ts). Executes ledger transactions (onboarding, issuing, verifying) and receives event notifications from the indexer and resolver. Accepts connections from VUAs and other VSs.