Web-page notarized
A tamper-evident timestamp of a page's content. Verify any proof — 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
cea3e0b4d1bf104da3f2fee7079f8724576af8c2c8eca9bc06ca89145b342a0a
4775c80d5de8033529f2d04231cc10cd8a6549b9216831ae73624959a9ecea36
709cb0ee03f520a8690ed4ec7e4c3c2ef487822f47640e201d566c67bd48c6be
a7ac4b04dbd341d385c12fbad2a132f12f70c2c2c7c0fd40ea78cedcdda12ab1
c394623ec02b743fb85476001d3da6880b0e7515402779fea11a7f8025d5acd7
adf6e3901652402d137fc7c6a2572a2a5648bd68faf9967a38ec0ee76998bfb3
60b18d2a9e5d3a7d445c4fbe4c8afeea8693fc6c7838aedfb567688536ebbc04
4ce404ca0db8e462869802fd03221680583df6ed80d5bd7728107795bd06fde9
44e5fa51837a47e03202584f2e3492d1258649723771a7dcfaf228ba2d6a5025
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 24d526f1e0892d293f54d7f0eaf0099e485f2a0f594297026008dd1806e2da3b; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 24d526f1e0892d293f54d7f0eaf0099e485f2a0f594297026008dd1806e2da3b, and the block's
timestamp proves the page looked this way at or before that time.