Evidence Anchoring & Inspection
Inspect ledger evidence without confusing it with identity assurance.
What you can evaluate
Follow an explicit action that anchors registry evidence on XRPL. Inspect the returned receipt and check its validated result. This is an evaluation workflow, not a high-volume genomic hashing API.
- Registry references associated with a test credential workflow
- Public XRPL transaction fields and submitted metadata
- Separate proof, signature and ledger outcomes
From request to receipt
Create a test credential in Vault, complete the scoped proof flow, then choose the available anchoring action. Opening a page or generating a proof does not submit a transaction automatically.
- Confirm the XRPL network and environment shown in the tool
- Submit only the metadata described by the tool
- Wait for validation and inspect the result, not only the hash
What an anchor establishes
An anchor can make evidence of a particular commitment or registry state inspectable in ledger history. It does not prove who a person is, that an issuer is authoritative, or that a document’s contents are true.
Data boundaries
Do not submit personal documents, DNA sequences, wallet seeds or private keys. Even a hash can expose information when its source is guessable or linked to other public records.
Explore the workflow
Use zkTransparency for evidence inspection and the interactive whitepaper for the current architecture. No throughput, uptime or clinical service is promised by this page.