Validity changes over time
Digital Identity decisions depend on current credential status. A credential accepted earlier may now be revoked or expired, so a historical proof result cannot replace the current decision to accept a presentation.
Registry status in the proof workflow
Vault’s test credentials are associated with signed registry evidence and current status. zkProof applies verification checks, while zkTransparency distinguishes historical results from current status. A saved receipt is not a fresh acceptance decision.
Native XRPL credentials are separate
Vault also exposes a separate native XRPL credential demonstration. Its issue, accept and delete actions concern ledger objects, rather than the signed registry used by the connected zkPrivacy proof workflow. Changing one does not automatically change the other.
Inspect both time frames
- Historical: which record or snapshot was referenced?
- Current: is the credential accepted now?
- Policy: what freshness and expiry checks apply?
- Evidence: what ledger transaction, if any, supports the record?
Deletion is not erasure
Revoking a credential or deleting a ledger object does not erase past transactions or recover shared copies. Production Digital Identity requires a clear status, retention and recovery design. The current tools remain an evaluation using test credentials.
Explore the connected identity workflow · XRPL network reference


