Web-page notarized
A tamper-evident timestamp of a page's content. Verify any proof — 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
d9e66b1d8c5e964c6dada85a44df51979ef414e9d4b6b0810c812dc92ba3798a
ae8c3bb3b1ef407e6148d8fd3d5a2c6a25a7d4094248f1a227287519839e4704
a9b3a9523b7249591344900d2f7b9ee65196efd1a3d07f63f19b6cf9fdcb6031
b3a4a8c289c2650def86d782f84127a23580e02b69b46dee5e1babd858c9f5da
c88d99d746421264e1bce4418c07887efd9c648348e8691a8677a3653f589aa8
00c5a031088aad27afbdb5f6e0ee417e9d36217c7154cc330a35be6c6bf9109f
f4973e7284b3c3755fdca0d255a1d8f70e67cc60fc439580e8ca28cc102dcb63
ca8c83bde5fa312ff91f686b2bddda1c70a386b7c01ad1f149850afe365f8691
350e2276a2b634ae397db7905144a5690a3f39eacdbe5293edc03ccc115d99e3
e7326d66829d991a83c3b5f751da7da7889522f1c9e799df2b4d55d8b579712c
db81bf04bed3a903688cb4aaf305ae487ec6a8d43c08d623aa76d82702d52511
66a856f7dc1f747c4aece72244c57445f3d40e4982bd12e2fda0e978d4d9f719Trust 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 964349 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 46c3ff78057f31547476a0ae8576a85375eb1d1b4d7ad47c40f47794188e31f7; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 46c3ff78057f31547476a0ae8576a85375eb1d1b4d7ad47c40f47794188e31f7, and the block's
timestamp proves the page looked this way at or before that time.