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-19T12:20:06.237Z
manifest sha25601e3991837137b919c94b678d59d239eca79a0a6cea8f8dfa8ef91d8b6223257
screenshot sha2562127c77b74c39e78e07ad14f2c4e9e8cf8771d13a37c216693e76c4d72a2264d
html sha256eb81f4a853f44042c661e01024febc475c0114cbba3994784f5599e164d28ef3
proof⛓ timestamped on-chain
txidaeb445801f34df2507701ad08bad33ef3d6f3e5defaf2db578de91f1da9af494
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 963,000 · 11,769 confirmations
SPV proof & how to re-verify it yourself
block height963000
block merkle root09f925d41b6c858c2d1033464ec22e134c8f9b25bcf2bb9b279460e188275904
tx index62
branch (8)ff6294123296d9c17a291f091c9b27231e58a7f2cf4802e9a0b03d2f55a0bbdf ce667c5de49f6a156f82c9bd0678e6b4947048cb91ea1638d55d6828c9b157c4 1e03635266a68c6071c078de8603751478fd6d36f1d51d1a19719492a395c4ae e3edea61deeb6e05302c28d0c6bc87ad7bdbcba009a87865f85c299711ce5f10 2374dd3f4bde6855aab1f7709e7f4b170fe0af157fc1760402170418d24863d0 5a4f6b49a255db23f424be49b297bdec9fb73a4e6a2fcf7d0a3ebe7b1c531e4a 3962b1aa0ef843bb68ea66b16778c0ae705fc3351a66b6669152d8c3ac36315d 6f6d64d84f67c863b6c7d2055d5143620862de5f2b2de22200bf4f210b68fa1f

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