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
f6553ca4f08fdb116fcc94d1af45169f6723d8fb8f1be26a5e7791e363c7fe58
7fa76711682458ccde92252911484151e89dc5d174725cf7f25a454edac0e249
6bdc813caedaa8f57b5d7bd96b9de706b73e8b6321d3ab333c9eec5bff9b7945
947ab71d4f49ecbc0b2fb39cd0933294d8492d2ab3272d0ed5758ca8aff2d618
1743a3c5fc6d44ed6f75db121801c6d5aa32cbe039856834f3d4b6b0c2ed9d8b
dccde18c6943aa79d73efcabfeaf919e2190baee6ae17dd97a2b5c32d84f4f82
74b68edd37bb8587e01aa57c00200b0d3cd4fd0f79c30051315c5d93f07a3055
007ddd30aeee70062dfbc48a2a8bdad37946dae21cc60b35f495f2e4e028aa62
bca74e71d593ee53c17fa529fd5260a55b55a29477358c563fe817a25babf266
c76704f64a98ab9c49026d49c12ed9c9a750bbb345aee57869536b7eaa472768
37b60dd23416742d7d1d3e375caa33131e60ed6f5153b0f7598ae34ab3d7c307
86253433f2d8127aa791b117049882e2a8360c0f825df34301a2d58056a513d5
93fa378ec9bcaa44d0e746c27c1adb45a4c7cbc2ceee99284ff9049e99a3eee1
b6fbc3a31b995f045444acdb3832c33934e7174480379cc926931cbdefb9abb4
de8bf5d6a1c4e50b920fd0118790db8a873c4b22a6e5eeb751fd5bf36759ab24Trust 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 971767 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 239415ec803d2027b20d1c2b35acbb8d5a56b758b161f5f9d5e05973d55fff2e; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 239415ec803d2027b20d1c2b35acbb8d5a56b758b161f5f9d5e05973d55fff2e, and the block's
timestamp proves the page looked this way at or before that time.