Infrastructure
The stack, credentials first
Everything that runs Verana is open source: run the whole stack or any piece of it, in your own datacenter. The credential side comes first: the software that builds Verifiable Services and the wallets people hold credentials with. The network underneath follows.
01
Build services
What a builder runs to put a Verifiable Service online: one VS-Agent per service. It is the reference business wallet of the Verana stack, and the runtime behind every demo service in the Verana Playground.
Verana's Business Wallet - VS-Agent
VS-Agent is an open-source container that packs the complete stack of a Verifiable Service: it gives a hosted service a resolvable DID, manages its credentials and Linked Verifiable Presentations, resolves trust before every exchange, and runs the registry operations for you.
Holder, issuer, and verifier
One runtime plays all three roles under ecosystem accreditation: it holds its own credentials, issues to peers, and verifies presentations, with revocation support on every rail.
Dual transport
DIDComm (Issue Credential v2, Present Proof v2, vt-flow) and OpenID4VCI / OpenID4VP with SD-JWT VC, DCQL and Presentation Exchange, plus Token Status List revocation.
The right format for each credential
Public credentials as JSON-LD Linked VPs with on-chain digest anchoring; AnonCreds where presentations must stay unlinkable; SD-JWT VC for OpenID4VC interop.
Ecosystem-driven lifecycle
The vt-flow protocol turns on-chain ecosystem actions into wallet actions: onboarding triggers issuance, and a revoked participant means the credential is revoked, pushed to the holder, and cleaned up automatically. No polling.
Trust resolution built in
Every DIDComm connection and every OpenID4VP presentation is checked against the Verana registry before it is accepted: Proof-of-Trust on both transports, fail closed.
Any service shape
Chat services on Hologram, MCP servers, A2A agents, and plain HTTP APIs, all declared under one DID. Plugin architecture, Docker self-hosting, REST admin API and NestJS / JS clients.
02
Choose your personal wallet
The holder side: the app or browser a person uses to receive, hold, and present verifiable credentials. Each wallet below is integrated with Verana trust resolution: before accepting a credential or sharing a presentation, it checks the issuer or verifier against the public registry and shows the trust card.
This list is built live from the Playground's wallet registry; every wallet passed the demo-credential loop against the testnet.
03
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.
04
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.
05
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.
06
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.