Identity Workflow Integration
Connect the roles. Keep the trust boundaries visible.
Current infrastructure only
DNA Protocol’s reference workflow connects Vault, zkBridge, zkProof, an optional XRPL anchoring action and zkTransparency. It is not a separate production blockchain or a genomic consensus network.
The connected path
Each stage carries a defined piece of context rather than passing an entire private identity record between products.
- Vault creates and holds a test credential
- zkBridge scopes the presentation request
- zkProof checks the proof and registry context
- XRPL records explicitly submitted metadata
- zkTransparency inspects the receipt and current status
Separate application and ledger checks
Request expiry, replay handling, issuer trust and proof verification belong to the application’s acceptance policy. XRPL consensus validates ledger transactions; it does not run the lab’s Groth16 verifier.
Integration readiness
Before using real identity data, define the operator, issuer policy, custody, recovery, privacy model and failure handling. The current formats are not presented as certified W3C credentials or a complete production wallet protocol.
Start with evidence
Evaluate successful and rejected requests, revocation, expired credentials and ledger failures. The interactive whitepaper documents the reference architecture and its known boundaries.