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
16d3baa45a86d09c27f2bd2786bcdcdac035de82125152b605c2ffc6b0f9265e
9281ae084ad8210ce3fab1c67ec4cc038e83838ccbdd624bbf8229b981f61d5c
3b896635cc1f7daa7f682fbb4ab28cd5c97fad3c9f0c1d2e244fccc0e21b37f8
1d2bffe1e588f98d7ebc58fa8bf0e5294a63bc3b2953e9942b251456f03d758a
0603d9a06445b50de67280156e8d07e909b1baed6717eb065f823ac4f6403c58
ecb740fc13b276815dea3eb42f9107114302d08997e403fe8060e1b2a4fe3c1a
67474e329dce9395644281c0c7ff5c70014fd38de6d5837143c7ce4eb67a9ae8
0402e37a2d884937ab1bdfbdebe4c735ca5d259195c426ae8381fc8469ca5a03
feacb7f89a05a3e8ccf7e56458fea74e390778baafac2fe45554edf7aa6fa1ab
5521ccabc799ce4867c376ecd119872cf269008d73acec62721f78f66bdf8065
fde7da009eee8616155f04eb1b96457465b2782219c42339c480a37d5c01bdd9
83ea916272989e40e8e711e45e1505988321b029b8868ab101aacf71eb11fb70
e7a7fa4db1d859969602262d41ca0ced60d477f1cf2f09d4b5d899c97d27b3b6
77a4e19709a80187a9ceae18dae702d2381eac69fd8a0fb695a8bb5214606bdc
2a1a65b3b4a21465de5ff3f7bd806ea504a93c3bd43500de4129b9f8470b1cfa
f7da1ac847a6925373eb41c9cc32a9138546b46617d95ee895845eaf119cc5fc
c9d88eeca45f323cbccdcab1ff830256e7498dd64e117c83e3fe69b044aeded2Trust 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 965067 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 4f44cbb26a1814910b39d0123cb4bfd8a864ccee561278e602e4d7ba0275df11; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 4f44cbb26a1814910b39d0123cb4bfd8a864ccee561278e602e4d7ba0275df11, and the block's
timestamp proves the page looked this way at or before that time.