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-22T12:20:08.965Z
manifest sha25625b929c67e2c511dc1ef4652b5f666b5256c69130a39a488e7c9f5b158f32609
screenshot sha2567690736f43eed0a92070907fdee2935e239d53f88c9bc371df15ab38672c517d
html sha256b0ff0476379251b5679c888e42cbee84e22b433611fc81ddfef98a8a736716ce
proof⛓ timestamped on-chain
txid566c623262813cc3df7f62c6b8ffc9733df2596016ae625747f54858d7f71d06
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 963,415 · 11,354 confirmations
SPV proof & how to re-verify it yourself
block height963415
block merkle rootea2cd4c4604b0f79ccd2831b7727261d9c3aff7884117ac258006c561b7c2836
tx index2450
branch (12)50fdfdedd916e0e90785103f3d809877ea1074bf399d2dc5cd546ae991419e24 d5d1201ee81997327323bae641d02ac726ac519e712406c4d7d11d15f7c6fe55 be8041d2624a6ac588349aae7b3114d6694a1c8753e78330a5481f46d16bfcee 91cd39bda19d62026aa978a24562fc7ccc3f4ff4a79bcfbbd002538f65924c37 67b78480de8e1369d0558d982fb9a77351a34c00cb46b9bb4148b0e7f529b4da 63c9ed1fd3f64b0fd913b1ccf10600dbd732dadfbd416a80a496875609041ab5 0bef3122a21e551d02f020724451ac6ac72707310d53bebea8cb26c57e3e2bbd 8d676a4d4cffb197f61ea9288c5a204f8da9793ff82622adf0b4c0cd47eb847c fdd7f7c81748c3acfe423095c1027a056840a64b376ec7a74541d93d1cd7b912 d992b660373f62ee48fef86b998cafd0cdb25b45d474e02810a5c5724225a316 85ce2c38b0900adc2efd08166fdc0eddaff165ad0913899ffdd12791a333fc27 da3614c8cc4bf0dfa99495611b754d64b96a8a81670ed57d5c251b32e8dc36f2

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