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
23e2f4dea56616142a6e80386c0f5e750116d3d98bf1fcbd443d90411bc95ca6
d5725bc753504990015420f2ef1329e2e67abc87eae3c1dcd980dff714ae65f0
9dcd64fe8e0a29813db5d49e8fc09c25fbc54e4fa936c1d43b4bb4cce09c8a3b
ae5377ac92091237535864343a67cc2a8d156dd0764498eb82ccf782d1c57019
bfc7d301ca267f1f976dccdd4fb2dd918c89d2c9a7e7011adbf98a9e6ac4a115
2b00ec15492755b5b1f5573b20722df9c702eae85c036a03b42993415d8f5ded
f4b9e7b890aa8bbffbb314019e5c8542e9b0a0654de4d3c22b2e7cf765a716d9
d3062a7ee846be4ae3251496f5e40ab7f34bc189554398ff7895f31f68516f2e
efcba9e048f8df28f43109494def026619c6e9dcc0ad4682fa3ed0e6271a3e92
7e9006c738788a519ae0019fd416b0f60eaf7b1d08246d207cd77056eebbbdc5
2981b816266f3775b9b3c86225bb89f7103ee7954cc09899c1b8f56b9c4cc08e
10f43614175e18a5422a4e4a98c92c2cafb309093ce72a199a98ec5d96e577ca
9c3988e59e8f9c7e155b589fc9cd7c9ec158fc67ea6ff59ab1452b9bff3c677e
e8d64721a417fb358a1afa1b68c0e3617a6eae87e18c4609b31059f220833daaTrust 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 965759 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 ca98e8e801d98093c5784b8412c9a27b2367f80413cd8ef575712d621c32b957; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / ca98e8e801d98093c5784b8412c9a27b2367f80413cd8ef575712d621c32b957, and the block's
timestamp proves the page looked this way at or before that time.