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
7577ddb7a865abe367f2845189da5b4b80c1ce2ad973c20f33e9dcc29d62d3d5
a85955160e0bd0c053980400eb94b6814d1382012b6164b0f5d46cd0d5111de3
d0b3c24de9782a3ad54130903cec728ca10caac867d4a4bc431fb4bf40d28b63
41a29241527e8b0bbdbc741e28833f52130a84a008b3a0157e629a48a0b89863
ec89037ac407bb9b12942c12676b8caa6566f9c08af7473a9d90885a95102c42
8c65430ea2714a56ddb27a37e6565c0504f8247abcb2d29ab95dc3875cbc60dc
6bc98cf2f80b86801da14f142a477fb5c49494c5c340f1b1fb1327b9bb3d1d1a
471a1b3d93d21b6010c03d865b4c8bcab23ffaddf9b727de51ad04327e7ecff4
b7b20c4cf102bbe73dc7730bbecb645f23cea196de74c15a3118554c9aee3d6b
584ed68d4364b12539041456a6555d732f7f5fd6ab194407fc2751d1df5d07a2
059b52ef838639868530f2d8d33ea3abca65fbdd0028d961da44c43e2f4a0c0f
a15bdd22464fa8af78970d3b525f20b0f4adea45c132e1fe057e918afa372ddd
be4bef9635e777120ec3f033fd4d81dcb3187ef51145059c324c94b68355ef4e
2efe8fc843c12dce09ff581a74ce720bb7f588b019d6e94cd6f03a6963824ec5Trust 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 962748 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 b017b113b25639a4b14de76ad23cb1c928dc4e25de31353651b418213c3cf5ae; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / b017b113b25639a4b14de76ad23cb1c928dc4e25de31353651b418213c3cf5ae, and the block's
timestamp proves the page looked this way at or before that time.