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
4871d2b6077e9b78e7c0135a786ddc14428df0a4ade30aac524ae07a5dd3ba2b
5fe60f1163503b609987c37aca51e1c5dd622da786f8471daaa3428a24edd909
b940e6c38b3d25f055c74d81d575f895fef6a06e6d43bfd61b5a1844a762c4ff
51421d3c4be6e413835505db44a3d291e6ea814d47b63c9fa11158d92a83f322
7c092c3996b2cb0c9f42b151f3fc46f22630d88a9c0a132bd577e42c03d0751d
2523254cdddbfef30797fb22f268f0b2a72059adcc02a846e3a6973663bf9d57
7dcd0a79879774bb44e31c768a6996d4c95f5ba702812bc5cd081243865c7a5c
ae84db0e29e5c2f3e96cb65d95f6efad400b6add2d0085048165f10b37fa5fe6
31a9ff020316aaca5946f1892e98994c6dde330c32777feb3f42db7a51e08923
8ba8b9b358fc0794b47b1041f0d3471eabb19f7ed85addc6ca109ffc45382c66
cbb4e97f8b480a5e43eaa2b9884d122c27a59564135e820d2b2f6549c9441ac6
d343b9e6653ac4e46a2da58fb938d56a085b578af3c53d5db62abebc20968147
ee343abf070a209d5ddb6a67050c29d6c43d15aedbb0444012fe4b43e61a8c75Trust 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 968964 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 4b47861f95f2adedd2ef0dd2f78643542b71128c6ae21e16b5fc387200787466; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 4b47861f95f2adedd2ef0dd2f78643542b71128c6ae21e16b5fc387200787466, and the block's
timestamp proves the page looked this way at or before that time.