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
5a0fe4acb8baaa367f318bbb628fb9d80d493b0ab29f25415966fed0192a12f5
9885b76195c0a3c22f13e9ad6542aec8fd445da13832905546f57bf46f9b1871
93c8cb298f6a63518ed208047984078eb08426a53eaef1ce00a7b5a123f0cb1d
8cb709cfdd99a7311c427c8b8298ae12f4069b01db0e7b76c2f206fe6c0ac41b
220a17a9af58e48cca442b3f1ad7dee0d4bde2ffe73bc23be24f8b36840a45cd
cdb46dc5136d426df8e09cecf4f3a5018893824fa5bfb8eda2b7522f287e4d1f
38575f675888589b34cb526c329853f67c3e42f9b977e57969b1133a99f79083
118e36903546a37a06871c7e026a07c61806ee8c0ab24fb375fa40e4f345799e
af858004ae580511e0df28b69edcea8ab1bef7b7adee1591cab2fcde22047948
81684c043722ceb566be39669477954a17a675168f66e777aaa801d6f6f3b48e
ede1e2eab20aa486df8d050863518f92e89dc0d8ae36b4fd1bca1dd3c2537ceb
390d9ec9e167ffa905c0e7c308abe6a8256c98683fc79951930946f8def6d0c5Trust 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 973738 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 bd31d5b72e1b3d7ea73a0ca18cd796cab2fbd9c1d3c35960c5b3b110c7b9a84e; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / bd31d5b72e1b3d7ea73a0ca18cd796cab2fbd9c1d3c35960c5b3b110c7b9a84e, and the block's
timestamp proves the page looked this way at or before that time.