Web-page notarized
A tamper-evident timestamp of a page's content. Pay-per-call — 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
e55aada97ae32a0272b185ef696e8e088537275706996f9e329d502ab368d1a8
ab100f79634aa30630b615cba048273f6dabf0fd4358382144ab269a2b477104
2f2862183cd96861a2c8c661e5df0b619154b2642bd46203c5acce3b8f4be600
cad768cf804d4b9301f764d8f6a659402ae20716985c9598bd3c3f2267368598
b7ce2c1e314019d4064979529b129e51a9c09b500e6b94baaac22c1c5f382954
e12e5a2977d9d34e8920efa1bf046b325d8b73ee1705ec37133f6973a0d44ac1
8d2b86aedc3dc2f242da81549d7dc95208da0b2c8b6bc8f45572ee006d77ccb1
60e1e96e6612c04bcabd99ee8c672e12545314cbf56e3ebb4b961765f2c3293a
d2e387d8feee095368b50b9b2faea861f483b031ed01f8774996017fdad56703
c00b92fe6c34d8d55cb00f1fccacdc80586c735e48f41ae954e340f29e36d6de
0f847ff7095365be2907dbf003bd5c0bcd9e80954c54e77083ee7a2deabde774
7fce73eea769caf8c5e237d54434014a37bc9616d0b14fed8e4b9997da2f5329
49b151cc2478afa5ec5a1e58379b94e3bb58698adb06fea764de30b6ad144b8f
abc5f55659c537d1f3d74ae2c3c7fb05375a40275ca0b7ea411ea74c9efa7253
74eafb59d91113e1619f0c2bb6ac4fdfbaf8cf2202fc933480ebbff4e1f646f8
03cbc7a67ea89109ebf9cfcc47902d31c32af2c1ae62ad061221379c09562005
d2d8ce7b8427ba5a6ce79b332542a79bc377f3c67ebe0b75c5cfcd62883fb9d7
b7b5f20adac8b9709458c540c9d722a50f54ca150a6840ac91bd2310cc4f554c
c132f3d9fddfd093779ca31a1b19f7c967e181c2ef0c4ce6660812e095241324Trust 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 964898 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 15c929f49e77cce3b2f694724b008fd3aadd8b42052ef046e68cd05178e952dd; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 15c929f49e77cce3b2f694724b008fd3aadd8b42052ef046e68cd05178e952dd, and the block's
timestamp proves the page looked this way at or before that time.