Receipt verifier

Verify a Pipelock Receipt

Check your own receipt chain locally. Paste it or drop a file, add the operator public key when you have it, and read the exact trust result.

Nothing is uploaded. The verifier runs in this browser.

Local input

Add the chain and public key

Use a JSONL receipt chain from any Pipelock deployment, or drop a PipeLab-published session bundle. Files stay on this device.

Receipt data

Receipt chain

Drop a chain or published bundle here JSONL chains and gzip-tar bundles up to 25 MB Choose a file

No file selected. You can paste a JSONL chain below.

Loads PipeLab's published sample into this page.
pipelock verify-receipt WASM ยท browser-local
Run verifier
25 MB input limit
Ready. Add a JSONL receipt chain, or a PipeLab-published session bundle. Nothing leaves this browser.

If the browser verifier cannot load, run pipelock verify-receipt --key <key> <file> locally. Get the standalone verifier instructions.

Scope

What the result means

With a pinned public key

A passing chain verifies signatures, record integrity, and record order for the records you supplied against that key.

Without a pinned public key

A passing chain proves internal consistency only. It cannot establish that the embedded signer key belongs to the operator you meant to trust.

What neither result proves

Verification does not prove the supplied records are complete, that every action crossed the mediation boundary, or that the operator was honest.