Web-page notarized
A tamper-evident timestamp of a page's content. Verify any proof — bsv.cx
Rendered page — archived HTML, sandboxed · click to collapse
Html-only render: no scripts or original assets, so it may look unstyled. Not the live page; not endorsed by bsv.cx. ⤢ full screen
WhatsOnChain · Banana Blocks
SPV proof & how to re-verify it yourself
7282750cd055fb0250f1ed935b467b37754aa811b25536fd33d69fbf9010743a
4b72fc8fffc04bce133b25d83cb38d4f8962e48d35d706af999d79ff63bd1a1b
a76a75cf63f0ab74feb7af7597696891576360a8346c15820daf49169bb99166
1b22c1b772e2e62f621c492faf9c0e3bbf9250322010c97855ca7e091af26274
99f425c2e5a3cb8da1d8cbaa6987b03d5adf7aceb6d84995c7bfbd112d570fbc
5dafc811fee5654b671b0392d7e9b8deba003087bac371db7761ede9f7cfca7e
d1e64bad5bb3d4930130348afa41ff315c8e917f6026c17c525e505db514220e
f5344038e70d999b897c3831ff7054303f0e42383b7d86bd75449070803df3d7
7f8ba7b85ee48038ea0d5680e57ce24de01720186144c1a2bc193074939ab522
754a68b785dc92ee11cb9b27192192e66580ab80bda38fe47e0258f803f51977
0a8cff1a3d50979fe2711e220ddff3bef367813d78603af6fd31f0adcb0924f2Trust no one: double-SHA256 the txid up this branch — at each level your hash goes
left when index is even, right when odd, halving the index each step —
to get the block Merkle root, then confirm that root is the header at height 965503 on
any block-header source you trust. We verified it against headers we run ourselves; you
verify against yours — no explorer, and no bsv.cx, in the trust path.
Prefer to check it against a second independent source? Paste these fields into
our public verifier (POST /spv/verify) — it folds the root itself and
checks it against headers we sync, so it can only ever make a bad proof fail.
Or take it to your own tools in the ecosystem standard format:
BEEF (BRC-62, tx + proof) ·
BUMP (BRC-74, path only). Any @bsv/sdk client verifies
these with no bsv.cx-specific code — Transaction.fromHexBEEF(hex).
Save both. The manifest's SHA-256 is the anchored id, and it binds the HTML hash — so from your saved files you can recompute every hash and match the transaction's OP_RETURN yourself, with no dependence on bsv.cx ever being online.
Verify it yourself: the manifest is the exact JSON whose
SHA-256 is 045592b12b373e4763aae745551e3cc3776764607a8b4cb4a50c0669af78d59f; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 045592b12b373e4763aae745551e3cc3776764607a8b4cb4a50c0669af78d59f, and the block's
timestamp proves the page looked this way at or before that time.