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-17T08:20:04.911Z
manifest sha256c7f130bafb0cbd53309d70c0cd2f79e92ec7f136aa94275d2fa2a5071f498fc6
screenshot sha2562127c77b74c39e78e07ad14f2c4e9e8cf8771d13a37c216693e76c4d72a2264d
html sha25660b93a46ff591f6966a1e326d68a9f962af61beb2e7775674458339d5492034a
proof⛓ timestamped on-chain
txid43ff87d1aaf7ab63364a75332eb47ab2b5084b443c06d452418e97a3a1c5cc2e
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 962,695 · 12,074 confirmations
SPV proof & how to re-verify it yourself
block height962695
block merkle root5a60ef1830ec34348aedd689bf2e6cf422dc86f30595dcc4c1b8f1896d4f4d6e
tx index25
branch (8)ebbc163d0fff1aabc64c838096f4a8e86cbc53555399a2894d763b5aa10067aa 242742d479eb2141272d201214c54e7532721801c01d933ba92159c75d02c64c 90bb9508e60b5f73040b9cb4897b8cd2e5818204b63d57c9bba625008a01af95 3b8d3a9e5ba3abc34ab55e5630506d67e5ede52da2474a9ad5991b6bd2dd000a f9c7f2dff49a9008143f3d9210f915a5f1ad6af38efa7c470be74f060aaea413 10aed335248bc0bf66ea9c3bb7bf7826f501e9ccac64ff02ed209418b8c10ecf f1916d8781e09579979c1872b17170c475b53d17e8bdc0ae65092f3b8def2cd9 3c169d59134c9bb09856cd1340d8c0c01517f8253a1e38d6654d1d56f29c7f79

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