🌐 Web-page archive

Prove what a web page said at a moment in time. Paste a live URL and we capture its HTML on a sandboxed renderer; paste a Wayback link and we notarize that existing snapshot (carrying its original archive date). Either way a hash is anchored on-chain — the proof is permanent, the stored copy best-effort. Need a visual capture? Use shot1.

You can also archive an X post without leaving X: reply to the post and begin your reply with @DropReceipts (or .@DropReceipts). No command word is needed. We anchor the post's text and its own media by content hash; a quoted post's media rides along, but its words don't, and links are notarized by reference (title + preview, not the linked page itself) — the X-post archiver docs spell out exactly what each post shape binds. Free use is capped at 10 archives per requester per rolling 24 hours; overflow is queued. Those are the 🐦 entries below, each with its own verifiable /x/<hash> page. No account, wallet, or trust in bsv.cx required.

The bsv.cx public archive — live captures 📸, notarized snapshots 🔖, and X posts 🐦. Showing 289–336 of 1151. Search below, or click any to see its proof.

How it works

We capture the page's HTML on a sandboxed renderer, hash a canonical manifest, and anchor just that hash on-chain. The proof is permanent; the stored snapshot is best-effort and can be taken down.

Verify it yourself: fetch /w/<hash>/manifest, recompute its SHA-256, and confirm the anchor's OP_RETURN carries bsv.cx / web1 / <hash>. Each capture is a distinct point-in-time timestamp.

And you don't have to trust an explorer for this, either. bsv.cx runs its own block-headers service, syncing the chain's headers directly over the BSV peer-to-peer network. For every anchor it recomputes the transaction's block Merkle root from an SPV proof and confirms it against those headers before publishing the proof on the record. Look for the green "✓ Independently verified against bsv.cx's own block headers" line on any proof page, open it, and recheck the same proof against any header source you trust — no explorer, and no bsv.cx, in the trust path.

← back to bsv.cx