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-31T04:20:05.774Z
manifest sha256ff55b174aeef99f9a579a44a393db670fc907774dcf056b1dc49e8b4d91c8a50
html sha256d999a04ade54113ce166df20545404bba82b2d8dc86074388bebd25011172254
proof⛓ timestamped on-chain
txid5290d45debce088ee7ed82a0143dc5f914961dc83c626b529f398f1a18038877
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 964,669 · 10,100 confirmations
SPV proof & how to re-verify it yourself
block height964669
block merkle rootba6a89fd91397f7b9df4377a8c9816288f094e7ea98074b6dea7dc8e5b7fbe1f
tx index183
branch (10)8a74db568a9cc0c018a446ece49f82ca12b6ea700b70be402b48781d9f1fa958 de42f3c6aa4761fed929aafd9e742dc506a3b36e07e12c96495220bf273fd016 ec548cc2d13138f1f2bd51629c72eaf53f55d88198539c69217ce780214745b9 3b0940295005bc3745a5f6c6362b26ff2d20a7fe5e0108b287679a13334ae435 51b1bdd9eb316e0206d12224e7861d71e7d70ebde944d62e233fe2aa006511ee 9267791dffc342cac7762a5d8f441e54e6b31727cd5b8089c3b5bcef4531f5dc 8de63270e92d4422a1e70f63be1f04e6268265a8c9945395e42f7a4b94f5add7 a735f769315c0ae5d5af673fa2ee61cfdeeb883edd839ae16e52c3e41718855e 1e5d19143f33e0e6791b12c8e0ec6f9ba541e4ff247110104865d8493205ae59 344b74e58e818d62726b50eeeb0cbac12905bb2202fe4aff512856f70f6ebdc2

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