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
e4aae27dcbc2f246f8c47b237bd1b4e1f8f0a4e96e75136bef2150b790850edd
7dd37b5d885fed874e98825a33dab1c008d342db3fa002fc029a805ca92a2a78
8a4cf98c2dd0281d92ef55c7c2ccf10089c6877512fe1e701bfbe9330a9273a7
333e1b2f2be67a724561054233ef31850f223b6b9dca87c6232c08f0a050c200
648535a0d9df15c9bd7f9ddc7232aa8d9377829575d7c59bf509f7f176ce11b4
d8593f9a9a518524baf537f9065a06c1b41da3a68df34fc60c00b35003327096
1dff42f3e6d21ef1e5f2aa77dbd535f530c1b874f211a27ff5e0c399963a6738
34dd7d80021e49c59fa292c5842d78c40d8b8cd6288c97e4f08bc804c802d4ad
c1727f946a22a3548eb528854677a664e94b99a88d2d80704041307e9468d007
0631dc3938338af7cbe7ceb6fda63dbd71065fa0a2907de80e371f8ef03cc470
9cd548c37e5a67a9a78769800b5c2b1ad4e89023bcfe21385ed772cf5a552316
709743fbb2a17fd16323d3e214f14e555520b03157794f186c6163403d5b06b6
f922ad8703bd3929ce5ec8612b2615756e83e58228156a99c1b19a34fcbe714d
*
640033128f98e691f4dd06842b0a0d0ddc7fd8fd967195ca3be3bfa7d941ed0e
580ebcab33cc72c3e7fd29a6606ec6e3ab7746b5abcfe1bc3cd405de337e7a24Trust 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 973505 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 0299f72010f9f37330e3654bfb0a16d2179f08422c1e3afc34a92b7d505c245a; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 0299f72010f9f37330e3654bfb0a16d2179f08422c1e3afc34a92b7d505c245a, and the block's
timestamp proves the page looked this way at or before that time.