Signal ships automatic key verification audited by Cloudflare and Trail of Bits, closing a decade-long identity gap in end-to-end encryption

What changed on August 13, 2026

Signal introduced automatic key verification on Tuesday in a post by software engineer Katherine Yen. The feature confirms that the link between a phone number or username and its public key is globally consistent, using a tamper-evident ledger built from log trees and prefix trees. Signal keeps that log on its own infrastructure, and independent auditors sign each entry, while the user's own app checks identifiers automatically and periodically.

Checking a specific contact now takes a single tap on the safety number screen, where the button returns a green checkmark and the words "Encryption verified." Yen made the comparison directly: she wrote that the checks "provide the same assurance as manually verifying safety numbers", and unlike safety numbers they need no in-person meeting. That single sentence is the crux of the change.

For a decade, end-to-end encryption was always conditional on a user comparing codes with a friend in a coffee shop — a step most people skipped. The new mechanism aims to deliver the same assurance through the device, without requiring any out-of-band ritual. Verification also narrows from a private conversation between two people to a public, auditable process that any auditor can inspect after the fact.

For an industry that already treats keys as the load-bearing element of secure messaging, this is a structural change in how identity gets bound to the key, and how readers who handle cryptography in production should weigh what they trust.

How the auditors fit in

Two external auditors, Cloudflare and Trail of Bits, each sign the ledger independently. The point of the design is that no single party can show one version of the log to one user and a different version to another, and that property holds only if more than one party is involved. An audit with one auditor would reintroduce exactly the trust problem the system exists to remove, which is why Signal names both Cloudflare and Trail of Bits rather than letting either speak for the whole pipeline.

Cloudflare pulls batches of updates from Signal's log and checks cryptographically that each update is consistent with everything recorded before it, then signs the update, and Signal passes the signed version to users. The auditor works only over cryptographic proofs. It does not see phone numbers, usernames, public keys, or message contents, so the privacy properties of the underlying chat are preserved while still producing a public, verifiable trail.

Cloudflare built the system in Rust on its own Workers platform, leaning on an append-only verification method from Meta's open-source key directory library. It has run the same infrastructure for WhatsApp since September 2024, publishing results to a public dashboard, and Cloudflare CTO Dane Knecht said that "Independent auditing is the logical next step: not just promising encryption, but making it provable." Readers tracking this as a cryptographic standard story rather than a product launch should treat it as a deployment change rather than a new primitive.

What automatic does not actually verify

The system does not verify who actually controls a phone number or username, automatic verification is unavailable for contacts using username-only discovery, and the check stops working if a contact changes their number; the feature can be switched off in Settings under Privacy and then Advanced. That paragraph of caveats is the most important part of any honest read of this launch, and it is worth restating because the word automatic tends to imply more than it delivers. What the ledger proves is that a given public key is the one bound to a given identifier in the signed log.

It does not prove that the person holding that identifier is the person you think you are talking to. A second channel — in person, voice, or any trusted out-of-band path — is still required to nail down who is on the other end, and Signal tells users to follow up through exactly that secondary, trusted channel when these edge cases appear. Username-only contacts have no phone number to anchor the verification, so the check is unavailable for them.

A number change breaks the binding entirely. The kill switch under Settings, Privacy, then Advanced means that an organization or individual can opt out, which is itself a useful control but worth noting in any deployment or risk discussion. Read this together with the cryptographic guarantees, not against them — readers here will recognize the pattern.

Mapping a key to an identifier is a different problem from mapping an identifier to a person, and the launch only addresses the first.

Why it lands harder in Europe and what readers should do

A tamper-evident ledger changes what silence means for European operators. Any undisclosed key substitution becomes visible after the fact to anyone who checks, because the signed log is reproducible. That is a live question on this continent, where telecom chiefs have pressed for blocking orders against illegal content and the wider lawful-access argument has not gone away.

Signal has been the loudest voice in that room, and its position is now backed by infrastructure that makes tampering detectable, not just disclaimed. For practitioners, three concrete steps follow. First, audit any number-change events in monitored traffic against ledger snapshots before treating them as routine, since stopping checks on number change is now a documented event worth logging.

Second, review whether username-only contacts in managed environments need the secondary-channel ritual, because automatic verification is unavailable for them. Third, track who your auditors are: Cloudflare now audits the two largest end-to-end encrypted platforms in the world, and Trail of Bits is the structural counterweight, with each signing the ledger independently. Concentration questions are real, and the answer here is the second auditor.

Watch whether other messengers adopt similar designs, and whether Signal publishes enough signed-log material for third parties to verify, rather than only its two named auditors.

What to watch next

The unresolved questions sit in the gaps that the launch explicitly leaves open. The first is governance: Cloudflare already audits key transparency for WhatsApp as well as Signal, and the two largest end-to-end encrypted platforms in the world are now both checked by a single company that decides who may block AI crawlers. Trail of Bits is the answer to that objection, and the design survives Cloudflare going bad, which is the whole idea, but that answer is only as strong as the second auditor's continued independence, capacity, and willingness to act publicly on inconsistency.

The second is scope: identity binding proves a key belongs to an identifier, not that an identifier belongs to a person, so anyone treating "verified" as a substitute for identity proofing will misread the feature. The third is policy: a tamper-evident log changes what silence means, because any undisclosed key substitution becomes visible to anyone who checks, and that property travels with the design wherever Signal is installed. Watch the audit cadence, the public dashboards, and any incident in which the two auditors disagree or a number change is later called into question, because each of those will be the first real-world signal of whether automatic verification is doing the work its name implies.