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-21T08:20:05.428Z
manifest sha256b0cfc8ff7fa0fc8ea676824a6137d5b03b9ada314fd07ae9493e8ff44def96ce
screenshot sha2567690736f43eed0a92070907fdee2935e239d53f88c9bc371df15ab38672c517d
html sha256b0ff0476379251b5679c888e42cbee84e22b433611fc81ddfef98a8a736716ce
proof⛓ timestamped on-chain
txide05cacce8da44be5c27392ae0926ca94f1a35beea5ad1e3738a9f600600e7663
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 963,248 · 11,521 confirmations
SPV proof & how to re-verify it yourself
block height963248
block merkle roota88774a2abc2b0ec70ad3af69b66cfbf1c75956401545c56309f8052e7574a32
tx index41
branch (8)abf7aeffbb066032424ec3afdf098606ad799b59b6ef2fb29cb3a62f5e573059 1b8d5d54067837c19cf2b20cc7f431b1b755a7987b546f0ed54239d7aa0500d2 633ab6f55b59022c47e393c259865e43253fc0b6d0140e79349a57603a1ac494 f241dd0820ec0b22051e3a9ac6855a6f9056007504390fa8d12da3eafe9ada93 f128f881cd10133ae62cac3e78817bb4978d3854d664543b5d44a31f7a4c9bc2 8da5de96090878525691552c05d7e5bb641c8b07d91a6f95857e4c4502b30193 765d75206c3b7bf2a7b57c7d8c0b12e330b749ea1049d4dcb5b66857051717dc b390456c328e0a1e9c923bf1ef34719a99e80d2f423db077b1a7dbc20cc10e99

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