Skip to article content
Close

Issuer Trust Comes Before the Proof

CONSENSUS / TECHNICAL GUIDE

Digital Identity starts with issuer trust, even when a zero-knowledge proof verifies.

DNA Protocol1 min readDigital Identity and zkPrivacy

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

A key is not an authority

Digital Identity depends on an issuer a verifier is prepared to trust. A signature binds a registry snapshot to a signing key; it does not establish that the key belongs to a trusted identity provider. Issuer acceptance remains an explicit policy decision.

How the lab models issuance

The Vault workflow uses test credentials, a holder commitment and a signed registry. An Ed25519 signature authenticates the registry root and context outside the Groth16 circuit. This shared evaluation issuer does not provide real-world identity assurance.

What the proof contributes

The zkPrivacy proof checks registry membership and a bounded eligibility claim for its public inputs. It does not establish that the issuer verified a real person or that a credential represents a verified identity.

An acceptance checklist

  • Identify the expected issuer and verification key
  • Check the signed registry snapshot and its context
  • Verify the proof against the intended public inputs
  • Apply current status, expiry and request checks

Readiness beyond the demonstration

Production Digital Identity requires accountable issuers, reviewed key custody, recovery and a trustworthy enrolment process. Optional XRPL Testnet commitments provide inspectable evidence; they do not supply those institutional assurances.

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.