Web-page notarized
A tamper-evident timestamp of a page's content. bsv.cx — verify any Bitcoin proof, trusting no one
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
3ab9317200daed70daeea91901d7a6896aa14a27c18e1e45338592810931392e
cb6895a4e8f2e89b0ce9c596bf9bd73ea91c175f759d01ab607b632d8b90deea
5f5824a785d6f1c4d491b69b966678afaa402c4adee5e478e60eac0796813abe
02a119f6a48454c7863a8ce9c058b82e1bbf2683bf90f397c0dde156c5cceefe
bc4a8792cb3d27921a5a952ba1b237fb66b444f5aa0d58637a36a725010a5b1c
ce61832c4dcc2aa5eea6b26697274815695a5dd1c77cb35737304ec40a6e0eb3
f202f323cc0c16186ba742a4cdbcfa7f28afe555b50c9ccee5610c4f93153f98
09002e128e21de12f7a1a9771460c32cd9f1b41c62e9fa13165176c6c0be1253
1db670f489d134f1d4e65b77f7de27cba31955c7d416e00fd9a8825a607cbbe4
33f13d6b504c0e1888c14a652561c25fbccab431aaa86332d12d75ba6e631b08
32ee05cc3299f3ec91c36377bdab7acf150fbe74a37d3a9724c04f9e23cca03d
1cf8eb340dadfd3b9cac1ae1e1fe061eb73a5cb1a104a428c88cec116a3c27db
2505ec439f2fdfe348ea20d7c6cc2d8f50e326f323d14aaeef819a7f3add585b
f1f5699d66d0b9062b9908db85a817436d12fef5f39936b800c25178e9e3de05
0c476a5091d40edcded245251e4f858ed358ff5af5bf01eb37007c7b958f2f4c
3e8df9f1fa7fa2516b2940ea112769426bcfb544134c178d5214efc458161925
a994ba46d5eb2f5619fd45883e597a5868fa55bf7ee9f6d3dadcbbbe86485709Trust 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 965343 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 f6179723874ff66a76841ec29b71b5bc2871ec3450d7906320459e55bde517ba; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / f6179723874ff66a76841ec29b71b5bc2871ec3450d7906320459e55bde517ba, and the block's
timestamp proves the page looked this way at or before that time.