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
5f109c90c83abc7f8c983b8a9bf84425b17cfbf7b7f2d37f53c3b747a8b7e82a
9b732d672168ee99f3562518fd38bfd6ed39314df317cfd343f50de1b8ff8315
9f94e40a5165dc1866fcfd023df8ee5bc21ba093f11b07f3137190f58eeec357
2510aa8c2943f596caaef0eba3f97e95a7a9e23241c771463430abced3ece19b
2b1a00dc1e138fe099868357ad8f8d68c9a2ce73a0b66732abb83543b8166f75
f428ecea0c20db8ea52fb52fc6e317e4898cfe723741b76e531bf0009fa623cf
3044829a2503d15e8e32e996fb7acc9ed2be0f75a31389ad7a91332f6bade7bb
6f6d64d84f67c863b6c7d2055d5143620862de5f2b2de22200bf4f210b68fa1fTrust 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 963000 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).
⬇ screenshot (PNG) · page HTML · manifest JSON
Save all three. The manifest's SHA-256 is the anchored id, and it binds the screenshot and HTML hashes — 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 e0836050cec34eabc9758564486282f68399842edf757b74a050574e7ee2b169; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / e0836050cec34eabc9758564486282f68399842edf757b74a050574e7ee2b169, and the block's
timestamp proves the page looked this way at or before that time.