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
1ee8ac42523af095c335d3083bbc52228f43ed5243c2fbf76565b4751d7ae203
b8191050acbd9bf77dec71c0c3ca09d00309ab77737371d11d54b6e8ac416966
3bd43713437318d6d29dcd92c7cb4010fcb9d8ef81381a2e26c710a5c408a828
848ffa5f36aa7be3399d8fddcad4edfd3edf11c1f5fd33476e98ba3adbdf2eb4
34d49213ae76310fa182b832761464223e2f728aaa16cb0af324edf8b6983a8d
e74a18e13897b0e6227e54619ea1163887ff863268e981a35e531a7993355e6b
ec6f2d4062a40fec1e418e7ea4391426395f86443534d92525c235210455bb60
2b578f62298e3864d80c2dcc022f8d1c4564cbd1dcd7fe847253623ed60cfda5
dafe1a9e509b86486fc811ecc8b8da166e97dc2ac3b92abe4b0cfc1790d037b5
be1f1ba18fb16f3848e66793d4719b881f3b264f8779e9fb93ba1b2bf556af44
f80c48c6de0600191a7998c826cc3ef9775719df27ba219b0f2117a499ba4c5d
eb7d2a3374b9bfe165f1614698e353469a5a21a138f212babbd61e23b115d1c3Trust 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 973084 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 be685278c18f2e936599756a8b46d80d1983a497dd115d23796799f31636ccf8; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / be685278c18f2e936599756a8b46d80d1983a497dd115d23796799f31636ccf8, and the block's
timestamp proves the page looked this way at or before that time.