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
5167793a99ae809e8e7657d8b8047e453783e335607e5aca0fd6217f1dee5fbf
d4268200f194b7cc4f2024fd337ebdd8eba34c92822d168e17d13b25575bed74
958846bf7697afb08e847950f06bdda28d0d2fbd9d89f7c06cf4bbc1f0dea4a0
eb1f5dcb861bb8d15eaa7d748e05d2b50bd5dd87a8b11417e9220e7403380b16
473d2e2408487f74be47cf535b16cdd64c02df78d8409327654670810c097af8
9f3341ab8aba39507680e06ed272681c8688d71b9132ba7a877ac442156d00d1
a738d2c008d8c2080d7d5a5f7e255ee73b4d556a71f782db84a43a4ae311e89b
d74982fd2ca07bcd89db455d19bdc685b5a94e1ab0dbc316b4f277ee8496b930
bdd2f6aacce4a214b51f214a5a01a0cb933ea3276b626c17c3ee03a8eecbc1a7
84a200bb76626c629ac3a80940c5e37c664a0ba725ba9398263009efc1b47d4b
4df49d4f295c0bf04b71e94c2135d61b9c58bf9baa5a3b6cc85388a649d08879Trust 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 970722 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 83817212f31596151a654e346e9f3d69ce80c9e2dcfc78a2430427aea965cdc8; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 83817212f31596151a654e346e9f3d69ce80c9e2dcfc78a2430427aea965cdc8, and the block's
timestamp proves the page looked this way at or before that time.