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
68c1f1d1fce26e582792e9974b28040921a5d9ec81999e30d149a2e159a48062
c560c57bde479789caeec98a93b828e171ed2eeb172f73d506050d16939ff28a
95be5922f51569578960beb4460738bcc00c6d2c85fcd5cf7dc6cf57dde68cd4
c5734d74ce8fe20d176112656ffe496bc4c7d1a81c2ae125014ff844806901c8
04a39daf9fbddfcc71899b6d6849567003d6363230714b1f4bd9c882cfdabdf8
7d0bc2b38b448779d35634fe3fd4b682f08a7aeff3e1f04248435dd7d909f02b
da3216bfd0256db5ee8ba669c07eabbf750b84895b4c63131f4ec31973c2614d
a1046947ec18a57c2f6582de4b246690e37cdea60126389e74b69057478a7074
2d688de638214b6042d2399bd3250559ae4d4df903ba49a5b88b466e4efc1cd9
678696de7e4c5b339bbc305027660e98ae9541e2095abd50087ed80ab63b5a96
4bae2f47fcdcec7ae9ad1657dbd65571b16388a4d22139f4e7b506cae11af410
f307b4fe5474bb82971c13a6398a7fc57ee526733fb14bd099f127b779effa17
7bcde9b54cb8c59878b459694d7afa2684a2a0a42b9469f686da2dc20fdfed48
cce3d751cb55ca4ac32252477d2beb2d61107e6d5fd775a4384efd62698da0d0
24437289ebbfefeff2d1cc6fad9de50fbe17d353de62843bcfe09caeace2de3cTrust 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 962917 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 353811c3eb69f03cf9d0f493a1ddea06f31facd8a3d61cdc1a0fa38d027a107e; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 353811c3eb69f03cf9d0f493a1ddea06f31facd8a3d61cdc1a0fa38d027a107e, and the block's
timestamp proves the page looked this way at or before that time.