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
2dbcc81918c0a7a7909e5aba5abc051c8f2c5f4520c8f87c7e7e69666177c6c2
f8c5146c368159a221cb2b177ae55ab9a99780393eb51c6bb6048e17e9419eb7
835084e413aa2fbd780d6440fe1d0d80ea7aacce1cbc962e9ed918ba114c1362
1d097623ba881212541541ae27fc3961c592c7454a5cff4c4eeabfaac13c5f87
ff6ee944d0622ced6a4de78efc4371d595e565d01efc6aa876c57c904523d019
bf4cbbdb6a2fb7f50be7bed308dc4444bf11ec3b915a61e95820ed6a127c3ead
c1291bd0b748cff7ca007422be99f70a2489e9ea0ffa4575b08696bea1badb4d
54f999fa9978200ed05b8ba0aa6271a2e6369afbfe35503663cc424d8cb045d2
f68855db249fd087aff966b3232bffe1e62d9b6133409d4fb2057c743be84179
29ab6f36545e59c0d2ebcc80d60c80b553cc6e66645c291fa18a5142f06fdb26
28b01fde4aeb1e2c7dc9c881e5e28a42a53f936c809932c4130627c56b02f439
8fe7c5d0509fef9b27b0037d3ab09e11be9470f0949cf7e3e783bb3e654992a5
c5f4f84f20cce3b360dc6bd061ee387698dba1fa28750859dc5ba12720629497
603839813d5cb9f83daafaa230faebe73c2e7cad4bed376385d11db98377b106
9fbe38b259699c3e55bbf17561759377b8881ec7f251364c3d7e76db7f78d086Trust 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 964442 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 85fbb0ed6334787be2122adcf855ad58c2bcef9420eb26d48064ccd58a7f2dec; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 85fbb0ed6334787be2122adcf855ad58c2bcef9420eb26d48064ccd58a7f2dec, and the block's
timestamp proves the page looked this way at or before that time.