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-10T16:20:06.016Z
manifest sha2568b44459bc6f704db5e6e1c1ca71db23cd098143489fc9fdd94c078f2d2ed18d0
html sha256af566e402bee34d5252d2811cb3b5f4943580acf7e9bf6003ff34be0b695e13c
proof⛓ timestamped on-chain
txid280cf519edb8b4641ca90a315de5cf618f134f2e2f14515af9b93340e06f5151
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 966,160 · 8,609 confirmations
SPV proof & how to re-verify it yourself
block height966160
block merkle root57e3ec8a1d09cafa0505280a8045342e63a1c343293a8d4c0a3ad48ea3624e2f
tx index1941
branch (13)672bb214ef49bf883677766544004fd6c43606ceff3d78469a9efd7d42ceb84a 4d3ce60821908d72297725b305d5b2e5bbecd999186285122e6d1f7f21e713e5 17f0ae235801ace05853d2b7dc54a6d2b2babf078caad44cf57c50fc781eac72 d770308990472d13d8cd092063d81ea05011c5f7f3e06ac0dc3f977c2228ce93 e852b0698d2d3e4dbd615899bfe5cfcb9819bf5f5fcf688df8b9b7d7ede92950 2747238e512fc467c4ff1c79107696f04d174972323f9e7f4811bfdf024eb907 1b7d171a204d93e39321ad299eaee62df1b85b87be1d18e32a8291a59cab18db e5e0215c1e3b2ab6d72488e52bc22c79bda1e014e4c8e580a932c0d447a02731 5967a0e65c292aa2ed215c4f28bce726cd18eb42bd1493844e951f8f249f324b 43aab6917af344f050777310c94456c35b6f2822f78b0c0e52154d0c56b88ade bf2d6485ca7858b98e0d4c810b5f0fe29bc61890fdc8e2494845fe9be302968a 91f4a62df3d878de09815b42bf599ef998389fe3bbe35d13f7ba8aabe7055083 36cebaaa8aa954ff8599a1c1675331af8430b5b962e0062821a7e898bade3bfe

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