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
031f1d8f69afcd0c3edc873ecf32d5adff4a6cda6b6a5a2d4acdf681c6ca73bd
6e0c84c3484ec1cc845f64b1bce9f2632a10e7ab0edc9264d3d981d030f2268f
e93b2d9509c20cf7402078003815e8f56f2d6486015dfe3161a12f10eb4af0da
01eb891f68ed00330da159fd5f029327708de49857170433bb266f6fb5bc823e
3ca2271c5cc28f2e4963f8c54b85e9f0112424879637bc8a2699134862a7b749
a8c8c865f31abdb7583fb119d973f44d2f46d627721616e482b8e4d8ff0babc5
dbed02234a6641f1750a11edaa701034d188f49041cdab45e676efab18d22fce
9a24285c08a960f20c995c51f2f95defeccf4081af7227f71b677d5470aeb702
058423122d903e69f7452190a6f6582ae52ed055ed4de2ec2201e4e4da2e091d
f11a9bc54d98432798f9ef8732cbe96ce1662189b6e4ef5575b518fc9a17828f
9c0563d59f68d282e889f99a0fa30f577f2f33ac90a2862f2958c39c38b4b7be
88d41c5a9400ca3bfe4ed5e99b45efef2423dfd15b3c9a7ecc62c0e1e0d8ca34Trust 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 972938 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 5ad47aebeb0546074f94f4a560ee53299e34e2afd9a3186f49ea07290a82b11a; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 5ad47aebeb0546074f94f4a560ee53299e34e2afd9a3186f49ea07290a82b11a, and the block's
timestamp proves the page looked this way at or before that time.