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
6f6fd837cb21531eba77db84059183c63e638106a1b8214a25943c837fdde969
f215473f09e7949ed55a125c88257a94e2f5f763613a417f4962ac8efa13d6ce
d0f5eb4defbc55cd586d3c6f291b21a8ba8a03d9552f12c9f3b7d88cf8c3b779
ee9dc9e836f4e9110eeabf80b3fa6212dd40d76e4b8d7509896f7da44519c9c3
f2a263388bef32a3d9f20d8360721a363ec605ae54246fc2a2f04503ceb8ce4e
4353aee4f5216484dc7388d0101fb02a5b7714d59336c327d5f6a977f41aa257
5dc5756cc12397ba59a69bcbc1119d4a82693d7f93863ef15bcf8de1e6947c99
75e2864a33ce0aa28dc4a8426b4da2dcb8e967f0c3de6ef5e6ce320436a59be6
9cf91edffda687ba296cf83cdfa3e483b1a0e6c36e15ad1432e69047dde849f3
23f7dc7b35e168c7c40fa468696ce21455263e11473d839f4136908f35bec8ac
33157706a9e8fad30eefd6a9bc15cba9675f16c85b230a989e4e61436a503243
3e0e09ca8bb17aefa56857346d61b2fd2acf4153abb65c2fb6efe7f71d9cb2b2
2a873a37abee5d59b080d797bd5e8a4d9dab87af8749bd68d6d3f6288821d015
70ce43c502d24ea456ee69e3e27f6770436d6d9884533a68e13bade036598548
b5203ec8835960d14a71a9f0161bc01f8f179aa67a97fa5a1f2242e041a707b6
3f5a907226e9f297048096903e328d7f3f8054be502295caa01f37d26018ac44
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 1c561d559ef5d307c8f0b747b6ec015c690cf880fccb405bec62c1a8567139d3; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 1c561d559ef5d307c8f0b747b6ec015c690cf880fccb405bec62c1a8567139d3, and the block's
timestamp proves the page looked this way at or before that time.