Web-page notarized
A tamper-evident timestamp of a page's content. Verify any proof — 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
67e6f0a25f664cb4e41da8ce9492c893829a851cfc98c434fdbe88df19dfe5cd
b43b0ad5c06973180edec2d9be3b09b62df3a0eb7f6c3c43f90b1e0dde6ccefa
845debc00e2fafcc9a0d4e6b18195fa011c084fe5dc3dfd11b28f1d77afac15d
c4a0203062bb24f9d72554a15165ed47695a2ad59c705a43494e46c21e37918c
3015fe5d9ba65c06165d0d5eb2b7595045911b849603a4923478408370f0d811
bd466b49f494d15d54f8469a3d4db24e15eab0f6f02fadba9c3be71aeeb2055d
65b36176671c15636b7cf5ef6edcfc9d9eabf50cfe1454f050a3d3ba1853f5d0
cd839c4923243c4b03d74ebfb947d89af66eca5549ac53cbe8f3ea385ca87b8b
fc2099ab1a99e7d53654c00d465510d185a9eb3aed360591770e325580207aa7
774d449da0f98f5327d74afb27bcb1b25cd41ddb36374edbcec005f5c0bc2f83
52b016148472c4acc7eed2585f14e3967661200b4d984f8df5e687a82cb04ecd
1a428fc2a91e1d5c7435ae6f5bc20835c9bfde92ffba15f24af66674ae6d4529
da36cbb7f7f2042ed1bf43d050fa4b4cfc0d1553f00a244fcc78322744dd7078
b571ddb61f38b0f4c23f328e646611266515b38b9671a485a27af687cc7ff31eTrust 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 962496 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 f3317988c875b87bce7411ca0daf9875493406a8c9a189bb2651834eb25582f5; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / f3317988c875b87bce7411ca0daf9875493406a8c9a189bb2651834eb25582f5, and the block's
timestamp proves the page looked this way at or before that time.