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
3d0363f4c6198fafd41d08360e5c39d8c578f3855f35ec267929987893aa1703
634efb659d6812973a12bdc3d6909cd907fc1fe79ba25e992122a256e3d4578f
6a301e225070403f237526a68fcd03342aa7ca6ed36062aebc3cb3de2ee3ff42
1da476e2d8ec454855eae43c5cb7d2be3fdec67c1c4408dc47eb74fd577bb897
09ffffe82483f72428dab3d5abeb5995d105e653b44e7b818edde8b1fba76cac
52a9e0490ed41a80f9b25780c31fd8e8884aae535b8fa567516275e511051474
b6243a3dc6e46537204ad5055e066ba25fb6249342eeee258ce76c9e4eba223a
023a24843eafb006ee675290e2cdfdcff72599545b4f49293bed054efaddb2b1
73a83916cd3d6e1ef9e9f8cb0c11e10cbc79b283381d7c8b28837895a3f7f4d8
7396a079d63d4be7214d05bac2a6c389f7774f7d5cca05d9f963ec14f11f494d
1cde4383006819c58949d1e6d9c921c5d36db09555f8b2966e775a9ef7f8b113
d6b042d2715872cb1234165014f178ed8d56cabdb2bd4f26617c034941eb99a7Trust 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 962879 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 1d46f361954f757c94a0fade4c47c44ce1f3052222c8da09c8d35a277d804b02; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 1d46f361954f757c94a0fade4c47c44ce1f3052222c8da09c8d35a277d804b02, and the block's
timestamp proves the page looked this way at or before that time.