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
21c8ceafb042639d21686be23132766b5d39defa8cfd22c2cd75a6a6434a08f2
09759474b3a01131c5159b7f8d92d51ebc73262fb55c34834eb2f2b726d49152
c50f289b1c462cd6024c99be8962fc2ec67b7362f2ed9dba694d855b7a0725a8
47d195ac8314a0558707dc4015238269416959737cc82602a86fd0dee2aa7861
9bd18f80288bbf8e501e097aaacf2c3dba10429708afe22fbf7381f99b71c79b
9d2ea7abaa6db19c89b27cb3ecbb02ae5ef626e427badcbecea03ec266ba356f
83263bfc36814f0ba7fb3faf751dba6a51296b988d7533937a2df4737ceed39e
9e01ae76a2d2b42477b6af7d6a8bdcb403d75d8718cf0472b90e3c1dd78f2988
e74764f77a33c62bba996aaaad44753ab928b18793c7e56a427c1d82dd956a4d
86f8464d178dae4fe2a7e4eda4003b14d07c1d481e80e8ade9535723a2f83468
4d9a2997f0a7f8d3e993a523435d17c77ab1197d3197bfefd024cbd1041d2b9d
9e556d390d3075831616c5f0ebbb976639b2335db55f936bcd44f2de60341b2a
da98b80ae00a6536ccc3a7098e41ef85a970299aa7f362c6af0eb11e6d4653aa
c8bac9c2604cbecd65c31635b23a1a90d1349118fef2d9d91a3a5b1131c7aa37
2cc970a10147e18a7bcb272af1564035559ed284455d612429801178bd873e42
e2322b3ef1c03afcacbaceaa3b1bec6ec2e45187fc3b6cfd9aa830a53e4f9c68Trust 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 963891 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 4eb9d920a0e47f92bba3492caa82799d462826183b1caff2504418bd77845ab0; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 4eb9d920a0e47f92bba3492caa82799d462826183b1caff2504418bd77845ab0, and the block's
timestamp proves the page looked this way at or before that time.