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
ed3ec44f59a45c85d67d62b55df4689c2babe0cf94d2735ff925f37177ee9db1
f9b7bcac8299abb9639341ce7902ee64e15cfd7314633083a7a3dce54b34c901
ec24206d5369c2816246559a1402bc31f1208c5417b3efb1acc235c54f708355
bf9e02808ce622ecc5dcccf758677694dedf975f9cb945d1c022ec77e85178a0
d376a2f40d4f0120f108564fe716223062006697d9cc9dc2bd04353cd1dd8161
f194b1151e58c9a928c6c0c61fdcab0f1c54e5e424074aba63eaa592de191582
f0d4a90eeac889e74620eb3f193693ce4cd9dc4ec563cef829cf17869300e519Trust 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 963291 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 81b16a42bed8d48be1ab6fb493a64b6f19270f34eba3693707b6963d94f48955; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 81b16a42bed8d48be1ab6fb493a64b6f19270f34eba3693707b6963d94f48955, and the block's
timestamp proves the page looked this way at or before that time.