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
1d23d39758dd976db1b930307dd60be3e1689f356545ae1bc6ecf45ad2ebe622
918cdcac58b7557baa2858d794e3e14c5cb484eee7de13c734f0baf74a077594
f2f447df734ea6d95b891f4b48b13564fd9ad397ac07371bc42aac2c9aa1d90f
bf92120ced1c5942d9e84ca48e25ecef3fa9818851e1f6cf9db0647f39d7e832
51dd2c836789fe8926eebe380bc94e9e4225f3e993301e76f60acb403d179700
ef2f1f72c96026ac0e74952a37cf7e0934d289f0d5d3e0341db544023fa353f7
3f1baa5085ffbe159ed1ab14bc022e655aa63f93eb759d9162cb1f37dcca0fd0
bea3fe92d578d93b30a0b45e3fdbb6e98437a7e7c8b4f0e3034a3d63daecbf4b
0a881ab50b3f484c7bdd31e5c738b08e6069f2cd16e20c2d36c593e1f16627b0
32111c8acdb4ab0bf591704cd6b39cf33912afb4b8218379a2976c45633a9533
1607ee331635792ec6c7be180e27de81c8125043e710336d6f1fca8d35b128bc
*
20e271a9f9e8ce4047746e709580687194f42828a392b9d5cf3aee6df4776ebf
95c980c4076ee2ca83373acc5de56afff914f014c84864d6696898543e331a85Trust 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 971071 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 1d5e001d188bc5e7d99774a3137bb1b7e080b090a44ff8c221569e72ba637fae; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 1d5e001d188bc5e7d99774a3137bb1b7e080b090a44ff8c221569e72ba637fae, and the block's
timestamp proves the page looked this way at or before that time.