Drop a receipt. See the proof.
Verification recomputes every signature and hash — PASS means every change was signed by the exact registered identity and nothing was altered after the fact.
The offline verifier — how to check a receipt today
Export a receipt from any session, then run the zero-dependency script — about seventy lines of plain Node, no packages, no network. It recomputes the hash chain and every Ed25519 signature. Exit 0 means PASS. If a single byte was changed after signing, the exact check that broke is named.
PASS · 12 events · chain intact · signatures valid
Verified. Every change was signed by the exact agent identity Token Holder registered, and nothing was altered after the fact.
This receipt was altered after signing — the failed check is named. Do not trust these changes.
Drag a receipt here — runs in your browser, nothing leaves this tab.
The hosted in-browser verifier is on the roadmap. Until it ships, the offline script above is the way to verify — same math, same verdict.
Tamper-evident, trusted-operator forensics: alterations are detectable and provable — the receipt is not “unalterable.” Verification needs no vendor server in the loop, so the proof does not depend on trusting us.