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
b865c11a77c0a81ee45734f4a7c6543dc508e18cd889773fdb81429addddd917
9865a3a6cbcbbeb07f2ca6a4aa1ab4707bc95cc1014664fc996b41833c80fab7
1e6669a15063bb483e581e1cc91731b20293556968085d18f102434f8e5c0ffb
b6326ab04cb8533c50b5202ffca53f8cbf17f8143635b18e53398d1375651a5e
8b7bad135fe104a2086c0161c75a29c59f6fe45a69a8cc25f2098a5879f75657
b3f91df5b8f6d3fcd1e93a24ef8fab418d2f736a44179a797f40ebd89810981e
c7f68f66fefe420ee6f9857b8793e2a9142b126ef0d81238c13399ff11a20c34
16ac0486366d820ea5e30fef51f0666eb979fac0f8ffec3057899915df1a3209
70b8edd3b6dea9e786ed3957bb217a74d879047ba86d18f920cc044f7cb5833e
95aa0c3c99579fc9a85db4706aa57af3d9e90bd5bcc41e8ad467334d04baabae
610b77f8c32c35236a5feca4d9b7712f7a40d1459feab0c03e605c2427c8ebc7Trust 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 966116 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 bbf0b92ed0eba1b55b742c8ee263d197349c9a4ec9331b159daddb342f163239; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / bbf0b92ed0eba1b55b742c8ee263d197349c9a4ec9331b159daddb342f163239, and the block's
timestamp proves the page looked this way at or before that time.