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
bd9ce09149ec7e775315e91ee0c7655d83386232d751d8851e2296388c2c3d0b
657e9d6b8dd8f6cecbb0ed0532ccee85431109308561a8e86e0f4410275ca92e
4339a632a876cef3e4843e622ae6199548aced138d42029dbcad2e6c6dcf6149
620b99206658c08cfb8da09cd7db06b5e6bde67e866afcd7fce93b7a30d6ce99
fa937df94f5f05eb53a1668bd04c6d025b41851b2f4d50b57947b8d7be62a0cc
0c7d080b85ed53c9393a0654019d0454678467104605f0bf0de22eb2f6ea525a
92d52671d6845fce889a2d642cb3c759444e4cc6918343850c874ad1dd99d005
f571d27e188f9ada5bc80d86daeb8133b780f34a6d544fe16fa7f1de9646454b
d51fa7de37bd4da99845fa2223bba3f9dd2966709e099699408ad5d46051cca7
bdaf7c11eadd3a08ab8b1d77fa68920e421dbdf519bc3e87254614a7e7561350
62d0613b6e8c9c8adbdf91dce66e7d0cfd90da718dd50b434b8198ada8e254e1
e31956bcf487ced63c14340ee997c619d04cc44917f4d4638d0ae31bf23aefe1Trust 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 967924 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 dbfd0c6f91ef4130f67c5bd46ba60caddd175a6c175f5742b591f2433b681efc; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / dbfd0c6f91ef4130f67c5bd46ba60caddd175a6c175f5742b591f2433b681efc, and the block's
timestamp proves the page looked this way at or before that time.