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
3587a094a1d0da3a6453b81ff0a5a1dbe028e3d57d70245d308e107629490d94
c13aebecdaed96db401d23a21ca0f2ba84553b280af4cbc4eee2b446308fcc14
cc253e1e97d4ecfdfd7e87f8a239c844b4c79704b1c392819f79e9032ebb21e3
9e4af423bd8e39a0397597ecd0dba422b513fd73a02f694f2a8784597d0cf92f
ec998ef8924134e9b4b882948bfd0c2760e259433efcabd9ab1ba38b1d22c544
67db588bdd0ad933baa96c615f8c353f1cffd35503d53286a5ce3e31ce1d5e8f
1853e1cf19f131b8187c7209e0d0ef40424e5e5bca2cfee7f81ee72c405ba826
27a6958087b3b3e09b82821e2ed5ab7c9c7cca4ee64a008c1ff84919e1b40278
b5c8b7b35aacd63acb7a866c07a812f32de2f61c1ca42d9037ee5d45dfe3d791
309a4489062e61d6acc4bb63f8533cf5a563b9ffb68a12068c3f0ca544613486
56318311f130d86985a535a9cc798a63319932e0fa770505f8ff28525da33606
80775168e318b122169ce4cbd26aef6dc259f00ba2d468a2a75186671c5c7e80
cbda2deb671abfdec06a4ded917f34736546ebb8da404453e7bb4808f4e71223
92ee116961fe48eff0e758b8136bc8e4cd4e1d3b5c5f26d2721759084e3b8c4a
8baae53116c428007578ed052787818a9542ae4e089e99685427273db8561f36
82826a32da763081849e1933d2305409bee617db2d462717833a5fb9af09f712
9cbc4ad42e53743f8d0d3fc4e30d9239e014082037be672c01a88d8f7fadfea1
2144e545b84678b544dfed72945927541d5a3aee14d7a615ecdea68b8469a9a4
dbf1cb20f25609a802a4a97a70a5e33ef9b0c32352e347b7fa569075f3dcf5aaTrust 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 964762 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 fa783c4769e79ee4ca6d7481b931282e7b14c7adca2c27148a5ab9a3008953e3; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / fa783c4769e79ee4ca6d7481b931282e7b14c7adca2c27148a5ab9a3008953e3, and the block's
timestamp proves the page looked this way at or before that time.