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
665bbf9a3085590810fc09d62713dff8a0a88e041c7a40c365be0d673e824ea0
db42a07368eb99717713767ff0e0f9a9bce2878ecca7e8833530acc0a03dd820
a14f7b750d93122e6bd7cdbfb602c2fe2f7ad3480ca092d9935db3beb5014b0d
e0e9cb086896ac2db9c3691399de2dd2c415f5c8707a9889456911a2551f89c4
05365f35b12d831e0a6993acaf05eb7bf59c53b6942ba3a5bdcc3fe50718a969
e66776d2fe957b84b9258438c70aeb27b2d507a841a9f7df5fbcd123f44aa218
f4246a2743354864952e2ff8d31562ff2a6bffc28941594cc40ecb3b03953c42
95a4f3209a345248d212c77f70ee777273ae8b497b299e6a5a53f8def754b045
1a94e4fb60e36ff2f88007e002aaca42064126a7e1eb2bfc4f5dabe6afd23faa
cac264c1ac0c95e5668532acd6b59478d36cb53aef61599396b0967923fdb208
f9d2d4ce1901bc20a4c937ec7367fe0381a3083a0faaa9b7c2096b210e3b092f
719f64d11db75343d83779568b71255351b0bdbb436fed6435f49c6d26e8ac17Trust 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 963633 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 9425e5cc2d7eaf4c0ddb6fea667c7a6fa81fdcd7010ee1ccd726a7ed954c279f; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 9425e5cc2d7eaf4c0ddb6fea667c7a6fa81fdcd7010ee1ccd726a7ed954c279f, and the block's
timestamp proves the page looked this way at or before that time.