Daily fingerprints
Every record Call Clearance keeps is sealed to the one before it. At the end of each day (midnight UTC) we publish the last seal of the day here and have it timestamped on the Bitcoin blockchain through OpenTimestamps. After that, no one, including us, can rewrite that day's records without the fingerprint no longer matching.
| Day (UTC) | Last record | Records | Fingerprint (SHA-256) | Published | Files |
|---|---|---|---|---|---|
| 2026-09-27 | ev_4 | 4 | 822d45673653b471b9c049073af3a8557239a7692f547d9c8e6ab14456049b41 | 2026-09-28 | statement · proof |
| 2026-09-26 | ev_4 | 4 | 822d45673653b471b9c049073af3a8557239a7692f547d9c8e6ab14456049b41 | 2026-09-28 | statement · proof |
| 2026-09-25 | ev_4 | 4 | 822d45673653b471b9c049073af3a8557239a7692f547d9c8e6ab14456049b41 | 2026-09-28 | statement · proof |
| 2026-09-24 | ev_4 | 4 | 822d45673653b471b9c049073af3a8557239a7692f547d9c8e6ab14456049b41 | 2026-09-28 | statement · proof |
| 2026-09-23 | ev_4 | 4 | 822d45673653b471b9c049073af3a8557239a7692f547d9c8e6ab14456049b41 | 2026-09-28 | statement · proof |
| 2026-09-22 | ev_4 | 4 | 822d45673653b471b9c049073af3a8557239a7692f547d9c8e6ab14456049b41 | 2026-09-28 | statement · proof |
| 2026-09-21 | ev_1 | 1 | 4e1b134ce174782450a02791eca951c6cb2f212a5c81b7f5f820defb660c98eb | 2026-09-28 | statement · proof |
| 2026-09-20 | ev_1 | 1 | 4e1b134ce174782450a02791eca951c6cb2f212a5c81b7f5f820defb660c98eb | 2026-09-28 | statement · proof |
| 2026-09-19 | ev_1 | 1 | 4e1b134ce174782450a02791eca951c6cb2f212a5c81b7f5f820defb660c98eb | 2026-09-28 | statement · proof |
| 2026-09-18 | ev_1 | 1 | 4e1b134ce174782450a02791eca951c6cb2f212a5c81b7f5f820defb660c98eb | 2026-09-28 | statement · proof |
| 2026-09-17 | ev_1 | 1 | 4e1b134ce174782450a02791eca951c6cb2f212a5c81b7f5f820defb660c98eb | 2026-09-28 | statement · proof |
| 2026-09-16 | ev_1 | 1 | 4e1b134ce174782450a02791eca951c6cb2f212a5c81b7f5f820defb660c98eb | 2026-09-28 | statement · proof |
| 2026-09-15 | ev_1 | 1 | 4e1b134ce174782450a02791eca951c6cb2f212a5c81b7f5f820defb660c98eb | 2026-09-28 | statement · proof |
| 2026-09-14 | ev_1 | 1 | 4e1b134ce174782450a02791eca951c6cb2f212a5c81b7f5f820defb660c98eb | 2026-09-28 | statement · proof |
| 2026-09-13 | ev_1 | 1 | 4e1b134ce174782450a02791eca951c6cb2f212a5c81b7f5f820defb660c98eb | 2026-09-28 | statement · proof |
| 2026-09-12 | ev_1 | 1 | 4e1b134ce174782450a02791eca951c6cb2f212a5c81b7f5f820defb660c98eb | 2026-09-28 | statement · proof |
| 2026-09-11 | ev_1 | 1 | 4e1b134ce174782450a02791eca951c6cb2f212a5c81b7f5f820defb660c98eb | 2026-09-28 | statement · proof |
How to check one yourself
- Download the day's statement and proof into the same folder.
- Run
ots verify callclearance-YYYY-MM-DD.txt.otswith the free OpenTimestamps client, or drop both files on opentimestamps.org. It shows the Bitcoin block that fixed the statement in time. Proofs are complete a few hours after the day closes. - Compare the fingerprint in the statement with the one on the customer's Call Record for any record from that day.
The Published column is the date each fingerprint was first fixed; the proof shows the same thing independently. Days before this page existed were published together when it launched, so their proofs date from that launch, not from the day itself.
Also available as JSON. Fingerprints contain no customer data: they are hashes of hashes.