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
df05cb00f8c5ce77ee1987610fe77e9545a840a57fdbee2d6bcdb91ab85ad019
abda796b450c7d9d7e9d79e4f78a1d7991717ea17c013cffb86548b44354efc3
bb5a91ac7b84fb5897dbfa4caaf7d2a61e096fea1ff24e439c306405cf23152a
313070a4d58b91646db93d43f21626073996545d9748711db366e23b79d712e3
ae4f7d2d8ede20203df188868fd81c951e800e3cbb681de499dd1d6eec282d4d
f83b6fdf240353cf0d2d30141379e2e8bf8c9ed9270f8a43699c2cd06a948af4
2eccc75792f3561900136dc676092765baf89415df3fbcc3d91c313d88994727
87a8bdb6bba43849f41b730b126b800ab4b4b7f3c1cffaca2657a9f9066e0a3b
c077d4b5cf941a0b4669fb02365c253c65160f6581e044e6911e636f4db87092
02d220e0e3bb26b73d76af0fbcb518fba927a01f8d9a440802d18bfb3cab9011
d964710fcad40a1bb0510c48af0fae2b44620bd2f6a1706a4ae3055fbb3a7363
2b76c29e970701895576692870ab2051e2dd79b313d9ae935af14fb79a653b1f
a094540241cb4005127ffafb3b11d30b7ffc306fa640aeb117ca447724b8b70c
1f0853eaf4f7ddcb15b117cbb0982f0cf68dce185678d97369fddb5f4d8b74c7Trust 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 962712 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 c59039acdf0bbd81cb01e2933033ff65a8c6ef0d1f2e55a1144214c79df1ac34; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / c59039acdf0bbd81cb01e2933033ff65a8c6ef0d1f2e55a1144214c79df1ac34, and the block's
timestamp proves the page looked this way at or before that time.