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-09-07T08:20:05.487Z
manifest sha25688ad33deda772f6f63f16e9ed573bb72ba860698f09dc42ca0bce5246b9ee990
html sha256e80cd75230ba7d9ba7ffa8fc8937317fdd5bf455f2515b9eb458b549cc4db772
proof⛓ timestamped on-chain
txid4f5ae4fc05278c9920f35ae69e806ac3aec641d202758ce786c6d9dea454357f
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 965,690 · 9,079 confirmations
SPV proof & how to re-verify it yourself
block height965690
block merkle root8442fbd84d39f9d4e2df29e3deeb435dd595ceb2fbcbe69c8124e804156a2321
tx index630
branch (10)3e30b3d09fa37e91cbe44cf661eee05c98f3b7d45e2b26f8607d2e62376a4286 97a09610ef9e101c2f2ccbf2155f9c22c7c8f75904c248852796c7591a10985a ce96be4ff89ce1e872c940d82a63d6eec3021ffdcd65d528a0e8780309115cac bd902d5138c7f965d699b2c02ec5cf75ae05c768cd0fe34b793ded35e274327e 6f051e44486eefe83afb8611a7abbf84b7f1660a77259225c598dc2042ee5aae da5883bd6779bcf0981715627afc164e2320b1099e5ce1dac61afb36afd6a6f1 1c978fb679e5890d2598fe90cb7f6b44858da8b2f9286f0105e79481e8d200ed 5fc68da046d7cf4165c15bc89f87da205ef8a7fa061d1ed49c2bbfe526266704 4b368384b350e3b167b6f289228a3d46160c82216547550caca4d59cb9f257ac 0dadb6ae06fe309241d6e55c38edf3f8b31a3208bc7c95b704fed58e64709765

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