Web-page notarized
A tamper-evident timestamp of a page's content. bsv.cx — verify any Bitcoin proof, trusting no one
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
ba9fbb5f3ef8cd2798434c0dea7a997e569f5057e48c5968e4719e6f4086e22a
a5444e279660f05345e66e07b6ec8b40b91d4309607bbb0c8d0f3fad70991539
645f086ba617f287310cdc03fd28c60f7e27b13b8d119999ff119217ad064ff6
5be97a84e10dada3cc84c408c09885748e21297ce1eb7533915dd15861fcea5b
c0d6faf25d1164f3b38af4d9afd9b7d8f6e0ea00405796911d152ed39754a9c7
8391082091ba07301b05d0c48dbf0e059549876317dd532e44e88e257dfdfac3
331333ff9c520ad4c3301cd921743462a31ad6fe1b2d5230c86b644349f681d5
f24bf788d47d797ee4ca83d500825b7ae70655c64886e8503a32e3e124572d8e
e169cbf15380ec1d7a14cb085cb944240a86bd93925c1028bb52c8905a3fcf97
2de8f2028da89f5c1672a476eb40989e22cab21b759867124392362365e95ec1
9445278ec36003045c179dfc621c351b73306ab48d7fb23d0f500ed7d6304aee
9e6b82be43835083ad614d807602832a44a20928917dfd1f0e25f1ea8cdd3d36
b62f25c1a9e26fab6bc22529890a5a59895554785d2340d469b8fc282d4a0e2e
d98b0968992f8b4f77e4c7d817b7cb0177088c8210052136d0243b136921a2a3
a32904596bd0de62c4371d7cae1acf90b63d7284d4899ca1dd743a9a1c68330d
223dd9a89e222f0573053fc6ec5301dbcb249eec009a1aa25c3b46f02128bb93Trust 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 964726 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 41e44f643a82b4102ab0e59ae930fe6b23b01952342be83792b73b85b96620c2; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 41e44f643a82b4102ab0e59ae930fe6b23b01952342be83792b73b85b96620c2, and the block's
timestamp proves the page looked this way at or before that time.