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
2243f30e44a6bcf829ddc915944eb967ac984eaea62cd1f60855bcc0c1a410be
a22df8027d9405d72f1ce73232ce91a8700a090677b46c5136b41dea5b54ebce
b1eb51ab2748f6de1cb688cdf63fc577357d35d7f566a348bf4b87ecf87958d0
ce266c169bf7a5d89fecf04ab008988ab1e2daad9ab69626cb6c59befd5953c3
634c92790804d2b1a32ea08b8df4c29d1b6f6f15351c4003c027894f104cd337
c917b3de508f02ea1cb9db33a108a89df57b463466510bd51127bb42d01163a4
04a69b7ba615f08df2caf3178fa4f938c43dc7ccda8cdc33abbc2e17a326f178
19f1c68a6067ce877c359331226cf0855ab6b40508ec1b43daa0578034442793
1f9a2d3ec16dabf2b7f79de79515e6acaedcd6fa346028c9263bfd2ae0b0fc77
6c83b33727f3657fc9390ec2942253b2f2829ff2332f877ad20bf6afcc2a565d
40ce5805f6d6ea51fdc43086da7624f03a259f493796b08a493608f9950f6c4a
f973c66e645ba63eced15f770d1514324ea37c55153c161935e544deab0e11a9
2d979fc9c0057ef81d9bbb7000c5078527f00a5cf91871fe2cf2a15d4d003495
44954ec9ff10addc5e7e4e91e73462738c6414444cf2f6dbdcbd8d4110029e41Trust 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 967610 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 da18dfedaabb95d34bf0be63b3913475b13ba52a9950f1b30ccbd8c15ec226af; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / da18dfedaabb95d34bf0be63b3913475b13ba52a9950f1b30ccbd8c15ec226af, and the block's
timestamp proves the page looked this way at or before that time.