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
5c37dbc12d3af465709b9d32bddbe4e3622cfe3aa139de50192dc63376635084
075b3890cbdaf845fe38885323c5648dc08a86d2529a477dc85d6e1ca2ca3f3e
302ce1239ac96cca8326ab93710bcb0565d9bfa39c51851ad12e75cdcef6d6e8
5f9a069f2da78839842135370651eca4811c8c22d28ef3446098ff35d81de489
e6808863d83554c8b3b212ae799689612f568411ffebc1e23d19b690d6309991
a14ccecf7e7e368ebdbe7c1c450d964c834cc8966acd0b1219dd3944cc7f57a0
e2f05bdf475d0920b01cb8ca8f57df0050c4bd3b331bb6291ce7bd5b259bf7df
537940d890a0c71edf262574b55467b49f3d2d05a72caa52d7c1625c2f30b3b7
8e85f1393001c3c0e62ece32684821839c895360430e56978f860236afa2c2db
70fba6083b793bac051ce6c4dfb08e7982813ace460bf016a09f205086f719a0
8cb1e418c216b51b500c19019429b331638ed44ae500cb0a9798edf50fdb6cd0
eef5919edcf78a320698ea3fa79f159fc48c74ade09e9a716dbadba64656fbcb
7482bc1a2f4891c36bb5b3334126e3212692cd5d620125bf5dcd5f9eeec10868
820401fc6f397aa39bd6b4d08de677e4a1943b2cb2887cedccfd5e5f43fe26e8
be28d1326194a2de5a2675fe48b0a4abf508f91103251f28b23c28beb8e432d0
81ad7461c830d05ca97b9a8cdcda980b88fe715b851b458d50c6bb6cd991dcf4
6dcc314d4a43aae5efbcbbdc5019dda2d359c1bfdef5254b49d88ea1e54db8aaTrust 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 972130 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 a650b481f5cc84ccb04fd3c1cb6b7fb8f8f143a7fdbc617b757f914280456aae; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / a650b481f5cc84ccb04fd3c1cb6b7fb8f8f143a7fdbc617b757f914280456aae, and the block's
timestamp proves the page looked this way at or before that time.