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
e0b50f5090459a522cfac61818fb66137f720d0ae5f0275190a97d82aed4bf61
74c1c24720ad7117117cac705164d1908fa105b57267ee04416e0b268ee4c1ce
b9fcc3b334ece7e4cc8175c11ae51b542bc65dd6464d7b669b79d899f709d45d
bde335aeedfe7f17b06d1868f339fa7d3d542afc59776e3417cb643731de7ccf
a10cfdafab49e2a9040ac11884642aa9ab1a86843ddb3f2669881b4ee01299cf
7a1e215ce6a2549f10938c09e84448f5b42e571099a017feba594ee74eddedcb
275c31f38f4c2638235a5a2e5d9a903a55fd17cfe6b294ef692dae740bcc9063
719655f6f0b13f345246a5fc4a148864975daa74bab634530fbf2fcfadc43412
465bb2456bb770ebd3588ddec5021ed87015acd1311610b3a4f8f74506554efcTrust 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 963944 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 ec9971fb43ef54aa7095c3f48b194c014c1a1b769793f6b5744ccf7aad529acd; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / ec9971fb43ef54aa7095c3f48b194c014c1a1b769793f6b5744ccf7aad529acd, and the block's
timestamp proves the page looked this way at or before that time.