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
167cb2d00245407fb1a68a22dd4561c312fecc9a5103528aa6efe25911106514
3cad427eb7c33b4eb4abd26099fd30a533a712e9513aeb4a65e4b6d13c707fa0
372bfe1bd6bf470a7b785d1a8be02fa4693075760f11457d7a2fbf98f40baddb
4acaed64037c45420acf0d081e1643c57824a02e20cf34aef93357a4decc5650
997d58009b98d64c014faf7a471364fbbd385bc4aeeb00f6c2d572a71d9eb466
ce162e2c186c03a19828a6924907c719bb453f63a08fcde31a2c51ae4bce4d5c
bf8770e252bf1e4f8734b77a726fe29a241d829fb1c929e49bb53ad0522fb618
863dea73a04c306514bc7ca031e01491c937adecc577f8879754dea66f38aa6e
6c6aad172fec8bfe9087e927af244a48845c775048916329b0011372cb2b39f4
31f12ee15d45e952a82ce0ba3634314143091d00633677511b62b7e02b1b9322
f76d7947656521d1f6bb560acfadd267c748407fb592b6986af72b6a267130ab
87ec5cb3b60516c5809cb084c64833896b11a140ab8929fc7776b8f75d120e95Trust 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 963187 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 986d153d76e58b7fb00277fc64d7a24bb0d43190842dc50e9c07b3793df5e513; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 986d153d76e58b7fb00277fc64d7a24bb0d43190842dc50e9c07b3793df5e513, and the block's
timestamp proves the page looked this way at or before that time.