Log InSign Up
Junctiq / Evidence verification

Inspect the proof.

Compare an exported evidence pack with a receipt you obtained independently. Check the manifest, timestamp signatures and log inclusion—and see what the evidence cannot yet establish.

01 / Choose your evidence

The receipt must contain the pack ID, organisation ID and manifest SHA-256 from a separately trusted source. A digest copied from the bundle cannot establish its authenticity.

The selected JSON is sent to Junctiq for this check. This verifier does not store the files or fetch their source URLs. For a check on your own machine, use the offline verifier below.

02 / Verification record

No evidence checked yet

Choose both files to begin. Missing evidence will remain visible; it will not be treated as a pass.

What this check means

Valid proofs can establish consistency with the supplied receipt. They do not authenticate who supplied it, prove publication of a log checkpoint, establish a publisher’s publication time, or decide whether a claim is true.

The product requires two independent timestamp authorities. One verified authority is not that proof. Original artifact bytes are not checked by this upload flow.

Verify on your own machine

From a Junctiq checkout, run the credential-free verifier with the same two files:

npx tsx scripts/ops/verify-pack.ts bundle.json receipt.json

Exit 1 means invalid evidence. Exit 2 means checked but incomplete. No Junctiq account or database connection is needed.

Inspect artifacts in the Vault →