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
0909b3a65127b071e9f52aebcde4ad59f4c4457c66ac3acdfe8c272d41cdcbab
7f19f81976e243481d576c94f64f9702fa436f30d86354b07664240129172c87
3420222ec1881c185de23f43518e53fc855d01fbfc8d683325752cb2d8e88468
76e9fd77d54ef9d5c7133cc9a1ffc7ef9693ed4af6cfb40ec54b10b48d2b1d6f
3f54685e0098a310f359476c832874d4d0ed348d3bd0276b5acc60a31e307988
9bd450d82fc3fb6538b86b459a31be6218927b8b480796479db229750375d572
bbf4a387ad6f256d911f7cc7882b95bec2d93b74f3a56cd5d7f8583cfdb12b0f
cef6685f3fb9e178a0f3dc8402580440a5773eb37bbae8b0ece7d195b217b480
a4d8c83a91ae8752c051a1bbaca0d5f88c54fcd335d6493b27792f373de59bcd
44d0da8822f252a71bbe03568f83f7fa19d9d54df7ad3affb228fd3f5cd2b265
08db7a92b6cdb3c9f22b9c676a5a0348f692d732ca4bd657d45cb274d5fbf9e1
438987715747b8ed67346b0b67fc612eba3d869c92aee1bf16b66185d4ce058f
830220bcc429ac35a32b00e2ef34ecee5fe0115eb1f3a4939ad9a86a39e6e1fcTrust 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 962472 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).
⬇ screenshot (PNG) · page HTML · manifest JSON
Save all three. The manifest's SHA-256 is the anchored id, and it binds the screenshot and HTML hashes — 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 2d7f6d6caace6ea58087d3e7b61185b7a8a950604221a143334607fb100dd9eb; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 2d7f6d6caace6ea58087d3e7b61185b7a8a950604221a143334607fb100dd9eb, and the block's
timestamp proves the page looked this way at or before that time.