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
2fc2116efe0b3535b5e7e17c3e06039d81e57e076558ac99544ddf8aab842ab7
eab350344ad0f4366d14d935d3a175294e79592be8fcc177d2808693f25ec1a2
b6f9845aaa4e7748a35c6e268b2c1fadf02cd6c22d18b8904f81fe798023b386
a79ec386fa6a27a9667e8f84c2f36fbcab9cc970c9d8cf21ad4e422d416a1c33
ef5db7b0fa5dc44825fa60e976dae4653cd4811c7eac10b8e1c857756f0578d4
bf3f340b73c735d5cde268054c9e234b32d97ac5623eb6c98289ddc25cf40930
6fae145311a068089aad046f6094a695da9cf66728c3b46b5e221fbcec620c1a
f0dd7cd418f660f1a94663e5013d9e1116d819d834ad70dbe8031178fd022354
e56656c2652ea51ce825d57eb3e6c43ce64f75acd5d4b7749d33247916b44c51
fd2f08fef83dc557db4fbb7ad2891cdac2123d5463e54f6449a327cccba0b108
eb9e351b6b2c9fa492a8994fcc459baedd36e00f809d2bc7c328e178656de013
2980d17cffcc7a16bd836bc687a5e12d96e8df09382e4106532789d8f31e66c2
e24b80db8ab2fef6b27d24f331993f134b354df6e0d532042b3f9d8e4a0555d0
84bd730d712592c7cd9dd03e51ec04290c8a1965e809ae581baf3a2d291eaffc
a864e77e4f9bfc7d38a79fbae4465ac84e9600eb30d0f9f30bcb876262f77894
9aa8a91bf32262fc4b3296c4b80f987b4c9d4e47200350afc1d44746f68312eaTrust 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 962296 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).
⬇ screenshot (PNG) · page HTML · manifest JSON
Save all three. The manifest's SHA-256 is the anchored id, and it binds the screenshot and HTML hashes — 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 0f4ef1752b49230edf1e78c417de0e09ddfacac0b2697c1109bb82532522d5b7; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 0f4ef1752b49230edf1e78c417de0e09ddfacac0b2697c1109bb82532522d5b7, and the block's
timestamp proves the page looked this way at or before that time.