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
captured2026-08-30T08:20:04.534Z
manifest sha256ff0fe33d78a8e21114d14dfec0320f518241bd16541325bdd3df844c6460cc25
html sha256b7092eab01aaf9cb93280f0b328c04a70e513f27e2791ee332349e67b3282057
proof⛓ timestamped on-chain
txid73e1c6d7ed034668fe248fc2d22a1e738420bc08e21245152594244c341dee25
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 964,545 · 10,224 confirmations
SPV proof & how to re-verify it yourself
block height964545
block merkle root5bad7c8e23404a314dd5ee40c5a577e95634f60ed1e0ab564c9260b163739ac4
tx index265
branch (9)e3bbe95c3fdf8f61451c0b3e5b31063ee14302a8d8bbbf47d81c434b21270aa3 52aa83a67feec843402320d668609a3e8b13cbc5b0fb94971bf7c64b878eb3ad 23c7d9e74aa08ac94802ca2d354a4fb555a2b974b42dd7f32830e6a98774a1a3 c74b9f758f05bb781520b90d4a9348873c19d8991b3ad9e704ff839ff719f52e 8a380aa48fde0371cde07784b4641b6873603803d8ad2a85ffb3f624428f950c f76648f4e4663d5adc6dce1c748810520ad4a718cce69909ad25852e13755739 e46f41ef9e1b0657fa17c5a57bfdab805be1d9dc655653bb48816e214c6e564c 755fa1d52a41c13c3058611262859a6a3fc5c7892ea35d2d6c8b4f8cb98a64e0 349ac55b83ca84f9950c3c78766146c75fc3ffe2a2ddb6ec059afa69068f9cbf

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 964545 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 ff0fe33d78a8e21114d14dfec0320f518241bd16541325bdd3df844c6460cc25; it binds the URL, capture time, and the HTML hash. The linked transaction's OP_RETURN carries bsv.cx / web1 / ff0fe33d78a8e21114d14dfec0320f518241bd16541325bdd3df844c6460cc25, 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