Web-page notarized
A tamper-evident timestamp of a page's content. bsv.cx — verify any Bitcoin proof, trusting no one
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
d5910c2cde126916f6e6996d7e0ed4f923eb62423d2cae28072627061516930e
0294f92b2870d72fde1e113a3f08830425b8051932615e7d6856e43f90ea5faf
9955d3a23c56d5ca546a23b3f6378c7e47cb708643157317ae24c7dc2f2affed
7c1f29d064f21e7835575029fed66c80394cb25627c308dc6db22f96714d4ef0
68d94d057c4a765bb18a1b532baa4a19d9dbf7a1be34c6050f7c27c30e9daa30
58b2a8a4bf57b27fc07610f48e6ba15404184c6df35c7c0307bf3edfde9a23a2
e06317dbef3e5f04bee95469c368b4655a3b421f4d6a738d8db36669b968912f
05a83d2d48de68209284e90c15370fe4f967b31f77258939d7378cc5c711990a
ba1bcd1dcc9386e5e125f69398ff9583422b1091783c6393477027252effe81cTrust 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 963145 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 52cc42e8b1ac216ad2689cf5eede178a51d7241615747a28f6f4cc9608748e59; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 52cc42e8b1ac216ad2689cf5eede178a51d7241615747a28f6f4cc9608748e59, and the block's
timestamp proves the page looked this way at or before that time.