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: 11f6da6f487337bc1b22b18e523ef20db90c02ff9c9ef35fc148d2372300bd14
File size: 126 bytes
Filename label: sample.json
Anchored at (UTC): 2026-05-02T01:11:21Z
Transaction: e118e08833a45265e441f9b58a31cc63410f4fd4fe862c165c3cabc32aee511b
On-chain commitment: 41505bfd3ddde3a0b517be69e1f1df62974e938e (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: 11f6da6f487337bc1b22b18e523ef20db90c02ff9c9ef35fc148d2372300bd14
SHA-256 of the file as uploaded. A single-byte change anywhere produces a different hash.
Content-canonical: a9b2765796f6bd32d811eff87738469368b3a95116f8e25465f61ba55d1d9754
Scheme: JSON (RFC 8785 canonical). Resilient to non-meaningful changes (resave, metadata churn, line-ending drift).
Per-section commitment: 9058b540fa8f865ab191571dc6dd7bba1f673fa8604587b80eef5f797f03c5ed
Scheme: per-top-level-key · 4 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/e118e08833a45265e441f9b58a31cc63410f4fd4fe862c165c3cabc32aee511b — 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 41505bfd3ddde3a0b517be69e1f1df62974e938e.
Re-canonicalize the included canonical.json from the .mbnt bundle (jq -cS . canonical.json), sha256 it, take the first 40 hex chars — must equal 41505bfd3ddde3a0b517be69e1f1df62974e938e.
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.