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
76109e154b14d6caeaf3d4dcaf40f370d91bc1c5277afadaa0dffea148fd8d9c
34bff84ddc36f73097addeef82a0919d60d977b465f2b992a7037f01838c42c1
8d01b1bc15d6e7c56c4bb85581c023a58e305d8b0bf66d40029dfcc2fd35745a
81d66891abc4d44e3b2de936b7b5a2681478c5fe0fb0bb027d4d6a32dd54eb3c
4b1f70e19e8ac5e8844666f6e1723ca55471aac95e04d401754f5c182a26051a
8c1f6baff28073ed829c704f1f605e99148400c0f77ceae8d5e6a1c958c665d8
7dbb29fd15e2d0cf87a4ac260dad0a2aa8c02b8a96337a29f0fa9d6f37ae10bd
f971f28a2a1e1c7899d85ce2f80925b3117f1775b5da8e5e1bb70c783ad1f093
88132f657d9177b6d2473a82f6d929927cf3af2488080c2d9775d70814207250
d5ac5753a319ffea92929bb5db8b4539f770d0c63338e942af24380c94897789
09f3d1dc0fe492c0e44ef6f621ecb03f0b41265edb74a61ad28bad3aba409926
3502e9a860ef00db43898a18081acccd1ce23fb3adcf282ff0d2e23e7ed37b9bTrust 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 969754 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 18b2e2e7551694d5a890eb5134a7d78b5ed94380376dd82dea5915e20666930f; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 18b2e2e7551694d5a890eb5134a7d78b5ed94380376dd82dea5915e20666930f, and the block's
timestamp proves the page looked this way at or before that time.