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
8de9484d822f9f1654bac873cad9de0397e5a53700aebd8af12647e4ed48200e
e28a3fff7e88992d30a95194ad60c6fee54df282f194af5c52daaea78d6adac1
d3eb9686440227c9fa880c68a319daf4384805818a806fc5ad8b31ef6bab84f1
48b835ca5fe26e3595459bc1695836ea8632a877dd5d88b8c5edf4aaddd3f813
b7276a9b07ed1bee94b6c304d38d829767a1a6491de4d6a115898062a92710c9
0c57071a04dac95f327446eaaa621655a7a354d09b9ec12086fea89f411e6d90
a083b3e2afa539fe59a57ec885048c8a0e5290c36df72181646bebcd69ee1821
b6538737c71f525837d93c6997fcfa5aa2b21148265a8ce2dc4ec4772f15fddf
3fb82b00187896562dbef88b1b02250d2a809e4bf0cb2f3bc2f383758d602723
99c4d7f0f43533d6a68c42aa98ce3784ac6de939b80d00218149940f555a2edd
4c6623d8c4b735f7d7dbd52696d71539daa65edd41331a1eaecd27c63ce9de79
38a65215cffe0129bfdd10f11936954d3863f85b7c7c0d1165ebce48d32db858Trust 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 969276 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 5234a7f3e0c51d044c57b6e36b0b8e11bd1f01027eea022bc3e5b62a3af4056f; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 5234a7f3e0c51d044c57b6e36b0b8e11bd1f01027eea022bc3e5b62a3af4056f, and the block's
timestamp proves the page looked this way at or before that time.