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
76a265466f56f148a6893f3efc8522acd67b6df4b7e52df73052f316d7506a2a
7ef09c4664ff9cb21fdff41b4de7252234dbaedb063bfaa1c66d66afde1f49da
0b45787adc087e0f788cdd204d6b893c1267183933d96a03aceb2436edd29899
50be02977bdcf8a8dcc3e3f92c45c87e272f1f77d9b2e0fd556bd8d1618197a7
05a8ce8a065f9a4cde333dc86e1cbfbbc59235b14fcd8aaf560bdea84cea1040
e694c95e0139b5591329d9646061f56f249b1fd264498f116562b95abd65934f
2d948376610d2e4f6e2d1df3ffe40cef02c5bbcc8327fc90634889cebbe68a8c
3dea2077c26f5eaa540c9363b6e23baeb6e350c7cbf69933f52353a04477510c
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 65b7ea9a8bc28d631faad36a15a51531fcfde69b4e48f90897f34051836d97dd; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 65b7ea9a8bc28d631faad36a15a51531fcfde69b4e48f90897f34051836d97dd, and the block's
timestamp proves the page looked this way at or before that time.