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
8eb98bad4163f93ca66d2130cde2c3fd5fa57a4106e3ace45ff2d92657b523b3
594664a57855d3b0afe29f1b766a5d73090a4891002f4eccc043663b2c6d86b1
de2c55a57ce6d4d295d201c8b7a0dfdf50aaccd289f3d882962412cde8fbb563
00c0816edc5da4b592f729f8e5c1df4a64f7693a21cd78941254e232cd7611eb
7ab7f8ce41a185511d42007df344f0e7988464d577a58f97da970299c5e9d3f5
8eab4c2e60b307598fbee7fed66ed4ce3532c72a653e27165fbc3c820f9a0dad
090010cd766055d6594063d458e750409d215f40bea5be19eaf4ba918140319b
de3f1ae6ebf666ac9a69701373ab84ce11a15ebea17e973601f2d8f30695c300
4492231ca6d731b82e88b05358b46cbb73696221ccbf7550f23147f3ba969c68
eb768d32d84136dceca717f94097583e2c300dc4519213820c94c0bd4547f82b
d136a032794122256e7216f1996390b002194200358c4570d7cd2faf1a8fd15b
eb227f92e09af637ecea017f87d43d0230a49a027d1cb054ebc07bd2f9339700
5854296083ffe5541cc31026a34bd6fd40372b69784da6bcc17fbf0ff020d21d
abc5f55659c537d1f3d74ae2c3c7fb05375a40275ca0b7ea411ea74c9efa7253
74eafb59d91113e1619f0c2bb6ac4fdfbaf8cf2202fc933480ebbff4e1f646f8
03cbc7a67ea89109ebf9cfcc47902d31c32af2c1ae62ad061221379c09562005
d2d8ce7b8427ba5a6ce79b332542a79bc377f3c67ebe0b75c5cfcd62883fb9d7
b7b5f20adac8b9709458c540c9d722a50f54ca150a6840ac91bd2310cc4f554c
c132f3d9fddfd093779ca31a1b19f7c967e181c2ef0c4ce6660812e095241324Trust 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 964898 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 9f370357dde6872cfb5cd278f092df1e7e7ca814bc7f3de21a45a9e3e8ee9fad; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 9f370357dde6872cfb5cd278f092df1e7e7ca814bc7f3de21a45a9e3e8ee9fad, and the block's
timestamp proves the page looked this way at or before that time.