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-22T20:20:06.407Z
manifest sha2560d8b14227640642d0d82c7738af4a0616b472fc8df6a7805b4d0cb187575df1c
screenshot sha2567690736f43eed0a92070907fdee2935e239d53f88c9bc371df15ab38672c517d
html sha256b0ff0476379251b5679c888e42cbee84e22b433611fc81ddfef98a8a736716ce
proof⛓ timestamped on-chain
txid1b6c2de8dddeaa465d09309fb288889bca5a4c6e48e862a7f56ef41664179adc
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 963,454 · 11,315 confirmations
SPV proof & how to re-verify it yourself
block height963454
block merkle root8b9ba8dd40a03c8301c6c68cf1bf66635108948c7a4abe415e802a52ba5299c1
tx index2780
branch (12)58b4348199c08a0ada154e6e33492ecea7a685009e88ce50d4e86061c2c1c2dc b13ce99341629e254bad4ddb07b9a3ba37fffecb7eee7a3772bfea6dd5bff4c3 f7da80f3e8a61887a28e88100852e7f0fffff0c8118494bc9e90a522df01c010 93cc0d4338f701fb0f865b690d5806215978a49c9be68373beb192e81536c753 a9a660e93f80608b02ad2a3a70efeb557f6d1888d01364535241a042caf47dd6 a95372c354b5802987314453df2940669abbcef4aeecac9c8852b5e37081713f f4d4079c6f8f66ee6d385b26035fedea3c0c1c2e49f8841fa85b37b54d4765d6 9c9db3df6eb31e74477d605018bbf7236200d3569e0bbb59a9c2dfdc517844d6 69e983c57128a564a10c891947ab1c4f72db5c2b5138be86d6a595ea234a4fb1 8745ce151c527569dcba0b0a90324b682a17da8153e1fceca447cef3d6517493 55850427fd0b560be956dd1889342f36f256bbde8c8cdd48c6716e10c8ba5e05 fae8d8056aab50af2ad1e4d49070d6436defa21249799cdb0537c504fbdfd0df

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