Skip to article content
Close

Scoped Requests and Meaningful Disclosure

CONSENSUS / TECHNICAL GUIDE

zkPrivacy starts with a precise request and a holder-approved presentation.

DNA Protocol1 min readDigital Identity and zkPrivacy

Technical guide · Updated 15 November 2026 · Digital Identity and zkPrivacy.

Start with the request

zkPrivacy starts with the claim a verifier needs and the context for accepting it. In the connected identity journey, zkBridge creates a scoped request and the holder approves its presentation in Vault. The workflow exchanges proofs rather than assets.

Bind the context

The evaluation request binds a defined audience, challenge, policy and expiry. These values distinguish the intended presentation from an arbitrary proof file. Holder approval supports the workflow; it does not by itself establish informed consent for processing real data.

What stays private

Vault uses the holder secret and other private inputs to generate the proof in the browser. Those inputs are excluded from the public presentation. Public signals and registry context still disclose information, so zkPrivacy requires a clear disclosure boundary.

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 confirms the defined claim under its acceptance policy. The current tools use test credentials and do not establish real-world identity. Issuer trust, informed consent and the surrounding organisational process require separate evaluation.

Explore the connected identity workflow · XRPL network reference

← All Consensus guidesBack to top ↑
get in touch

Questions about Digital Identity or zkPrivacy?

Email support@dnaprotocol.org.

Social network

@DnaOnChain

Get in Touch

Send your enquiry directly by email.

support@dnaprotocol.org

Email DNA Protocol

Opens your email app. Review and send your message there.