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
06d95eefa186550f93710637cebfcee1310d06e719d6f3a53debfefded6edb42
b9901f4d86953643cf5d5028be38b06d4598e42550465422873dc28c02baea90
dea90e7181410d41a99b5a93055e1206f0227c5d209e3d61a4fb767e27abccc5
b43a95ec5aa706a4dca2326af29ab9a511d017d0748d8709d11d5a53e6cb693f
29f779602356500382bead87e3bc54134315d8283ca7ec597e9588b3d49b1a44
2800bbdab422a92ca05773969379a1d745b42c76ade6d7ee739fb2a0d2cd4081
15aacf0c4bababdf8f340df2806a08c642fbeb47ea86e4856ee11743625c1982
44c84d9c737ac03c765b169705890cdc20e3aa8438ef0ccf818db128a851be4e
0803f0dd31ef19b3046548d80dbe413413c389ae48edc5902c6357ced68b0182
844f9915474ae4a5e2b478c645ebcfd03486c3519e59b56ac2d184b4d651ad9e
7b61f725b5a7f155b2faedca105c5ca2be688b1ba904942686d10e9f904cf52d
fca453b447450e1258ec917504c49e297b57922fe8b61ea743e4882ef4a21312
b9d406e98cba6d93d92983a2f134529f6f9b163ba55001f929edd0231856ff97
a5d54cd093e2ca45068b55276259261fab2e930c67b2cfe6ef6f6f323a30897e
ce449a0df29ea46f0dc53fd58a4a75c0c632d401d0b53f4127a261d45cdfc081
b75d5cb5f30643fa284237455f0c396e32dca31ff65fcd16bb5efd9faa5b95d6
40aad312444dc7fe7e3eb64a6f4281899e8299c6214aa15ab30535fb61bff882
cd2fe06273d26478df53e82698f3c2781ff86cf3bcf587d63473899695ca0c03Trust 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 963589 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 a0fcedbc3de70d906b79cef29d52cd170568fb8c1861bf6a7179758e6f89d206; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / a0fcedbc3de70d906b79cef29d52cd170568fb8c1861bf6a7179758e6f89d206, and the block's
timestamp proves the page looked this way at or before that time.