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
40a41ee415fd80baa84e5ce9b847e6e1032ee8f32d3a3bf92deb2a10eae1defb
93e13c9c7f6e9d6b086dd6c11a02dd83df9cddb974634bbd3f63bd97a9951f5b
cb82c0b2b02180c44a438d956b808f57d4119f07a7b42c975cb11f941e4be6db
11f09fc68ca4ca73c190b5cc48369487c77b504a8c46a6da0331df282ced9bc3
e64c2799edf14ffaf380bb27f598469b92825909797f3bc2c78df213fca4c135
870a0d890219ba7823d0efea6ae426a669dc8c9c07e5759091dff2fd57ef825e
5adde690a00dcecef0324eba240a28034d3a13a47b0a5c708fc261b50280ca08
1e3dcf411c4bce182bb12553c210b006d806eee9a328ccf33fa962c3a788a1bf
d97a06a3629f758240f974494497a48cca96876b6dd2306abbe795c9689e63aa
e40bcd3c90e791d60b545469409ba6764f3817cdbaadda0e4e9ba338505450af
17091905e5142fbd205a679c4b4ea1bcd7e6acc7ee2a0e5d89401bd5c4bdb4e4Trust 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 967750 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 cace189cc1abf01e5a8e60ca93b16f361dcccdc0b28527f481aef39e54c7da97; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / cace189cc1abf01e5a8e60ca93b16f361dcccdc0b28527f481aef39e54c7da97, and the block's
timestamp proves the page looked this way at or before that time.