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
03812f1df113e6518909800c7f51c866a740cd1f1bc54b6233eaf285ef454fd5
864c1600c2648e731ed088c9a5aa9670785b03174e9f5f127356114ee20a4e56
e6130837f63a05321af2f73973d20cfdadf45c22d0088a93095e743ca64b7a4a
cb347d28f073e47971a485fede4aaa05051056934a0fcbc0a3f353d568bcac2f
05732ab68de2ad147ec296765ae60864ef140bd227fbb19ed0a14572980ea60c
b3f7c563b6429e7ef87c8458866a074f82ce2bbb77ca034fcac342535c16bc5b
57fc8e8c4c71efc42fde87cb69667ce273d8b25b97820d43db86c94733ca31a6
51835bb3818f67abd7a669b1e9e49ac53272e3a427ebce93b8d1a317d3d22deb
c29f13958b0629b9d686e9b219a2ab302e0b2bf2c4fde5e69df24f32a1db61b2
5c1315e903a757c4c273293058e319d739019ee5705cc9c80267b3f89cd151e2
dcab743d996004e37ad55b53e010b3c19cbffb81adc71d6768664cb1f88e72a2
0694bbea56c93b5c9d15f2ac77ec3445a0bdb1c8f59d72d8aac7fa424102e763
66b7ea9c9ee15d568d20c08497425ba3f031cdfe4fc85c5223aec70b958de8ee
4d62e7f1dd5c63ee8e86efd8fcb9cf9d8f5b346da9024ac05cbb1db08f2d90ea
d2fa148b6290b8066802f55336636b2724e7c06372f23e621735b1c3522d0f00
8b743cffcbeaaf1760abd82927f2543d6b442700913cde4dde253163a657828c
f6007bbe142e1584528ac012087990f57e4aae885a366a19f35cc98417f777d3
ddc104786674959617e5ecdee3ff3bcce5c52f142e7c10ef950de9c59b08bda4
bc2157036787b50f69abb48db7411aa2db92ae2bb54f9cf9dc97523b7b4aef08
645417fa7c7a06d9b380277732f717bab358f2407f275e094690b098bbf2006aTrust 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 964942 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 0ba292f8ae4a53b25c4ed650c04ee474b9e18d941d5dedf8777276eea38ee77d; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 0ba292f8ae4a53b25c4ed650c04ee474b9e18d941d5dedf8777276eea38ee77d, and the block's
timestamp proves the page looked this way at or before that time.