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
f9894a3b692b6814d2eabbcde41862fc6ac31e1d2ae92abcd1a1be9e96084aba
a7171e2228c19d609f962ead7d48147457e7892547707672a286707e5e3eb163
16a4e8c09651375e25db6a8643b86a1c6ea5639951a66584ba511ed4eef81099
3094a3ff6e1f04e2c52a0dbfcdc71e3e7ceec6971dfc57ad486e4231d2f99842
031057f25b91e632153b9d973d4a1432b8e5a7c92a6b8f083e8c3771f6ef2956
ed677debc0e65cf46f4dfd416462f33ddd9d1da8bb887467ad9e486bf237bbc4
6bbb81fab3674f6213078745a9bc20166b6fd1acde778e265e8425bb9def22ab
1c00c7e85cc97b42a84f112e5bacc01b0b7a7ac1a09a8d2eb3b465c733635d9b
cae8a93882a207d993442fa9741c3e361a6ecf92427845407e972a97323d1408
4d8bafa0cf6ed339db3e07ef9688a4dec24b316eead7d03a7d052f420d175dea
ad561580d4102ee3f33e92c9ff7976204789d233a57002f5e5785ff5e9dc48d2
e6db82983217a12bec083d4b81046ec5f10222e8193339616b81d29933569c1d
94760bc49f664add1d0c09b971b9225a6da8ff7e79f41467bc1eed353628b9cc
d0e68e54cfa6831f8467be82cee7afe10de07c2e6bcab8bc00240ecafb6500ae
6283c6971423396a5309254bc3bc20c39efe6dd2d2f1ed29ef013042fcdac42f
932b4248300933baa0c6a7b50577d73d6092040189c3b5942ea664a22b5df4ed
f6f8a44d6fc1893d3ee97eb69a2fd57f695c193d8c45d5a8b75fb60eca89d72f
d2defc7fd2f814ff570a1936adbdc3b11e69dba6e7bd619c39d7a4122fa492c3
9b651cf2350ceb6012769b9038ced40f8781a361a2f4a3c5d60a0a3a928a0b75Trust 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 970741 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 b295ef20b619d21c985ebf24cc4ffad108817f0ff766b504949ae669b0cd0aa9; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / b295ef20b619d21c985ebf24cc4ffad108817f0ff766b504949ae669b0cd0aa9, and the block's
timestamp proves the page looked this way at or before that time.