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

off by default; remembered for future views
captured2026-09-03T20:20:05.800Z
manifest sha256c0de1acc802a09f9ebc4789939abdbd3d42182093b8a0082981d190135c4d16e
html sha256e80cd75230ba7d9ba7ffa8fc8937317fdd5bf455f2515b9eb458b549cc4db772
proof⛓ timestamped on-chain
txidce728326e62ce6b12e17b0efe41513cb120cff42441f7fc40a455a2544a57f7e
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 965,175 · 9,594 confirmations
SPV proof & how to re-verify it yourself
block height965175
block merkle rootd67af53eecaab07409cc4f2c2892ca079d79785dfc2db6ae38cd4752e08d0bd2
tx index494
branch (11)a4d6f28333dc4daddb651491d7f2f969b5f6914de65220939bdb81f8dc2d84db b87c69c4068751d437944dad4a059523d7f769c33aad321d6102d7e659fac379 2423b144aa4b84d2c2a72fb1c73c132833bb205f933868bf094e46f496e8c119 348c41b42fb2f9f38bfccdf4ad8455bad55a6f0e024c95fab0b823f8b1ab330d d9459f1afa3ec3339a9789cd7bbdb80da371bc0b833fe73685ffa1f091fe84bc 499054b38d4c0136d08a29c36f24a61bd7597144416436ad425fc062e49196b1 0e495d1f7ec9549c296a7c28dd7702df7c5b3f4f02577632b07d0052c7b56b4a b729d3ce84a0a3f24cb7bdc26eac5f7caade64b00a7891f9f0703b73730a52ce f4ee2c891523bc9f6a901a9e73cfa0567a9b1b082aeffe86add9527ba501921d 7b7c04070f0d097e203bd86d024738b2ba67b79b888b2da922938eb0b9ab8acd 65cd311d330336eff7b45f510a16edbc69b81306429e8a2130eca855a9403e04

Trust 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 965175 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).

keep your copybsv.cx stores this snapshot as a convenience and does not guarantee to host it forever. Download your own copy now — with it you can prove this timestamp yourself, indefinitely, without depending on us.

⬇ page HTML · manifest JSON

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 c0de1acc802a09f9ebc4789939abdbd3d42182093b8a0082981d190135c4d16e; it binds the URL, capture time, and the HTML hash. The linked transaction's OP_RETURN carries bsv.cx / web1 / c0de1acc802a09f9ebc4789939abdbd3d42182093b8a0082981d190135c4d16e, and the block's timestamp proves the page looked this way at or before that time.

Other captures of this URL (185)

← back to bsv.cx · JSON · saved HTML · ⚠ Report