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-25T12:20:08.391Z
manifest sha256dd404bf53af117c554b4d9ba87630886f636dd8dafec1ab0d233b9c0704c3645
screenshot sha2567690736f43eed0a92070907fdee2935e239d53f88c9bc371df15ab38672c517d
html sha256b0ff0476379251b5679c888e42cbee84e22b433611fc81ddfef98a8a736716ce
proof⛓ timestamped on-chain
txid2b3f9027991dbc16843d953f8a6949d6aa0dc3cad1550549f5ae943a1d53f316
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 963,845 · 10,924 confirmations
SPV proof & how to re-verify it yourself
block height963845
block merkle rootd254ec94fc74314f48ad91587057a55daf6088b81783417cc62f83c9bee02371
tx index471
branch (10)4045952a70786339a98da184e448db14b1c7779d4ee35ff4163484fa3b02ca32 595eb8a5c62d9ffd16357e5718454cba91283ded13d28569bfa0e6a5b1990ae6 989a5cf64b80a83cdceaebec5605c7c49f0fd45de345d6de677ae6e0dcfde812 59c0d29fec4659a7a70837985c29dc9899352f76dedcaf9b7626a501420ba94a d17f4498bfe2a2b98e6f76892c5043dad969f7cf0fff98a48947aca74ca21631 7368b88336265a28505f3a7da84e5ad29219883833c2dbdc18199d726cba684f a7019c79d38c15460956d38ec8cc2f9eb8f8adb01410e2c4b07e443dbc8a54af 940e4441d281a0d83c5a2a118d95864a01b7b9d99f25ec84714c907b8f4b5397 04cdf036e7a0d35fef085bbb21ff6413676904d189e6d7863273f2541c460c22 e7b66a09d312e75054cf22c37c2cc4d7449541832368ee0b37ba06c21f486495

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