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
7b0e77bb76fedf3170543a6cecde32e5206699247e8646d8bc2aebca714065b6
04661b7bf169ae777133dd8f115996301a792996ab82b0504ec9bbe7a5242ee2
843cc07e079dbb545f987744bc9830a693533fb45931b631fe43945f1a987df8
2e7980ed911462b9163a80b8eed7f87ba1b49ebe73abe982103d6e54fea2c080
36d8ec6da44591b17eb5ef69ca954812597a19ca2ba4d9daddfce487feb8ee4a
0091200bb8bf73f41a77684f05b2e21bb13775d6e0114a59e7da78f3cf1d7067
aebe3e70d7836febf21f1b413a086cbcafa4ce530e373fb3e0f6f447982bce43
c447cb8182c92ac121f6c6c89565cbf9d2fcba14b97d3345a4eb44c7dd31f98c
0f57ae8faac6225ce9934b5755d633e265ad53cd010974fa1700bb18a6a69059
ed31941d4f95fe3160cb8835ae28e6c592a814bdfb602fd95c190fa8e8a46a4a
a7fe485eb49e1c395df0c7c0b721fca877b0ad0682fd8eeaf95a10790ac4aa93
b22735602e37589662430ffc9388b55c029cabe7b0af42118324a483b28b29f9
1c07addbfcb15bb49d637c1e8defca597c891d0115c939e8d889463d050312aaTrust 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 970992 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 09305d35ecfc74f09dd3216991e6a09759c09fcb4296268043fd52765074e788; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 09305d35ecfc74f09dd3216991e6a09759c09fcb4296268043fd52765074e788, and the block's
timestamp proves the page looked this way at or before that time.