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
6345456b684f26ff88e94c3c55b6ada1e8dd476dcd267f817dbdaa5cd42e1d68
e035728ca331613d77d528bceb94dd1bff5c2905802d8b88e9505bb675a390f6
01e1b2fec921975824137eac419b3e951fe8526a7f920559ae70fc3728fb0521
8698a610a17a2e2cd86d7a69d8822670a6b8fc5118243b436958ecaa3f69aeb4
734ce71066717d144ed6630b447fe68d832ac6fafd9c91015556f607816ccb2b
cc338d83b1e39e4cebe1b60abd4dc3091d00e4369f6ba78bec39f38c21a1560d
93880f269d19b6b633a0f6a0c44f12b9eef7f1d833ad0b8a0fdf28d1da1fdc87
4306b25d4bba5caca937cab94592f4eb4762a3921433d1cdad130ab3a42cfbde
01bd1981b59c73204f6739dea2500ebc8b80bb293de3daf309a86339c4edf342
ca8c7f78e37e2ae87ec3204d1345059b1049015ce5f22af1a1191fe6902336f6
272e204f47d01df83a33cfe3d552845dad7cdb54105a63ff328dcdb8cf7c0615
5b826fde339ff138d29dd48d72025995dba28cdfc98f3309d2060efe32d71f64Trust 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 966657 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 751db552d30702ed06eafc2f5969a0b1a2b3c2e376f1569b456530ff0da99183; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 751db552d30702ed06eafc2f5969a0b1a2b3c2e376f1569b456530ff0da99183, and the block's
timestamp proves the page looked this way at or before that time.