Proof & records
Verify an Original independently
Use the matching reader to inspect complete source evidence without granting access or executing a financial action.
Select the matching complete source
Use the original supported PNG/file or complete proof source. A screenshot, thumbnail, printed picture or transformed media export can omit the embedded material. Verification first admits the enclosing artifact, then parses/projects its carried subpayload. A payload hash or schema-valid JSON does not independently establish the enclosing identity, ownership, funding or custody.
- Keep exact bytes
Save the actual original using its supported export.
- Choose its reader
Use the public proof reader, Note receiver or Vault reader for that source family.
- Read the result and scope
Inspect accepted or refused evidence and which parts were actually opened.
- Preserve the original
A verification view does not replace the source for later independent inspection.
Public and local readers
- Open the public proof reader
- Open the standalone Vault reader
- Inspect published schemas and resources
The standalone Vault browser reader includes its complete reader, canonical artifact verification, native source admission and pinned issuer material. Save the matching kit for local use. It makes no network requests and grants no financial or access authority. Required verifier/resources and trust policy are part of independent inspection, not a replacement server approval.
Machine-readable Vault inspection
node public/vault-verifier/v1/verify.mjs /path/to/vault.public.png
node public/vault-verifier/v1/verify.mjs /path/to/vault.public-proof.json
node public/vault-verifier/v1/verify.mjs /path/to/vault.private.png| Exit | Meaning |
|---|---|
| 0 | The carried evidence verified within the reader’s stated scope. |
| 1 | The input/evidence was rejected. |
| 2 | Usage error or protected private contents requiring the original passkey. |
Protected and historical evidence
A protected private file can have a verified outer artifact while encrypted contents remain unopened. The reader explicitly distinguishes those states; it cannot claim to verify inaccessible contents. Public inspection omits keys, phrases and private source bytes. A valid historical proof does not independently establish present unspentness, current holder authority or a new account credit. Inspection is not consumption, transfer or deposit.
Investigate a refusal
Keep the original and exact error. Check source completeness, supported format/version, required resources, recipient/application scope and enclosing artifact admission. Do not repair a financial proof by editing its amount or stripping unknown namespaces. Schema files describe structure, not financial authority. For interoperability, publish the exact build/resources, evidence scope and refusal cases; use the conformance procedure for a full capability assessment.
Implementation sources
Inspect the exact path.
Source links retain revision 6c5d582. Read the documented operation and assessment scope alongside its code.