Two different questions
zkPrivacy proof verification checks a defined mathematical claim. XRPL validation confirms a transaction’s ledger inclusion and execution result. The Digital Identity journey presents these as separate checks, because neither result establishes the other.
The proof path
Vault generates a Groth16 proof for the test eligibility circuit in the holder’s browser. zkProof invokes application verification of the proof, public signals, signed registry context and request conditions. Acceptance remains scoped to that circuit and policy.
The ledger path
An explicit action can anchor a registry commitment on XRPL Testnet. zkTransparency lets the verifier inspect the receipt, network, validated status and transaction result. A returned hash alone does not confirm 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
zkBridge connects scoped requests and presentations within the identity journey. It does not transfer assets across chains or place a Groth16 verifier inside XRPL consensus. Proof verification runs in the application; commitment evidence is recorded on the ledger.
Explore the connected identity workflow · XRPL network reference


