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
67ae333df0c681d451df43d40053df664eec2327b18cf43e01f19d34a20f929e
a5901d1126dd4279a449bcc7f8e41cd6e99dfb7ae97294e362c5928dd04a4ecc
ef5318a2b1169ac206503c4b64dcb4a6a05306d8f2fe19f70086f6c0ec0c6b06
680b66592ec0ddf6fab9f2153ed59f1cae1da42f7b2bb286b635ff5af895052c
4feed4f33ac84bf8da9df97c850105b0fb485ded2f98db2bb753a27d1e4ecf95
89cd8b6f62af5d0323b593c240416afdfcebd0942ef463a02e0bb7d1ab12c51d
64522bb904c772cdb7b10e6f42415d294a82b8525f64a40adaed62ab3ecacd8d
da4c9afdb55b50f06e6be3994f2c78900003e9d7cc2564294085caecbb7cefe6
18438634eba2fbe82efadd4f6d30c63801bd4cfe2d7bc295aa667e745b3a58feTrust 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 963821 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 0cf50b91a88e6e2868ca5bdc758086b592db43db7630c25c59a4cd3993b46d5c; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 0cf50b91a88e6e2868ca5bdc758086b592db43db7630c25c59a4cd3993b46d5c, and the block's
timestamp proves the page looked this way at or before that time.