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
dcc9216ffd128dffe5341a364c49168081f7b8da263bf808ab9ab4acfac6ab30
594d8c58a98033d23eac83464fdebfdfff806c80636e510575f8f249e8b9b8fb
e4ba411a505d5275db2ca4ee1c341e1966fb3d070b2ba7cfb0d4070562e055f7
24443c786d370d927b1aaefa7ef23edc5fa79449b7b99953cfc0b4899017f774
c0ac30deff20362ad69c510cfe4c4fe6c955c5bdac8bbd08e59aeb60c7d0eda1
f69e048877e4a1b0100724acd6fa5146b668f8eb6852d91cdf463c9d8060e904
78ce0a95065376b5b3cabc7ebfa3f2209fb2fa0f1ad426dde3218aac42ba1974
13d336432232900c5fc6ceef7f6264cb945e2d296a0c48f399fa3a24977d9140
9a77040fdfaaa70e216f7f3bf24203e05de52888b8d2f6c16e524b65c973f1ae
22ec6ecb5f05db95235b937f627f7138e873118d3ac81d92f62e9c6032a34364
19743f0d9cdaf15f80c68f2627bf944a7c7d1c958614d8271bb1d2a74d13e80e
182893ca10cd77e76dd4e8381cab9282f9b0c79e10fee4855fc10697beb845efTrust 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 967364 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 ced182e0044576f3ad60617cb617b68de7e0210b3eaea43a35109497bae33c21; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / ced182e0044576f3ad60617cb617b68de7e0210b3eaea43a35109497bae33c21, and the block's
timestamp proves the page looked this way at or before that time.