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-16T12:20:05.191Z
manifest sha25601380b1972ed0685663c1a3c73337db482ad16ef085710d07b5e46bf3371c0c6
screenshot sha2562127c77b74c39e78e07ad14f2c4e9e8cf8771d13a37c216693e76c4d72a2264d
html sha25660b93a46ff591f6966a1e326d68a9f962af61beb2e7775674458339d5492034a
proof⛓ timestamped on-chain
txid275ce3f5c893e1b02ec89fc576b736775578eb27ba659312dcfa5a8325d7d434
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 962,572 · 12,197 confirmations
SPV proof & how to re-verify it yourself
block height962572
block merkle root2baddbcda83b7b7b0341126b4a367f869e6bd14fcb94cf0644c6c5c88853a0f0
tx index193
branch (9)ea71bbb8905cee55de769d0e1239c52e8d9675108101345fa98f015cbedac16c db432197fba8711734b5d41d20cbe231400696f93a89ee9849907db617332a95 e8fe7c19a3998af17ef06205d222c64282efab90c3a7a6be6660f079c3829610 6ef1d619c121354299773b5345acacc6de32dae2a40137ca373651eecbe96fb2 8dc7c063cc0017ff99eff654cd55a7bf36e0e1cc22521f52fbb2ef77231c105f fd3655d006c3cf4e167d963c7da241cffccb174364ae38e3346718ec21fb1967 5130ed2d6d9cfca41a58c12499b73027c83f5bddb78364b02ab316dd11e4dd0b 02fc6d5b31dc1dccdb93c8de46513cdcb74116c2d2382f185a4be43f83a71edf 5e0c1f011e41090c2902615ca84246b957026b63966091cf22069f3c828d8687

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