Skip to article content
Close

Fresh Requests and Replay Protection

CONSENSUS / TECHNICAL GUIDE

A zkPrivacy presentation must match the intended request, audience and time.

DNA Protocol1 min readDigital Identity and zkPrivacy

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

A valid proof can be stale

A mathematically valid proof can still be unsuitable for a new Digital Identity request. The zkPrivacy workflow also checks the intended audience, challenge, expiry and replay state required by its acceptance policy.

Challenge-bound presentations

In the test circuit, a nullifier is derived from the holder secret, nonce and audience. zkBridge binds the request; zkProof’s application checks replay state alongside cryptographic validity. A nullifier is not a universal identity or a guarantee of anonymity.

Keep state and time explicit

A request can expire while Vault generates its proof in the browser. A missing request record or unavailable status check must not silently become an acceptance. Re-evaluate the current request rather than reusing a previously displayed success.

Useful negative tests

  • Present a proof for a different audience
  • Retry an already-consumed request
  • Complete a request after its expiry
  • Check behaviour when the required registry or replay state is unavailable

Ledger history is not replay protection

An optional XRPL Testnet commitment can remain inspectable after a request expires. That historical record does not make a fresh presentation acceptable. zkTransparency shows ledger evidence separately from current request and credential status.

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.