Technical guide · Updated 17 September 2026 · Digital identity on XRPL.
Two different questions
A zero-knowledge verifier checks a defined mathematical claim. An XRPL server reports whether a transaction was included in a validated ledger and its execution result. Neither outcome should be used as a substitute for the other.
The proof path
The Vault browser generates a Groth16 proof for the test eligibility circuit. zkProof checks the proof, public signals, signed registry context and request conditions. The result is scoped to this circuit and acceptance policy.
The ledger path
An explicit anchoring action can submit registry metadata to XRPL. Check the network, transaction hash, validated status and result. A hash returned before finality is not evidence of successful execution.
Read a combined result
- Proof validity: does the proof satisfy the intended relation?
- Issuer context: is the registry snapshot accepted?
- Current status: is the credential still active?
- Ledger evidence: was the relevant transaction validated successfully?
No cross-chain claim
The product name zkBridge refers to the scoped presentation hand-off. The current workflow does not transfer assets across chains, verify another chain’s consensus or place a Groth16 verifier inside XRPL consensus.
Read the complete reference architecture · XRPL network reference
Email support@dnaprotocol.org.