OPERATIONAL anchoring on mainnet · 0/300 anchors this hour no issues in 5h 32m report a problem

🌐 Web-page archiver

Prove what a web page said at a moment in time — we capture a screenshot + HTML on a sandboxed renderer and anchor a hash of it on-chain. The proof is permanent; the stored snapshot is best-effort.

Recently archived — newest first. Search below, or click any to see its proof.

How it works

We capture a screenshot + 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.

manifest{ v, url, capturedAt, screenshotSha256, htmlSha256 }
on-chainOP_RETURN bsv.cx web1 <sha256(manifest)>
POST /w{ "url": "https://…" } → capture + anchor
GET /w/:hashproof (HTML or JSON)
GET /w/:hash/manifestexact bytes whose sha256 is :hash
GET /w/:hash/snapshotstored PNG (?f=html); 410 if removed

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.

← back to bsv.cx