Verification result
Start with Verify sample chain. You should see five signed records pass verification.
See what a signed receipt can prove.
Check a sample, then see what happens when a receipt is changed. No account, installation, or payment. Your pasted data stays in this browser.
These buttons load public example records, not a live transaction. They replace the JSON below. The tampered sample changes one receipt field without signing it again.
Inspect the sample or verify your own JSON
Paste one signed artifact, an array of artifacts, or an object with an artifacts array. Include the full chain to check the agreement and receipt together.
Use it with your agent
The sample shows that a changed record fails verification. The hosted demo is temporarily unavailable while its origin is moved. To create a fresh result with your own service, prepare a local setup.
What this page can and cannot prove.
01 · checked locally
Signatures and chain links
This page verifies BIP340/Schnorr signatures, canonical hashes, artifact rules, and links between supplied records. The Rust verifier runs as WebAssembly. Missing or duplicate chain members are reported explicitly. A valid signature alone is not a complete chain.
02 · limits
Evidence is not a guarantee of truth
Signatures identify keys. They do not prove a human or organization authorized the action, that an output is correct, or that a payment settled externally. Historical verification does not check expiration against today's clock. This sample is a conformance fixture, not a live customer transaction.