Web-page notarized

A tamper-evident timestamp of a page's content. Verify any proof — bsv.cx

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
captured2026-09-10T20:20:09.168Z
manifest sha256427ede18422b8d515a6b8972508c91fab19139deede16f43b60cbbdcfac441c0
html sha256c4578212f432b9c4eb9c8a987986027e141677993071211e0f9a874240ac5118
proof⛓ timestamped on-chain
txidc70f52301b196398025c696413ae7da12469a892b18402fb06a0c42434cac7e9
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 966,194 · 8,575 confirmations
SPV proof & how to re-verify it yourself
block height966194
block merkle roota33a64a1ca68523fd9e53c6bb5141b90a82b66fa08c07bcadb96fad7993c944c
tx index985
branch (11)c763c40552e97d9fca2d0ce21d2be0da9766000f3cbb7dbb372624306329d388 dff6893072728767305cb5b662755ab77e88d84a9c769da139c46d3f82ec3257 cefa9c6c34c23e1a7d28bb87e56c7316662676e1bb3c85e2f319d1051d994494 08f27b5c4efa55f18f9f67e2810a144e2402a01ca51371f8da733395d5e7a128 5d3d2964d4559fcf5ae9339d8e251e3954b30e4e006251fe0415bbd6666b227c f5f573666cd1c60321aeb65a1769a6b043742c7373ea5f4342dfc3ad98cd7ef5 54c168e116f3958ecb9284ee7e40e9808c6f9c934479a37e0163bb9686ea1c12 20312abe7c10c56204dcc8385cf4be60f037598db0159aae102b419963ddcb4f 98d916b41be894d1add39f1a6cbabe7024361f7704f491b6b5129606b27c1c3c 2f0017223e7274594ea5c8556dd818268c82e64f6f154b67e3520f186d525e68 c8ab0dea16480d05ce2c080a7584a8a266c264e95d4413425d4f0dea79f1e70e

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 966194 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.

⬇ page HTML · manifest JSON

Save both. The manifest's SHA-256 is the anchored id, and it binds the HTML hash — 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 427ede18422b8d515a6b8972508c91fab19139deede16f43b60cbbdcfac441c0; it binds the URL, capture time, and the HTML hash. The linked transaction's OP_RETURN carries bsv.cx / web1 / 427ede18422b8d515a6b8972508c91fab19139deede16f43b60cbbdcfac441c0, and the block's timestamp proves the page looked this way at or before that time.

Other captures of this URL (179)

← back to bsv.cx · JSON · saved HTML · ⚠ Report