Proof Receipt

BSV mainnetStandard proofAnchored on chain

Standard receipt — file never left your device. Your file was NOT uploaded. Only its SHA-256 hash, file size, and any label you typed were transmitted.

File SHA-256: 5fc164427b457aa4d4626fcc2ffb818ca655bab69980f90695837a46bf0365b2
File size: 398 bytes
Filename label: sample.zip
Anchored at (UTC): 2026-05-02T00:27:11Z
Transaction: 45ffaede5bc6c49821c51addeba381cfb7b08f3566ad2668e540331bbbbba1a0
On-chain commitment: e7000b56d06e1398d622071a6d3ff8f625a793a8 (sha256 of canonical receipt doc, first 20 bytes)

What this receipt proves — and what it does not.
A valid receipt proves the file existed in this exact form at the time of the on-chain transaction. It does not prove:

that the underlying event the file describes actually happened;
who produced the file, who saw it, or who signed it;
what the file means or whether its claims are true.

Proofs anchored

Three orthogonal proofs about your file are committed in a single on-chain anchor. Use whichever the situation calls for.

Byte-exact: 5fc164427b457aa4d4626fcc2ffb818ca655bab69980f90695837a46bf0365b2
SHA-256 of the file as uploaded. A single-byte change anywhere produces a different hash.
Content-canonical: d9b5d69b9c7cd73a78715de1e38df18dc565814b5ea2f98ea8fd6c91b76cddfb
Scheme: ZIP entry manifest. Resilient to non-meaningful changes (resave, metadata churn, line-ending drift).
Per-section commitment: 5404a4bcf60683b9533a3a2261724fc9b96338b21ff8d8271cb2e2b0b7d1812b
Scheme: per-zip-entry · 3 leaves. Lets a holder later prove a single chunk was part of this file without revealing the rest.

Includes the bundle, a printable PDF receipt, and a verify guide. Keep alongside the original file.

Other download options

Bundle only (.mbnt)

Create another proof →

How to verify this receipt yourself (manual recipe)

In one sentence: re-fetch the transaction from any BSV block explorer, recompute the canonical receipt's hash, and check that your file's SHA-256 matches the one inside — if all three match, the receipt is intact and the original file is the one anchored. The verifier at /verify does this for you in your browser in one click.

For an audit trail or scripting, here are the manual steps anyone can run with jq + sha256sum:

Re-fetch the on-chain transaction: https://whatsonchain.com/tx/45ffaede5bc6c49821c51addeba381cfb7b08f3566ad2668e540331bbbbba1a0 — confirm an OP_RETURN output starting with the bytes MBNT.
Decode the OP_RETURN payload: bytes 6–25 are the document_hash (sha256 of the canonical receipt doc, truncated to 20 bytes). It must match e7000b56d06e1398d622071a6d3ff8f625a793a8.
Re-canonicalize the included canonical.json from the .mbnt bundle (jq -cS . canonical.json), sha256 it, take the first 40 hex chars — must equal e7000b56d06e1398d622071a6d3ff8f625a793a8.
Sha256 the original file — must equal the File SHA-256 above. The bundle does not contain the bytes; you kept them.

What we kept: this bundle (downloadable above) and one access-log line for this request. What we did NOT keep: the original file — the bytes never reached us. The on-chain anchor is permanent.