A fingerprint has a limited meaning
In Digital Identity, a hash can help detect changes to a referenced record. It does not establish the issuer’s authority or the truth of the underlying claim. A commitment’s meaning depends on its construction, the signed registry context and the checks applied.
Public does not mean harmless
zkPrivacy treats disclosure as a design boundary. Accounts, submitted metadata and transaction relationships can be visible on a ledger. A hash of a guessable input may leak information, while encryption can still expose timing, size and relationships.
What the evaluation publishes
The connected workflow optionally anchors a registry commitment on XRPL Testnet. Vault keeps the holder secret in browser memory; zkTransparency exposes the receipt for inspection. Check the actual transaction metadata rather than inferring privacy from an opaque hash.
Evaluate the boundary
- Use test samples, not personal or genomic data
- Separate a signature check from a content-integrity check
- Inspect metadata and access-link exposure
- Record which network and snapshot each result refers to
Genomics requires its own design
Genomics remains a future application area for Digital Identity and zkPrivacy. It would require validated scientific claims, suitable issuers and a reviewed disclosure model. The current test workflow does not process real DNA or validate clinical results.
Explore the connected identity workflow · XRPL network reference


