Web-page notarized
A tamper-evident timestamp of a page's content. Verify any proof — 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
29927fd05f589fc6ec3aa8874252651452939d72703e35bfd49b68f2fd95f9ea
230694c2f8ca6e3d32e196fe228f09ef7e9d38b2091657907a3f730ba4cb85bc
c9b770b6e2ba8dd4106fa980a3e1ebc4ae394a2853390b59feb2c915ae0a1e4e
c77b08f978d2beb317050c3752af6a916c5915d24017ec80dd8f2b27073b1dc2
da04a15c8ef864ec8fd0b51f2ba72557f2cb71ec017cbbf75e2118006f37a28e
d3c7f648ae8a37225b9776cab95f7b78b922afc8de7e8c4a1721fe6868f1ab2a
40106a7f0f9aa7c3f98724a91b7aae63bbb10d29f67a1afd5373592b340f47d9
d24a11a29f64d794a27c9ae4daf6d336852d97c0924180fcc03b494560b4d6d0
a2068a7fe4bc58847d6090a3730d9df7924f36b2d8f552f1f90e1394f1142b24
0889424b8f476147169989caedafcfdd8031f5d04626a6fc0d002e8f2af58a4c
7997edf372f400df29688b3342b43965948570be6716c4ce83e0a34183641b32
abc2daad23e261f6b6fa92ad01265589a4eed477180ffd737f461c02a0ba56ecTrust 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 963916 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 3f97c5c5d595fb53bbf2329921422ea26f86c874408f2df84f660da048832750; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 3f97c5c5d595fb53bbf2329921422ea26f86c874408f2df84f660da048832750, and the block's
timestamp proves the page looked this way at or before that time.