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
2d37beb1c0005318a2ead2b0d404754457c8ed329e90faa31e17494c8af98c7b
af109ee33fa1c7d9e0858889ae0576c3ee95d26015ccce2448a340af3a3ef658
8918acb9cda55ad04a83963d57dbafeb359131c48bb6672587898028ba00524a
88a9ee1db96d03810724e7c3b2021cdafeb72e9683fdda11846ad9135f35fdc9
40502245e0ce9dff03d5c5272a861a707cb93ad3e78c188a9ab73b1991ffabe1
26933961723c6f7792f820b3f7473d2a0cc344a4d906397954ee44d329b818d5
2e70f9fc2f32ab0a92630dd6ec1265ddb9405d682b71ac0e6eb3f3c50c12134a
3fc26d546206c23d89a8e3523ec5bfb7660733aa9c1c088661afd9aab2892aee
2fd73190a4d6dc9d1093fbe77623d27ab16a37c63780433a1cc694ad8b22bc93
ce910d21939b070bb3319ea713922444eaeac2ac7914fc80d995fa2d81cfeeeb
310c25a4221fea83a45abf887df0223245e8683a016fc36a60a5df1b5a239260
5c9d711093f6d39ec4490e7d715f62cd4e771e2e85a900d4892a7e7c0c648e96Trust 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 965257 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 4f7046f5ba1500b54eab333d5d4f0ee7e6538501e558227cb80a210e56c01f07; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 4f7046f5ba1500b54eab333d5d4f0ee7e6538501e558227cb80a210e56c01f07, and the block's
timestamp proves the page looked this way at or before that time.