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
0ec047bb2c6a12aaed62a469cfcbc78d89b9ea275bcecb70ac9504b782d0704a
851829340c909fae75e4160872cb45d081a69c1bfdfae213a142fade54ab9c48
6680e30a281ce1cea1146c76fb8ffb74f0700fe06581a1a33b9ee6a2dc0e0f20
e4feef009435971d50f8883d2efe919af0e3b4f6a7e47a3934e18ba6d2bd5d8d
d9a76204c5432a6b6c8621f91b3a8e3781e57b8f15ee3e33ec06854009be0db9
5ac4d5b9d944d94ef4f273167026f309388c06504d074c2549fc63b3069455bc
d563f36872edf3beabcf741f80f9e1f18e8997301545ff47860400b9aa997eb7
222f3b8bf4ac2e074d925d22d0c22452e2c4e48636c0cc99d8f9804822d2dac7
e8b2f0a61159948967d957f14223a05e741ade66ead2e93ffe2e718981e42c95
ebf88f9ba7dc71e860b59f724b7e3afe9bd13d515276d39738482c777e9fb675Trust 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 962022 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 cc8472fda896103d25f19c05b5419ac1991816c7c87658f1d54ff7f8d308cb2f; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / cc8472fda896103d25f19c05b5419ac1991816c7c87658f1d54ff7f8d308cb2f, and the block's
timestamp proves the page looked this way at or before that time.