Web-page notarized
A tamper-evident timestamp of a page's content. Pay-per-call — 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
f1d4a1b4e8895a2a830b2da74090af29db80e65a0c81c1de89afcf91bf0682c4
573ec741fde6a662304f3b7de6bd31525d2d84f6e24fc198db030b72f58c6e1a
8f9277304fe8d12211eaf74b256b0bc59d7864cdd56c2d3033ae16c02d3c3f6e
0afcecbf9d578c660c2263f6b63e3e2f2f2d3e64acb1c1da1c1b16334def31ae
c9b5f5b567d38013a3bc57ee90d17f01cb9ae9edd92919efbf024513702da872
adb9854d0db3b5c71229f23820852c1f242abfb5d87adddeadaa081a8f49eb51
e118d575c993cba2422e550624ff0a7c5f72f5df3efe2f51dd38de08530b08e5
f299ac4c7c0ae90b0126f8fd67bafcd71839bb3b1f7a7c0151208a16d8467fc7
550ab13683117869978f96acf5fd34d691bb262a023f031510920a084e296a01
db3a2587722358ae5a24ead6f56978cc8c02cb2ac17a49a6aa628c2e1c3e89d7
b2b5031f7ea99ff28b71110f7b9085d1f4c1427e081f3945a92aa33e39e10204
bb072221ce8e418b95e3e89e3eedaa1433bbfe86e3bb475624e233ca4a59799eTrust 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 968095 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 ad75f1b5592a65993dada28cc528d265ff63b76d271a83424b130c280bf2f6b7; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / ad75f1b5592a65993dada28cc528d265ff63b76d271a83424b130c280bf2f6b7, and the block's
timestamp proves the page looked this way at or before that time.