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
a258b96bc14a6c9ecd911d20c59f6bf21e3954e5cedcb24f26f52524dd765a00
b04a42fe67bc92612a6c4d45e430720025032a3781026322fab71d7868ad5f5c
a04be05d73950bf5feff8c4dfa7c77c93498b14b510377fe255fe412a7e44a58
a2bca413a4d5866114729427b2e17b1dab89e700795e1b330e1ea82cf56331f5
ef557fff6981f8f7243f7ad7c51f5c927616d7dadc854ee4c401edc31b902f7a
03ba9b3da7a588502d6035d339689d647bef48b79cde50705ce9dbbb04aec865
fffbea960843602b1b6d7b90144d2d6d9b438d1ffdac0817af7b2460ae08add9
03bc7823b74c1abeb858420f0d3fc24490ff652a49676eeed2cf80438ea00a9c
e22149301fb8a119c7cb7b3ea132cc97c5cc2eac267e824d41fb7dd4468fd230
6e58b5a86f669034b299c232972a1d002ec842691e71062cf8abe9ce490c79c8
e1043a48ec1aaedbf3bc9278451664e35f1002e173b7b854afff8f3d6b523c88
b6bbed78dd4f756c07af2379c10fc4e35fc629b6de1273948ed57a512d969d73
b924549b58a133c9d2fa206306146be612548b15fa9b16cf81340f8c131793b7
818b84aa64d8de6e3981dd2bdc4bcb80142a0663dfc6e946b71a80f87ed96266
a44f0e91e341e956c2866e2307a645ab0ec66a3f5fa11930b7da5aabf96c2e6c
0f9d6debbd5b4408f8764ef0560f0bdcf002000731ddad37287c62e95607668f
3a446b9129dc63d89146e78d884d34f4be7a472448bdc4282beead8b9a20fa4c
72df84db0f98004d48b2362bfccdfdc92dd8fa5206a1c7ee838656d00a39fb6e
411f750d3757fb2da5bd8d50a62141c99d3c00d64899ddbd1fdb7dd4c3f55edeTrust 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 965016 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 9cf1fed4dc5f0afce5baa1c8dcaac7a34d2d32e97d08ac7120a113de1fc4c3e5; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 9cf1fed4dc5f0afce5baa1c8dcaac7a34d2d32e97d08ac7120a113de1fc4c3e5, and the block's
timestamp proves the page looked this way at or before that time.