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-20T08:20:05.474Z
manifest sha256546be300d132e5fa72603b4f94642e7cd74473c61d3c1130f8cc0bb438f33d3d
screenshot sha2562127c77b74c39e78e07ad14f2c4e9e8cf8771d13a37c216693e76c4d72a2264d
html sha2561067e3a5e878b1954c255bd005df7805cbc315a40a53f5a549cd5975d76dc454
proof⛓ timestamped on-chain
txid995889ccad8427d51a240c63b74c8fd1cc3f111c08a7ae5ca54fa77935e6badf
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 963,120 · 11,649 confirmations
SPV proof & how to re-verify it yourself
block height963120
block merkle root6e1bcc5ebec13fb679dffd7d2fcaf113513c5215f1f6e92ec596b1d88dac41d7
tx index52
branch (7)cc67a9af4a0fa8e4d18ec4f3a989636b00c1088a269e5f0e4a0cd32dc4bf8d3c ed4bbc9a72b91fda6ebf14327d5b2c3a6b3ebfd451bcb42a14d28b7c7fb3001a fd0560ec5bfc73430d890d8370a625c5b5e7752cb9f17142fe6fcd5e2fdee896 603af86e5ab3b7d02082dc53f3ad5a92aac5485909f20b820e9e3a1f11287843 5c9ec3e9af2e71e83240965fbda06accd4529722b5b758c3528fc2c4594f52a0 2145cbd3a49b694d2ab77f694628dce47957922cd1f602563e2e2055fdb249db c663074e6c333bd1f11d7fb67accf5c1b9db860988d64a076481a66259848c81

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