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
e792fc07138822a07a320e3b6c8d37b7d7e951dc0720915093c6a897877fe55a
cd6aa10cad44aaad2b6af38c29711af2fd6772f446f5f6d84832bf159c2cdab5
034db9d6bc78fb78ac52ea692781a61f410703bc051db00350e25e7a0c173b76
72f034a41757f3186f27da35d85255be868ef675f2c8cf2944c5baa68f984c3d
8dc806092d8635ca266a2a805b80d532ad02bd40ddc3239e9d29e8e61675d772
cb2809ad57ec28fb4e006f388d1bc9cc7c5ab6b2d0b5cca737eae74643d3547e
de6f8f62f0f735beacd57bc41f2b48b59620ce1bd4b3f4cf6d824e23cf1afd6e
1d242cd850f387da8b48d92f195b5d39e3693b1960207a1aeede7006a62ee417
8399c8881a66d7d6407dc2fd8a97f99aa8a4b7f79303dceaed2028d44d272cae
52918acca13f026c61d1c4658230bb11a1a9e31766df46ec2e3654434fa8e330
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 3de662d796e4a5641a1d36612b95f095aa0bd17318a1bb341749fc4f9f65dc7b; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 3de662d796e4a5641a1d36612b95f095aa0bd17318a1bb341749fc4f9f65dc7b, and the block's
timestamp proves the page looked this way at or before that time.