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
46aaa3ffafed70d8de6632a3e794ae1700f3faaa9b31747ce63e40ed9d8bf89f
3c92e07d4f20a286fd43867ffecd99a08b7b5cdfe7eb794ad8a293210441c7bb
f3b5b8c8bd1de9228ef5f34d2889e3cc9fa26c749073cae1b508cb9b0bb2c465
1295993bdd539d7d3d1bbea43ba7002c7e0ee54590ff5f94db820e0037d6dbfc
ae86d6dd67511942f774f2facc62018213e7b4adfe327fddd7acaaf70a4b584d
1189b14547892b6de7b1e4dd88e3f7c24db4d7396f0b8161f4b025e7a5c02b71
313a86bb15c1b09e1550f058561aa501feffcaed7991bdf0fa7ab9768ea7285b
139468a1a077442ffb3bf225e46ee38b412b52ff015f4f125ca545c5531a3feb
38931b2e941b8394a425b8e0cb1b30c8a77660ab7087c21885854a446c8adce2
f498d21837dd2ed6891f328c3f8345f55e911fbd13f0c751e63cc224529517c7
f457ab37dabe64d0b2ea3e9539839c29c95e29c1274fcb73269f80af77b0c3ad
12d9b62b7d3c4625a69528fe89a074cbe31165c6d7134ddfcd7681069fd2f8ff
004796ed744f9d769642b8a1784149b479a55f49891a09b1cf972cb021a57687
1e4fcb3dc199eb3c6aec8a08f19e3f7b101f80735337ad4c34376b2f201cd6d8
d27162f90e3945437a182423c8364790af2e94bf57dbe9dc5a456a39e18cc552Trust 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 965041 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 86caeea7213d323f8e8176da4ae521827a039c9d99c075ffbb3dbe767c331cb9; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 86caeea7213d323f8e8176da4ae521827a039c9d99c075ffbb3dbe767c331cb9, and the block's
timestamp proves the page looked this way at or before that time.