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
6e4dd8e11ac9456de79d4557d4f44f8172c67a44aa496a5bee5d9a8b035800de
c807e6eb6fb75497a90fa60f61522cad8d71f4dc30c6d3038881ae1f71ecf020
b61a4c70ac9909cc10760983625b1f529f49676f736533568efe025a187bf54d
8b0397eb0e7b1bb75a4a47f6d296c1f9c67ab59f31131892a8ef70177fec9635
dfcd3774257157a46c84207fde8f210f4b85f335cd1baac99162a37b44995e2b
d1435763fa697ef84bf12a97da50d259d9efa90d1be4e867231ace23a8198661
ab0ba45a8867038e1a0d5b678331e7230c3af2ee46a3c9d51cee5561e9c776f8
0788e2a65939d30f4b943eea65cdb3c9081e9b434a822c71ff9d722a4ababd27
5925b1e9e93a3096b2eaeb96bfdae8efe4696588b7de4c670bd887e1343ec745
0886ecb36a7df2a31fe9ea1e42f00b393e61e61ba2bdac6f42704a848afd8165
2e47c3e10991938623faadcaa9143949951f51fb43e9c162f7aa49609053471b
096812ab8f0c3561af0e305bdec2c0af60e99f6d306bddbdc343d08698bde16f
a1c5f80a79a7e57febc3770c04c15b6c9d333b819e87555b04113a4d8276594c
ad9cc685555c92ed20d5db31c5e0d3c1571948a8b07060ffc74a3dda23139c98Trust 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 965784 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 1af46117e0fc5ba48774ac508edb0482d50a4891f38f0c32de5a7ca0795bbcd7; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 1af46117e0fc5ba48774ac508edb0482d50a4891f38f0c32de5a7ca0795bbcd7, and the block's
timestamp proves the page looked this way at or before that time.