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
024d1523458f389fbede53a68aaab65765271dd42384b07add84fc8cb645b792
1126b05da7bd053937408db599d0d22bed7544b3961c64bbb726b01f899bd6d0
8f2a35a03232abf6493ca0436ae8c96844fe1cf57776f840a47fdcce8d702539
25ecf60e9cf0bcce4c39bc830548803254dc730d25a8d1e225fffc2c530db7d5
5fac3465e129371224edfe0bf2ef69f77fdc1b7b6669239239dc89fd948751f6
4b33b0c6d8d66572d0c5f48f5e63326415fcd906af1c41298ec1b56cdd69fed2
d9ccdb05dff786b4e95d2bccec292f806827080016b4d57b9e7e25016c4db845
4d5962fb451d2d8fe83e82855c13654b6dec21e4f07a6396844e9015a21e7263
791671f668bbacf04be28163569baad567e3d44f2c01b4d0945131696b1d8c79
4af75f79f191de58695116bbbd44c7e74e7c31f44fcee0ecb98f67c347175d0cTrust 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 962675 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).
⬇ screenshot (PNG) · page HTML · manifest JSON
Save all three. The manifest's SHA-256 is the anchored id, and it binds the screenshot and HTML hashes — 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 db7c22e1f11174e2bfcaed7f8360c62d44f5e88d64cd2cd3e57b0e366b04ef16; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / db7c22e1f11174e2bfcaed7f8360c62d44f5e88d64cd2cd3e57b0e366b04ef16, and the block's
timestamp proves the page looked this way at or before that time.