Your local registry, summarised. Numbers are computed from this browser; the chain height is fetched live.
A bar per day, height = proofs created.
Compute SHA-256 in your browser, anchor the hash on Bitcoin via OpenTimestamps. The original bytes never leave your device.
Waiting for input
Re-supply the original file or text and compare the recomputed hash to the stored proof. Recomputing happens in your browser.
You don't need this site to verify a proof. Anyone with the original file plus the evidence bundle can verify offline:
sha256sum yourfile.pdf
→ recompute the hash on your own machine.
ots verify opentimestamps.ots
→ confirm the Bitcoin attestation against a Bitcoin node.
openssl ts -verify -in proof.tsr -digest <sha256>
→ validate the RFC 3161 token.
Every proof whose write token is stored in this browser. Search to filter; row actions match what you can do per proof.
| Title | Created | Hash | Status | Actions |
|---|
No proofs yet. Use the Certify tab to make your first one.
Recent public proofs. Each row is a confirmed Bitcoin anchor that someone explicitly chose to publish.
No public proofs yet.
Audit log of every event the server recorded for your local proofs — stamp attempts, calendar upgrades, RFC 3161 timestamping, Bitcoin block lookups.
No transactions yet. Create a proof in Certify to start.
Sign in by email to claim your browser proofs and create new ones tied to your account.
No password — we send a one-time link to your email. The link is valid for 15 minutes.
What ProofLedger itself cryptographically confirmed about this proof.
Each row is a cryptographic check we ran ourselves at the moment you opened this page.
Drop the badge anywhere on the web — every embed links back here.
What we do NOT verify ourselves — out of scope of this page's claim.