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
613b7910a17511c14b03e4bd1f7332766d5c95e94837f0226fae32c616dbcfa4
764d1bc505cc7596c8b7cca7af41368de2bc4d64b37983cf79ccf270ae817967
e3f8c28677d2bd92aa98f393a6e1f282d3128bf49292c7ce36dc961d7e5c445e
02c9c7673d04cf32492432116dd760e43e873a90adbe9b643d267b010bd9f38e
8133fd051495ee26b21089d3979674c11d32e91a32ec6536df4e437a9923cb19
521a7703dc1bad0b9d028c5764d8af576022f8d5b8085d9b9f8426c668c0102d
e3034d7f8246ee573f4b3613a43bd6f856cde0db47f63d9c91cbdcd9821cf657
0cb5e1f4093549252cf91d646f5c5b97e9c393f00d796df537b4581cae6fc988
1aee5b69e7fa1f23e62bd40a0faad767cffb6ab69eb3e38bea68d83d921bf763
62036dac2e44b29a3773b5ac17b232c4ce5fe9d35cc17fef1e7ffac925218c41
fdba9cfdb865979c81b83cf77a0ec41e49c46d97e82a427a4bb4008e0f7dc271
769357f2777b1c0079581535eae70b238d0f683eba2c4b95ddb6eed65215a43a
100c5ab735309b1dffaac31a905f28b6d9cbd8a99d7b16134e6d08b2e54db28a
13349873f1d17bee6ae411efcf38d308cf717d2c8f6eaa19f9b336c83b93b216
c71a159c9192e01d488fcb0eb9e2b34380acd64111642f1b16cd90e169624ab9
c74135cc37fb0fdbbc2aed9ace04c861ea96c44f25537d1f127dd648a80dff93
a5a893859a27df60d2114e567851475a9f82efe7c48afb0987f63aea8176eb31Trust 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 962352 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 2dc5f14641f32be5a7b16e1a48b04ec10730db516682cb0c02f8a6456439ddd8; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 2dc5f14641f32be5a7b16e1a48b04ec10730db516682cb0c02f8a6456439ddd8, and the block's
timestamp proves the page looked this way at or before that time.