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
3eddcc84c594447496dc71e97d68a8fd2e53975278206f41585c250a7dce7dce
6cab29ffc32e39b7fd0a4155b566e6a7424bbc6ed1c848963291adca84a9a84c
da3cdb6e6367063ffa56c73028889cfacae94928cc200906335a0b158b3599f5
5355bc20137c6cb31b769d91823633c2676f775a65cc0596a16ab2928aa27599
aeaff2504985420b45337dd1f742fbc333cd92306f87b77bbac621b216aa7784
aa1d6304f9801e4ada6fb9ae2ec4f7f3c348c31dde4d5077789c3ecd07d23072
d11270850325e18d9cca92ec4917c8ebd40b193bcef82f99241c21280d613666
53fbca1b50b040026e61d22f4aa4d19426c4ddfdf33f8be8470cbe440e24eb40
634899b9f823fd77a67bdc4e71b493645e2584227a6f38e41a6a0366849a9641
7b2c6fbda8b99770c548402cf1cf5c3fe4e0c58d7cae1db2c8211398725ebe8f
3e61e775e3222e1aceea85bda7557167ed7310df5bd118fcaf9d71427adec137
d388d074041d146d6ed23290e56b33591ba7c2b8b512df0363cde0d106ecaf7eTrust 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 972887 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 e2d19973ea52133673eb3474382ad2dbfc029f85b1b29dc45e3a7ac49225c54b; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / e2d19973ea52133673eb3474382ad2dbfc029f85b1b29dc45e3a7ac49225c54b, and the block's
timestamp proves the page looked this way at or before that time.