Google DeepMind Uses AlphaProof Code to Formally Verify Signal Protocol Guarantees in Four-Week Research Project

Google DeepMind has completed a four-week proof-of-concept project using a new AI framework called AlphaProof Code to formally verify selected cryptographic guarantees in the Signal protocol, the encryption design underlying Signal, Google Messages and WhatsApp. The work, reported by WIRED, represents a demonstration of AI-assisted formal verification on real-world security-critical code—but with clear scope limits and unresolved questions about cost and scalability [1].

What was actually done

DeepMind researchers applied AlphaProof Code to "a number of the Signal protocol's key cryptographic guarantees" [1]. Formal verification uses mathematics to prove that software meets specified requirements—in this case, that the protocol's cryptographic properties hold as designed. The analysis found no new vulnerabilities in the portions examined. As a validation step, the team also ran AlphaProof Code on older Signal versions containing known, long-fixed vulnerabilities; the system identified those flaws and showed the protocol could not be formally verified in those versions [1].

The researchers are releasing the specification and proof they developed to support other formal verification work [1].

Scope limits and head start

The project did not formally verify the entire Signal mobile app, nor every part of the services that use the protocol [1]. DeepMind researchers emphasize the findings are "just one milestone in a larger process" [1]. Swarat Chaudhuri, a DeepMind research scientist, told WIRED: "We are very excited by this result, but there is a long distance to go before we are able to scale this to all the software of the world, and we want to do that" [1].

The four-week timeline also benefited from prior formal verification work by the Signal Foundation, which the DeepMind team said gave them "a head start to a degree" [1]. Signal chief technology officer Ehren Kret stated that "while prior formal verification focused on smaller portions of the code, Google DeepMind's approach enables significant expansion" [1].

Human-AI collaboration, not autonomy

DeepMind describes the workflow as a "human-AI collaboration process" in which agents contribute and self-correct at almost every phase while humans provide input and review at key junctures [1]. Chaudhuri told WIRED the team does not want a "vibe world where AI is generating the goals and AI is generating the proofs and basically taking tests that are self-written," adding that "there's a middle ground" [1]. People still define what properties to prove and review critical stages.

Cost and commercialization unknown

DeepMind conducted the analysis free of charge as a research project. Google declined to share the cost of the work and declined to comment on whether it plans to release a commercial formal verification product or service [1]. Pushmeet Kohli, chief scientist at Google Cloud and DeepMind's vice president of research, framed the potential value broadly: "If you can now verify the correctness of these implementations, then you can rest easy... You can imagine banks, imagine all those other companies who rely on assurances and who worry about bugs who could now say, 'I can prove these properties.'" [1]

The open question: scale and cost

The central constraint remains whether AI-automated formal verification can cover far more software at a workable cost. Formal verification has historically required substantial human effort to describe intended behavior and build proofs. AlphaProof Code aims to shorten the proof-building phase, but the specification-writing and review steps still demand expertise. DeepMind's ambition reaches well beyond messaging apps, yet Chaudhuri acknowledges the goal is "a long way off" [1].

For now, the concrete result is a bounded research demonstration: selected Signal protocol guarantees mathematically verified in four weeks with human-defined requirements, prior art as a foundation, and the artifacts released for others to build on. Whether this becomes a scalable service—or remains a high-effort showcase—depends on economics that have not been disclosed.