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
d804510743175f255ec76c7bd921f89e39b96682e54d831b5b035da54ac2fea5
bf8f53e9ae5f5372195d110dc512ccc098e469f2f043168b2ff13c5e7b78547b
0c234f138cb2a5205421c8ebc50c06fc61b49d9227b172c9a311bb18d9ffd45f
0dfd55684e96e510e070d03f6593d3598a51fd4b06e29b64839b4b69ef26bec2
e7571732ced3cc193c413e0a032efa5a1fc5c37b79d5e73004419cfa4d0a5b36
f0a707f4e7dee213b50c42c951a60828841d85b0b9c373d22943ec814dc6b3de
d769cd0afa288f4fc1efa13289ac94ee074618a49c90efdf89e2e5f113359fa1
f2f1ccf4890b89f18631ca52f59c5b0594c4a5e74cd7c59e3938e9007041ceed
88991e37139a04253258091fbad610d67e160b18e9281530079976e874983701
66b18f1f0cd0859f67e8b8f50e147908101f8334657116f1e6e2f3e482f5fa7e
*
52fa17d9e17f2e5c044e1b158fbadc0a643fa2390443c7ae0df27b06624413a4Trust 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 970497 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 450293371592b1c5363c5ee7b77dc60fcbd1faa1caa4d66b3dd36210e1db4b65; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 450293371592b1c5363c5ee7b77dc60fcbd1faa1caa4d66b3dd36210e1db4b65, and the block's
timestamp proves the page looked this way at or before that time.