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
4508be90c3ea52c8f6d00645597853cba125eb7b026420fb8e3db4be4fab9273
0cdafee59ce1a727f197ccd8917b204e2bf24e868f211ed394ffc96510b58eb8
955cf91cdb1b3e6296f8ba9a48d2a476b119e27338f5ae7f7a2239460a39528a
6a0f1f68d0b7115a96564c9f71bec812e38239b37961434a94a4327dfc16e090
fe99bfb59a2b770f121b0dc6a96b79b7dbe70d79b94bf4f6dcf1558cec2b77a9
43f5fc1f770252687281255c2b821f43ecae8d1ff396f375b92955cad79b9a22
8572e48c0ddb806f99507ed611d546760eedfc61275538254088d0ba855d7a5e
ca5beeaecc4c0e74189acfb4c35c7fed93931a3e0bc70b09d21bbb0e356198ec
37ddfd3fbc1ef1742b5d9306175b90c4f5d66417821ad1fa846bf304813a4d39
06effb16858e05b5037c1a7b87243a557b810e83e4b08324341258fd7322455b
65249cc55aadddf2aa6ae830145737ee5128f2b1bba3cdf8542f8e176ea19dc0
09a6191ec8a0b037f359816f3943045e677c20172b30cc35bcbd94d2a11df59f
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 7df8aa9b3c126fcc49aa48bf759fdf3af1a43bd70496ad25d8d0918b5a44681f; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 7df8aa9b3c126fcc49aa48bf759fdf3af1a43bd70496ad25d8d0918b5a44681f, and the block's
timestamp proves the page looked this way at or before that time.