Drafts and the Passport · 3 of 10
Signing keys, the countersignature and the daily anchor
3 min read · checked Oct 30, 2026
A record is only useful if someone else can trust it. Typalog makes your record checkable in three ways, so that neither you nor Typalog could quietly change it later without the change showing.
Your signing key
Each browser you write in makes its own signing key the first time you use it. The private half is created inside the browser and can’t be copied out, not even by Typalog. Only the public half is sent to us. Your key signs each sitting summary as it is written, and signs every certificate you issue.
Because we hold only the public half, Typalog can’t sign as you. A certificate needs your signature, so Typalog could not have issued it alone.
You can see your keys in Settings, under Signing keys. Each one shows its id, which browser it belongs to, and when it was made. The key for the browser you are in is marked this browser.
Typalog’s countersignature
When you issue a certificate, Typalog checks it against the record and then signs it too. Its signature is bound to yours, so neither can be moved onto a different certificate. Someone checking a certificate sees both: Signed by the author’s own key and Signed by Typalog. Two signatures mean neither side could have made the certificate on its own.
The daily anchor
Once a day, shortly after midnight UTC, Typalog gathers everything recorded the day before into a single fingerprint, a short code that changes completely if any piece of it changes. That fingerprint is sent to two independent public services that record when they received it. This is the anchor.
In plain terms: after a day is anchored, the record as it stood that day can’t be altered without the difference being visible, because a copy of its fingerprint sits with services Typalog doesn’t run. The fingerprint contains nothing that identifies you or reveals your text.
Anchoring happens daily, so writing done today is timestamped tomorrow. Until then a certificate says it is not yet timestamped. Your Passport links to the public anchor log, where each day’s fingerprint and the receipts from the outside services are listed for anyone to see: choose How this works at the top of your Passport.
Browsers that can’t sign
A browser too old to hold a signing key still records your sittings, but they are not signed. Your Passport says so. Write in a current Chrome, Safari, Edge or Firefox to sign them. Certificates can only be issued from a browser that holds a key.
Replacing a key
- Open Settings and find Signing keys.
- Choose Replace beside the key.
- Confirm with Replace key.
Certificates you already issued stay valid. The browser makes a fresh key the next time you open your Passport. The replaced key is listed as replaced, with the date. Replace a key if you stop using a computer or think someone else has used your browser.
If you clear your browser or change computer
A new browser makes a new key. Everything your old key signed stays checkable, and the record carries on.
When a record doesn’t match
Each chapter’s sittings are chained: every summary includes a fingerprint of the one before it. If a link no longer matches, the chapter is marked, and your Passport says that something doesn’t match what was recorded, with the address to write to. Nothing is hidden: a broken link is shown, not removed.