What you need
- The subject file — the scanned document being tested.
- The CredaScan manifest JSON — the machine-readable record created when the original proof was generated.
Verify Record
Upload the document and matching CredaScan manifest. The verifier recomputes the document hash and compares it to the recorded hash.
Verification Resources
How independent verification works
CredaScan computes SHA-256 over the target file bytes and compares that result to the document hash stored in the CredaScan manifest. If the values match, the tested file is identical to the recorded version. If they do not match, the file differs from the recorded version or the wrong file/manifest pair was used.
Evidence Pack source of truth
The CredaScan manifest JSON is the primary proof container. A report is a human-readable summary. Independent verification should rely on the manifest and the subject file.
- document.hash_algorithm: SHA-256
- document.hash: recorded file hash
- created_at: record creation timestamp
- evidence_pack_fingerprint: manifest self-hash, if present
Legal / Court Exhibit Note
This explanatory technical note assists review. It is not legal advice and does not guarantee admissibility; legal assessment depends on applicable law and case-specific circumstances.
- Exhibit A — Subject File: the scanned digital file being tested.
- Exhibit B — CredaScan Manifest JSON: the machine-readable integrity record.
- Exhibit C — Verification Report: optional human-readable summary, not the primary cryptographic artifact.