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
52350f0cea686728df9565583bb53f2509da1828f1c60b232900989ac6e22550
f3bcea4fd4f913859f72da4bdef79856865583f16578146f5eaeb06dbc39b968
3b3f04afe04c69703b67abfda42ef4fca1d9e2da404518a0704a83e8d3d5b1bb
25758b965efba533c0a27847ad5e337bf5129617d32ddee60b73fc937d4ab255
8ec1cf7ab8801023f2110760a69199ce329bff479d388cfe140f8c9c16b0ad20
5a46f74e13530a617bd54208e42ef4f4573c9e90a60228e6baa3ad59fd29a75e
a4c3d5d1b10315ece40504f05ab152e411310948a91443cd3f3e9b420d7165cf
ad2ae28117d3396ff3ca2d0cf16c4b8fd63150411ebab21c6e211552df8c4313Trust 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 964107 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).
Save both. The manifest's SHA-256 is the anchored id, and it binds the HTML hash — 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 3d4ff097d82530837a88c35e438c9d1a31dbcdcfa3c7cf037fe2d705766d2805; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 3d4ff097d82530837a88c35e438c9d1a31dbcdcfa3c7cf037fe2d705766d2805, and the block's
timestamp proves the page looked this way at or before that time.