Technical guide · Updated 17 September 2026 · Digital identity on XRPL.
Validity changes over time
A credential that was accepted earlier may now be revoked or expired. Verification should distinguish the history of an issued record from the current decision to accept a presentation.
Registry status in the proof workflow
The test pipeline associates credentials with registry evidence and current status. A verifier must apply the intended registry and status policy, not accept a stale screenshot or receipt as a fresh proof.
Native XRPL credentials are separate
The Vault also includes a native XRPL credential demonstration. Its issue, accept and delete actions concern ledger objects. They are distinct from the custom signed registry and Groth16 presentation workflow; changing one must not be described as automatically changing 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 copies already shared. A production system needs a clear status, retention and recovery design. This lab does not implement inheritance or transfer of biological ownership.
Read the complete reference architecture · XRPL network reference
Email support@dnaprotocol.org.