Signal brings key transparency into contact verification
Signal has introduced automatic key verification, a new layer for checking whether a conversation is still using the expected public encryption key. The feature complements Signal's existing safety number system rather than replacing it. Signal says the design uses key transparency, app-side checks and independent auditors to make unexpected key substitutions detectable across its ecosystem.What automatic key verification does
Automatic key verification is designed to confirm that there is no unexpected party between the two ends of an end-to-end encrypted Signal session. In a blog post published on Aug. 11, 2026, Signal described the feature as a streamlined counterpart to manual safety number verification, which traditionally requires scanning a QR code or comparing a long number through a trusted channel.The user-facing flow is placed inside a contact's profile. Signal says users can open View Safety Number, tap Verify automatically under Automatic key verification, and see a green checkmark with Encryption verified when the feature is available and the check succeeds. That makes the verification action easier to perform, while keeping the existing manual safety number system available for people who want or need direct comparison.
Why public-key directories need transparency
The security problem is not message encryption itself, but confidence that a public identifier is mapped to the correct public encryption key. Signal says its service remains end-to-end encrypted, while automatic key verification adds a way to detect whether the directory association between a phone number or username and a public key has unexpectedly changed.Signal explains the threat with a hypothetical Mallory-in-the-middle scenario. If a malicious party could compromise the directory that supplies public keys, that party could return a different key for a targeted account, allowing interception before messages are forwarded onward. Signal describes this as an advanced and unlikely attack, but one worth defending against because the public-key lookup step is central to encrypted messaging.
Key transparency addresses this by making directory changes globally consistent and transparent to participating clients. The practical implication is narrower than identity proof: users are checking that the key view is consistent across Signal's ecosystem, not proving who controls a phone number or username in every possible account-takeover scenario.
How Signal's key transparency design works
Signal's implementation records registration, phone number changes, username changes and account re-creation events in a log tree. Searches through that log are supported by prefix trees, which Signal compares to index books in a public ledger analogy. Together, these structures form the key transparency log used to check whether identifier-to-key mappings have remained consistent.The design is meant to avoid making every user download or inspect the whole record. Instead, the system returns the specific data needed to verify a search path. Signal says this allows a device to check the result efficiently, while still detecting attempts to show different versions of the record to different users.
The feature also relies on repeated monitoring. A user's own Signal app automatically and periodically checks that user's public identifiers in the log. For a connection, the check must be started from the View Safety Number screen, which means the system combines background self-checks with contact-specific verification by the person using the app.
Auditors add consistency checks without plaintext user data
Cloudflare and Trail of Bits serve as independent auditors for Signal's key transparency system. Signal says these auditors check that the log and index structures evolve consistently, then use cryptographic signatures so clients can verify that the system is not presenting conflicting versions of the same record.The auditors are not described as identity verifiers. Their role is to help establish that everyone is looking at the same set of records, while monitoring by users and their devices detects whether those records contain unexpected changes for a particular identifier.
Signal says user data in the log is cryptographically obscured. Public identifiers are processed through a verifiable random function, and mapped values are protected by a keyed hash function, so auditors do not see plaintext user data. Lookup requests to the log are unauthenticated, according to Signal, and are not tied to a specific user account.
Where the feature still has limits
Automatic key verification does not verify the real-world identity of the person controlling a phone number or username. Signal says additional verification, such as following up after a safety number change, remains necessary for cases where an attacker has fully taken control of an account.The first version also has a practical limitation for username-only contacts. Signal says the app automatically verifies a user's own phone number and username data, but verifying someone else currently requires having that person's phone number. If two people connected only by username and did not exchange phone numbers or otherwise have access to them, automatic verification is unavailable for that connection.
Out-of-date phone numbers can also block the feature. Signal says a contact changing phone numbers has no security impact on the contact's public encryption key or the underlying encrypted session, but the local device may no longer have the current phone number record needed for automatic verification. In those cases, Signal recommends using a secondary trusted channel or the existing safety number system. Users who do not want to rely on Signal or the auditors can disable Automatic Key Verification under Privacy, Advanced, Automatic Key Verification.
Conclusion
Signal's automatic key verification is a security usability change rather than a new messaging mode. It moves part of the burden from manual comparison toward a key transparency system that can expose inconsistent or unexpected public-key mappings.The trade-off is clear in Signal's own description. The feature can make an important verification step easier and more continuous, but it does not remove the need for manual safety numbers, trusted follow-up after suspicious changes, or caution in account-control scenarios. For privacy-focused users, the most relevant change is that key transparency is now available inside the normal Signal verification workflow, with a manual opt-out still present.
Sources
Editorial Team - CoinBotLab
