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
67f384c0c8bafb0703c765385db04f870e9b613f33f3916d045501337ccfb27b
b3831d419f184dcc891a86fd0c58214d1702ee509e873a6f406a8bf4e04cf8d5
ffaafa107dc6a67da791fa0b0ad5891da91985c73af98cc974b96a8abf4cddc7
c4fcf6c4c42284db67ef01be4f8eeefff5094f14eff51fe536718586bb30867f
19a094b59ef8bd4ee89bf283682ce64a4af098a2a713b5c94102fcbfab54e51a
169f838020da01e66f1927616d38d5ccc75dcfcbff285ed4be1c599f9e72af18
e93f53b7b3cb1a60f263524bfba440a88af3f1365906ec98ceb1a0de413d3d0d
491c6c13c5c8b936386560df251e79f4b12ddd0701ebeed0b71ac06ad72b45cb
aca35772f473309432eb12872c68a3ce0f823772fb096617c10467301c12a88f
282659169537690945f4985b9e9e38636a08fe66d760ddf90cf288069f5ca1bb
1e3025c5dd0b0993478ae1b220aa3d7e8f17e7dc95e1555f95317c149f0d5802
cdff6bc4fe960ee10aa7fd81f8d29e0f8ccde08189a97854420edbd116c878b3
3fffd512e9b752d581b0643077aab2d5ca8e99b6962e01ea5e0c39c444c73338
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 1a5bc7a42d51838dbc3225d4f883494420be3b0be5ff563a7fe1371f41076a49; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 1a5bc7a42d51838dbc3225d4f883494420be3b0be5ff563a7fe1371f41076a49, and the block's
timestamp proves the page looked this way at or before that time.