How the lab models issuance
The Vault workflow uses test credentials, a holder commitment and a signed registry. An Ed25519 signature authenticates the registry root and context outside the Groth16 circuit. This shared evaluation issuer does not provide real-world identity assurance.
What the proof contributes
The zkPrivacy proof checks registry membership and a bounded eligibility claim for its public inputs. It does not establish that the issuer verified a real person or that a credential represents a verified identity.
An acceptance checklist
- Identify the expected issuer and verification key
- Check the signed registry snapshot and its context
- Verify the proof against the intended public inputs
- Apply current status, expiry and request checks
Readiness beyond the demonstration
Production Digital Identity requires accountable issuers, reviewed key custody, recovery and a trustworthy enrolment process. Optional XRPL Testnet commitments provide inspectable evidence; they do not supply those institutional assurances.
Explore the connected identity workflow · XRPL network reference


