Technical guide · Updated 17 September 2026 · Digital identity on XRPL.
Start with the request
A verifier should state the claim it needs and the context in which it will accept it. In the connected evaluation, zkBridge prepares a request for the Vault holder to complete. It is a presentation workflow, not an asset bridge.
Bind the context
The request includes an audience, challenge and expiry. These values distinguish the intended presentation from an arbitrary proof file. They do not replace a person’s understanding of what is shared or a lawful basis for processing real data.
What stays private
The holder secret and other witness values are used during browser-side proof generation. They are not included in the proof package. Public signals and registry context still disclose information, and must be considered in the privacy model.
Before presenting
- Review the policy and intended audience
- Check the request validity window
- Use only test attributes in the current tools
- Treat continuation links as access capabilities
Limits of a successful check
A successful proof does not establish informed consent, legal identity or a right to retain a document. Technical presentation checks and the surrounding human and organisational process must be evaluated separately.
Read the complete reference architecture · XRPL network reference
Email support@dnaprotocol.org.