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
9f2c0fdf1ee987ef2e8d8292e59eefb0346742367cd259e5615c7cb6f83df911
b5ec3111c46f302f3ccb1c83faf71c4b6aa6bcc76d087e6028042e2b505b9b64
dc5891babd333c753f23428434028d386f74eab97376328ebea4d5b803fde650
f5f91314fe34f6a3b64e59bb3ffb03386c44b4d76090fce64b6c8c0f7b547c4e
0e2bf07e44ddbf28c2825321709116c2b196d8eab24a9812d37b56c836d92257
ddb90a2104bae28847850b2a39bbe20cdfa6a36877284184a5c60cc4e061ab97
abfdf39da89ef575b9fd36273531980423ec7224f596cb92296bf3039142814d
fbb21b41dd12d111d3e1da4e8a8e0f2128cd69ccde523788161e9e9c429b183c
2416f87ad9435838cffb96e1b590329f9ced2e5b7b6b9aeab1b23d264daf3ce9
e98f625ff7ef60ac3a9abe2397ba851cbd51fb71e3ffbef0c069b9388e7d735c
188d3e1bdaac33518a463d3d0dab3e887d068e21c0fe8f9212eb8016fbe4f8f7Trust 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 972592 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 f9b5517620eaeaaadcd4e3ecd584f90b63420e80cd8f1ed4824ae88d5fdb37ca; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / f9b5517620eaeaaadcd4e3ecd584f90b63420e80cd8f1ed4824ae88d5fdb37ca, and the block's
timestamp proves the page looked this way at or before that time.