The hosted demo service
A standing service run by VS Agent, Verana-verified - its DID and live Proof-of-Trust, resolved against the testnet on page load.
organization-vs.main.demos.testnet.verana.network - DID document · Resolver API
The use case to test
- 1. Resolve the hosted service - see the Proof-of-Trust.
- 2. Receive a credential issued by the hosted service.
- 3. Present it back to the hosted service's verifier.
Run it with any integrated personal wallet: Inji Wallet · EUDI Wallet (reference) · Authbound Wallet · Paradym Wallet · Procivis One Wallet · BC Wallet · wwWallet · Hologram Messaging · Sphereon Wallet · swiyu Wallet · Altme Wallet · NL Wallet
Under the hood
See how this wallet is wired
Pattern A/B - the stack itself (or a vs-agent sidecar) owns the DID, DIDComm, Linked VPs and VPR operations.
ECS credentials are obtained via the vs-agent Admin API or out-of-band, then published as Linked VPs on the service's DID document. The reference automation lives in verana-demos's common/common.sh.
Registry links
- ECS Ecosystem:
did:webvh:QmcT...AM7T:ecs-trust-registry.testnet.verana.networkresolve - Network frontend
- Resolver API docs
This page follows the identical per-wallet template of the playground spec §5, generated from integrations/vs-agent/integration.yaml.