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
d30649e01031b89bf964082bb4425e943276a8f9223f38add3fa7e4ed5a4c0be
90771395657c484b78e935006ae610c21b076b282be56cee138f818830017786
3785565cac2ea32b9007af37a2257ec80d7836171c2cbf750ca7e5cafccd4ae2
e9605f06f1bfaf61d7fe42dcdff1e7cf3ba89f288ba64ec818101648f5080390
cb8d59413fb0beee7075d32b709f793d1d69e39fbbd71c5a8ebbb4e328274751
c44d81bed8e021d1d3ddf3d0237e98707de98a147060bb5153143a2d4aa39b18
d67b9a615ebcc62480c77aea1084dd43a13af3743d1ac9550d109cc8aae17805
0358bb82d54e9333fa48775ecb0d5ef26bd98ff93b233d3c2dcec5e14b7e808e
697b209e3ff7f1de1ee8d7616b94a8a03d51edef5bb0b0346c6984e03d96efe8
f3e62b788758d98c37f40b35d3f6d16103e12bfaca2d7c3e19452ab90a431173
6c6b36f576628fdfd2f38f6ffdaf5fe983314e9022a03c63dc5ca2e17a760fd4
27fe6569f22af44664dc28dfe94cf394b71ccb02ba1505f3b0e92f4a7338134d
3792bf27be84fb169463b791ca17925412256e7e4e16279711417a9d03213395
dfad1fb327f7991cc6fc1ac4ea52b9cb2a7c249451f7595765b8203c498f2656
725f0cf027b82dbf56e25a3e2917e96fcfeadfd0a4ff26d08de1a3a9660a631eTrust 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 965106 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 0091cf4315ebec4b99e749507d7a3a236960567a99f5b3be4df16a89333588cf; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 0091cf4315ebec4b99e749507d7a3a236960567a99f5b3be4df16a89333588cf, and the block's
timestamp proves the page looked this way at or before that time.