Issuer–Holder–Verifier
Issuance, user-controlled storage and verification by a relying party.
// Topic hub · Identity wallets
The technical lifecycle of digital identity wallets: issuer, holder and verifier roles, QR pairing, verifiable credentials and production security.
// Core concepts
Issuance, user-controlled storage and verification by a relying party.
Proving only the required attribute without disclosing the full identity.
Binding credential use to a trusted device key and user authentication.
// Guided reading path
Follow the articles in this order to build the concepts progressively.
// All publications
A screen-by-screen guide to Registra: reading verified data from an ID card or passport chip, applying web-managed templates, creating PDFs on-device, and approving web sign-in with biometrics.
Yes. It can present a signed proof of the minimum attribute required for a transaction instead of exposing a persistent identifier.
Limited offline verification is possible with an appropriate trust root, validity window, revocation strategy and device binding.
Assessing the demo through 22 tests, live SoftHSM validation, institution isolation and durable template records, with remaining hardware HSM and standards work clearly identified.
Two QR codes, institution-and-session-bound pairing, Secure Enclave signatures, pinned template revisions and SoftHSM-signed disclosure results, step by step.
The updated prototype architecture: HTTPS portal, native iPhone wallet, isolated SoftHSM/ES256 service, institution sessions and SQLite-backed versioned request templates.
Eight implemented demo journeys and custom institution onboarding, covering field requests, template approvals, QR consent and SoftHSM-signed results.
Issuer–wallet–verifier design, separating implemented SoftHSM signing, institution registration, field grants and versioned templates from the remaining production goals.
Why digital identity wallets matter for data minimization, with working synthetic-demo examples covering SoftHSM, institution permissions and dynamic request templates.
We’ll walk through the Loyalty Credential, digital wallet, personalized offer selection, and Order Credential workflows in the DemoAir app step by step, using code examples.
We examine JWT generation, the MongoDB wallet, and the claim presentation flow in the FastAPI prototype; we explain the requirements for an asymmetric signature, holder binding, selective disclosure, replay protection, and credential status for a true Verifiable Credential architecture.