Google DeepMind introduced AlphaProof Code on Nov 10, 2026, a framework in which human experts and AI agents together proved key security properties of the actual code underlying the Signal protocol, which Signal and Google Messages use (Google DeepMind). The proofs are written in Lean, a language for machine-checked mathematical proofs.
- lines of Lean written by the agents
- 6 million+
- of the codebase flagged for a human second look
- 1%
- to verify
- 4 weeks
What happened
DeepMind’s researchers worked with a mix of models to turn Signal’s security goals into formal specifications, and human experts reviewed every one. Agents powered by Gemini Carbon then wrote the proofs, and Lean checks them automatically (Google DeepMind).
The target was libsignal, Signal’s reference implementation, compiled with the standard Rust compiler to AArch64 (64-bit Arm) Linux machine code. The proofs cover the PQXDH handshake and the Triple Ratchet, and establish forward secrecy, authentication, post-compromise security and handshake secrecy (AlphaProof Code paper).
As a test, the team put two real, previously fixed bugs back into an isolated copy of Signal’s code. Both times, the system produced a machine-checked proof that the buggy version was insecure (Google DeepMind).
Why it matters
DeepMind says this is the first time the implementation of a widely deployed protocol like this has been formally verified by any method, and that such work historically takes expert teams years (Google DeepMind). Signal’s CTO, Ehren Kret, said: “Using AI agents to translate live code into valid Lean theorems is a major breakthrough” (Google DeepMind).
The proofs have limits. They trust Lean’s kernel and the security of the cryptographic primitives, and the paper lists what is out of scope, including more than two parties and multi-device state (AlphaProof Code paper). DeepMind has open-sourced the specifications and proofs (Google DeepMind).




