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
af298150d94ac6849ed2ce5600715741f2a10cb5db24dfa552aed66b5294d662
fdf4b015b1efd4cb637dc176e2944615ab4bf16621f243160250b1acfc41c2e1
5400f8b884e9d5fd6bb0d21dbe975d762362b91d2546b4b9a39c1a7f1621bf4c
cd2f704bdd1ae2e9334b4ce1b90c1f674c5c4fcc6a30b4f81c2962c6fa49b000
be042cbd8998fb3208fb1af8f67fff43aa7f899b2d63079822c8f0b6592fddeb
9b5fcfbe5abe1cbb9d7a38160c0509e2c73939d7a8c8501cced43a14fceebb18
928aa31b8bdb9cdebc32388e3cb3cfb71b437671030ad87d1075379376574e12
e7ce6f5b20c6de41d279c30ce8572bb846de734cd882f76a80135529ecf9e086
239edc4dab0414a903d902220cf02bdc079369d511fa78901d96094b1a7c40f1
f7c9b5784d37587d0a24db29ae44ac1f7af277c21e2ee2080a5e06dad6b27159
65fdc10df97a355cbc41edf3cf7656d854b8300a5d2ee510dfe45d5753fcca47
872f8a6cb44fc2672b0e3e06f63eaf7be40719f3d04e8be06e73a819d37e03d4
1aa5afc192615c7529193c6efb859df219ed6298c1dd869e9e6c8d939002c62b
e65d6b2b80cbf70ae5357fe982fbb1a2c5eab84ff4d71545f5fe0f5f301481e7Trust 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 963730 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 236048ddfd01fcb9a6fb0425643d754ea8aa76ec959628af5097276fec2ca1d3; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 236048ddfd01fcb9a6fb0425643d754ea8aa76ec959628af5097276fec2ca1d3, and the block's
timestamp proves the page looked this way at or before that time.