Signal has introduced Automatic Key Verification (AKV), a new security feature that gives users a streamlined way to confirm their encrypted conversations have not been intercepted — without requiring the manual safety number comparisons that many users skip or misunderstand.
The Problem: Key Swap Attacks
End-to-end encryption is only as strong as your ability to verify who holds the keys. In a man-in-the-middle (MITM) attack, an adversary — such as a compromised server, a malicious insider, or a nation-state threat actor — could potentially associate a different public key with your contact's phone number or username. Your app would then encrypt messages to the attacker's key rather than your contact's, silently breaking the end-to-end guarantee.
Signal's existing safety number system addressed this, but it required users to physically meet or compare fingerprints over a trusted channel — a friction point most skip in practice.
How Automatic Key Verification Works
AKV builds on a Key Transparency architecture based on the IETF Key Transparency protocol draft. Rather than relying solely on Signal's server to assert which key belongs to which user, the system enforces a cryptographic guarantee: the mapping between identifiers (phone numbers or usernames) and public keys must be globally consistent and transparent to all participants.
The Cryptographic Foundation
Signal's Key Transparency system has three core components:
-
Append-only log tree ("the ledger") — Records all key and identifier changes chronologically. Because it is append-only, past entries cannot be silently altered. Any retrospective change would break the cryptographic chain.
-
Prefix trees ("index books") — Enable efficient binary search through the log, so a client can verify a specific entry without downloading the entire ledger. This keeps verification fast and bandwidth-efficient.
-
Privacy-preserving protections — Public identifiers are passed through Verifiable Random Functions (VRFs) before being entered into the log, and values are protected with keyed hash functions. Even Cloudflare and Trail of Bits — Signal's independent auditors — never see plaintext user data.
The Verification Layers
Verification combines three independent layers:
| Layer | Who | What |
|---|---|---|
| Auditing | Cloudflare, Trail of Bits | Verify each log edition contains all prior data plus exactly one new addition |
| Self-monitoring | Your Signal client | Periodically checks your own keys in the log |
| Cross-verification | Your contacts' devices | Check each other's records on independent schedules |
If Signal's server attempted to show Alice a different key for Bob than what Bob's device sees, the auditors — monitoring successive log editions cryptographically — would detect the divergence. Requests to the transparency log are unauthenticated, so the verification itself does not expose who is checking whom.
Signal engineer Katherine Yen described the result: AKV "works through a system of verifications performed by you, your Signal connections, and third-party auditors that together provide the same assurance as manually verifying safety numbers."
User Experience
Users can enable AKV under Settings > Privacy > Advanced. Once active:
- When verifying a contact, a successful check shows a green checkmark and "Encryption verified"
- The process is automatic and continuous — no manual fingerprint comparison needed
- Users who prefer the existing manual safety number method can disable AKV and keep the legacy flow
The feature launched August 11, 2026.
Limitations
AKV cannot operate in all scenarios. It falls back to manual safety number verification when:
- A contact was added via username only (phone number is unknown)
- A contact changed their phone number after being added
- A contact has restricted phone number visibility
Importantly, AKV verifies key consistency — not the real-world identity of the person controlling an account. A fully compromised account still warrants out-of-band confirmation.
Why It Matters
Key transparency is not a new concept — Google's Certificate Transparency framework applies the same principle to TLS certificates — but applying it to a consumer messaging app at Signal's scale is significant. The approach transforms trust in encryption from a binary "do you trust Signal's server?" to a verifiable, audited, cryptographic proof.
For security-conscious users, journalists, activists, and anyone operating in adversarial environments, AKV substantially raises the bar for the class of attacks where a compromised or compelled messaging provider could silently swap keys.
Takeaway
Signal's Automatic Key Verification represents one of the most meaningful advances in consumer end-to-end encryption in years. By embedding key transparency directly into the app experience — with independent auditors, automatic verification, and a simple green checkmark — Signal has made robust MITM protection accessible to everyday users without requiring security expertise.
References