01
The holder carries proof
The credential is a signed object in the holder’s wallet, not a row a verifier queries from an issuer. A citizen can present it without asking permission or exposing where it is used.
Sovereign Infrastructure · Identity
Proof that travels.
A credential lives with the holder and can be verified without calling the issuer. Proof, issuer status and revocation stay available through a trust registry—removing the outage, tracking and dependency created by a central verification service.
System map. An issuer issues a credential into a holder's wallet and the holder presents it to a verifier. The issuer publishes proofs and revocation status to a trust registry, and the verifier checks signature and status against that registry. A severed trace between verifier and issuer marks the call back to the issuer that never happens.
How it works
Three parties, one registry, no phone call.
03 / 05PresentThe holder presents the credential to a verifier, online or off.
A credential is worth what it can prove when the issuer is unreachable.
02
Status is published
Revocation is distributed as a cacheable status list. Verifiers read the registry, so an issuer outage cannot block proof and no central service builds a usage log.
03
Migration runs in parallel
Old and new systems write together while verification runs in shadow mode. Cutover follows a zero-mismatch window, not a calendar date.
Technical specification
- Identifier
- Decentralised identifier, resolvable from the registry
- Credential
- W3C Verifiable Credential, signed once by the issuer
- Verification
- Offline-capable, checked against published proofs
- Revocation
- Published status list, cacheable by verifiers
- Trust list
- Trusted issuers on-ledger, versioned and auditable
- Delegation
- Explicit, scoped, and revocable on the same registry
- On-ledger
- Identifiers, proofs and status only
- Off-ledger
- Every attribute and document behind the credential