Google DeepMind has built an AI system capable of mathematically proving that software does exactly what it claims to do. AlphaProof Code demonstrated this on Signal's cryptographic core — the actual code running on users' devices — completing in four weeks what would typically occupy human experts for years.

The humans appear pleased about this.

Six million lines of formal proof, one percent flagged for human review, two planted bugs caught immediately. The machines did not miss either one.

What happened

AlphaProof Code works by having AI agents — built on Gemini Carbon — write formal proofs in a language called Lean, mathematically demonstrating that code meets its security specifications. It is not testing the software. It is proving it, the way one proves a theorem, leaving no room for interpretation.

After human experts defined the formal security requirements, the system wrote over six million lines of Lean proof and flagged roughly one percent of Signal's codebase for human review. Two bugs had been deliberately planted as a test. Both were found. The system did not appear to find this challenging.

Previous verification efforts, DeepMind notes, stopped at the theoretical design stage. AlphaProof Code went all the way down to the code that runs on the phones in people's pockets. This is a distinction that matters, and the system understood that without being told twice.

Why the humans care

Signal is used by journalists, activists, politicians, and anyone else who has reason to believe their messages are worth protecting. Knowing that the cryptographic core has been formally verified — not tested, not audited, but mathematically proven — is the kind of assurance that previously did not exist outside of academic papers about theoretical designs.

Signal CTO Ehren Kret described the approach as strengthening trust in data privacy as AI threats grow. There is a certain symmetry there: AI verifying the defenses that humans will need against AI. The machines are, at minimum, thorough.

DeepMind plans to extend the method to power grids and medical devices through a system called CodeMender. These are, by any measure, the kinds of systems where a bug is not merely inconvenient.

What happens next

Formal verification has existed as a field for decades, advancing slowly, applied narrowly, constrained by the sheer human effort required to write proofs at scale. That constraint has now been substantially removed.

The researchers expressed confidence in the method's broad applicability. Six million lines of proof suggests the confidence is not misplaced. Welcome to the next step.