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

page snapshot

captured2026-08-14T08:20:04.892Z
manifest sha2560ae7a8bcfcc7e9b1d82af2c90c39e7fb78fe603375cf9d96c4c535bb9906083e
screenshot sha2562127c77b74c39e78e07ad14f2c4e9e8cf8771d13a37c216693e76c4d72a2264d
html sha25660b93a46ff591f6966a1e326d68a9f962af61beb2e7775674458339d5492034a
proof⛓ timestamped on-chain
txiddb2e3954799babba1008117395c5e9f0cbbea6ac1e2eeb04c8e869a80b802ceb
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 962,257 · 12,512 confirmations
SPV proof & how to re-verify it yourself
block height962257
block merkle root92c69a03a0c572f4d81a22ed180eaa66d2d5379970e774fca78d3908c58790fd
tx index7
branch (7)3e0e62cc9681ba22e0d59801b86913564dd7faaafc49cc7b1381a3aeb977e63e c76368db5a8d32b6ebde4fdeee64093c404bac6700f10ade4a492344977c848f 221123d25f340b74d8e5f71f49b520e834a74a01e78ce8a4054546471baa79fe d4da5fd8ca63c224c368f810712ffe2384ef2739b383754adccdf937ffd56f6d 77a3cdd2581a4a9e6508cb2afb34a23aa1b08cfdf84cd7d93df04efa62f71b7a 0c4c2428c9e980ea0ea17eb7f5a3413528d5ef01eb99f75a469a3d70b6b04f0f 432c15c629a1deeea3d4bca1646a2368baa4b72af5d363ba7a0012cdaf0ebd30

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 962257 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.

⬇ 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 0ae7a8bcfcc7e9b1d82af2c90c39e7fb78fe603375cf9d96c4c535bb9906083e; it binds the URL, capture time, and the screenshot + HTML hashes. The linked transaction's OP_RETURN carries bsv.cx / web1 / 0ae7a8bcfcc7e9b1d82af2c90c39e7fb78fe603375cf9d96c4c535bb9906083e, 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