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
ebd6a564264ddbc20fe75c57564ebe0d50ba31700df8c20c8552a697b90ffde1
085a708cfde1e3462ea5605150ac015a9a589629d18018688d781dbcc8859ae0
04a403c58e3b331e52d7fedd08c0df5bfbfa908c5daababfc1044e3bd25b5c53
945bb770141210bbe1c2d61d2a2710b8d484b83fecac7daa8ce3adbc6fa4e1eb
f0370e5054c8ebad927b40bfd65ff874b7b32772934fae919bea8aa0a2b06e67
650cc93aff89917091e3ee758bd4033c1e9b9ea69c703b25b8658dba908be22b
8017f5cb5bcac893f5e90e45b0919b0f6d5b0917da76008f1304f6165fb603c4
68dc83dc069b37f69b46db11094cb5552793a0b986edbf406ee95f24fecb3ba3
4f215e68407eb7708367435936d12dcc4aa30c99d24aa7e9d8d0dad36b4dde4d
fda88b63c6026d27c0575d60ead998b6ff877b4177abac31ad4c0dd46613d9a9
45c6aa0c6d2a1d8daa7b9145ac05fd4bee1c3431d6962217f51e91c1862fd998
1cf8eb340dadfd3b9cac1ae1e1fe061eb73a5cb1a104a428c88cec116a3c27db
2505ec439f2fdfe348ea20d7c6cc2d8f50e326f323d14aaeef819a7f3add585b
f1f5699d66d0b9062b9908db85a817436d12fef5f39936b800c25178e9e3de05
0c476a5091d40edcded245251e4f858ed358ff5af5bf01eb37007c7b958f2f4c
3e8df9f1fa7fa2516b2940ea112769426bcfb544134c178d5214efc458161925
a994ba46d5eb2f5619fd45883e597a5868fa55bf7ee9f6d3dadcbbbe86485709Trust 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 965343 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 a224162d162b82b96b925072ca517ec9abcc9b5dc22e3bab52ba4e8e6e18f47e; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / a224162d162b82b96b925072ca517ec9abcc9b5dc22e3bab52ba4e8e6e18f47e, and the block's
timestamp proves the page looked this way at or before that time.