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
8313bc9a82e2cbb0aed8465dfd2bc0bec6c09d79eacb58bc2b99756480f556c5
d5cce062e10bd86531f4769db2f279f1c89a746d23df0a3e9a7cd314f9006e05
0c06f1caec2850a5b965d562f25ef55cfbc4dc42eccd70df671dc85a80521254
bf9f60894643bcb4d86aace0e6a3e76864435c39c953603c6dd1170a256b0ce2
9f6c597de77aef732bad65610bf0c2f5a93f19beb1bf9b7086026829700ac30b
01f16bec6d5ed24cf9d2ff159d2ebd112ccfa66789be6bf0aa2ae3a97b97dadb
251863a9613e9bbe3c779548ff966f363da0bc68f5d3c76422a43408df7f9f33
16c671272b5367ac2840c644af014645ae08bd5516ca7bc66e825b95a005cbb0
64065b7d56a38c049a23e7a6d6565a9abb8c5440e5615dc2c234e22cfdaa20be
7f5146670db8ea0096a569b1262c878a9c23a2d988f7debf7df7a20f640ac7c1
6285021650e199216f1d83c5ac40192043aa72c311519b19ab9490f9f76fdc5fTrust 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 966710 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 e4df3fb65534cb6ce881a9bfe67bd84a859162f987586c37389cc8edba0d4096; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / e4df3fb65534cb6ce881a9bfe67bd84a859162f987586c37389cc8edba0d4096, and the block's
timestamp proves the page looked this way at or before that time.