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
87e8bec1f12410d33a0db1fedebe706d1c4849d4533df5c907f7fcf0e6ae11b1
f6c1c9428bd7d2f816c9b6af6c44eee80392c5c532a54e79132cceb15e68b495
703d62e65fb67fb9d60454447151292000b13a2be0b68a96a5d2f0311123d0f9
5d7e05e3007869cf98daa0485c68e358176ad17690b63d965020186f9a16c85d
f2368dc771d3fa67ae2042cd513bfdf527f5627df938d1b24fb7514960e2b4cd
031a77c6f6497bef1b8d35af606fbbdff06f1e4862c2b28ab622e2de9c982c88
1ae6a50328a84a629368b5f0c525e4f3a23168a6b6f3b31ba546520a7b24c0af
d0935dce9b6425872db415321343a47d3bcddc2d74ef6c667e8bdf12ee124e00
2b6f355f4e14958e5c51dd7b216c2006a21604d39afaab4f57272f46c8c2ce6e
0d4983cdbeb47386b51deac0b9208636af0de5e328d4cd50b8d006b0b07254f5
692ef12b29017ea688c3bb91ebfb1205fb92ae4b6e4ac7a04b8a98e4d98788f2
2791d33bf11c86865fd7042c03ef71137180c79c8d56d14f29abe9cd08a9f0a3Trust 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 963680 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 0dd987b02c91f879696df5988d7d73d54ebe75354b2dce982e92ff2caab8bf2c; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 0dd987b02c91f879696df5988d7d73d54ebe75354b2dce982e92ff2caab8bf2c, and the block's
timestamp proves the page looked this way at or before that time.