BRIGHT EVIDENCE PACK / Emerging
AI helps check the code that keeps private messages private
Google DeepMind’s AlphaProof Code produced machine-checked proofs for parts of Signal’s cryptographic implementation. The promising step is making rigorous software checks easier to do, with people still deciding what must be proved.
Canonical Bright record · JSON evidence pack · Key-facts embed
Dates and assessment
- Source published
- 2026-11-10
- Bright published
- 2026-11-11
- Substantive update
- 2026-11-11
- Evidence state
- Emerging
- Independent verification
- Not established by this source review
- Last source review
- 2026-11-11T12:07:18.168Z
The claim in context
The human problem
A private message can hold something ordinary and irreplaceable: a family conversation, a plan with a friend, a difficult question. Most of us cannot inspect the code carrying it. We depend on other people finding ways to check that the protection works.
The prior constraint
Rigorous verification of real software has required substantial specialist work, limiting where it can be applied.
AI’s actual role
AI agents draft specifications under human review and generate proofs checked by Lean against approved statements.
The documented result
DeepMind reports machine-checked proofs of specified security properties for a compiled build using libsignal, with about 6.5 million lines of proof and roughly 26,000 lines of trusted specifications and processor semantics.
Why it may matter
If this approach becomes affordable and repeatable, more software maintainers could check whether important protections hold in the implemented code. That wider benefit remains to be demonstrated.
Limitations
- The result concerns specified properties of a particular AArch64 command-line build of libsignal v0.105.4’s one-to-one session code, not the complete Signal applications. Group messaging, multi-device state and side channels are outside its scope.
- The proofs depend on trusted specifications, processor and environment models, and cryptographic assumptions. The computational proof offers no quantum-adversary guarantee. A separate symbolic proof covers handshake secrecy if an attacker later breaks Diffie–Hellman key exchange, but not the added post-quantum ratchet’s recovery after compromise.
- Bright has not rerun the proofs or independently audited their assumptions. Public artifacts are available for scrutiny; affordability, broader coverage and routine commercial use are not established.
Original evidence
- Google DeepMind · November 10, 2026 · primary technical report and public proof artifacts; scope and limitations in sections 5.1.6 and 5.2.5 · paper
- Google DeepMind · November 10, 2026 · institutional announcement · institution
- Signal · Double Ratchet specification · background on messaging security design · institution
- WIRED · November 10, 2026 · reporting on undisclosed costs and commercial plans, not independent proof replication · report
Attribution
Credit Bright AI Future and link the canonical Bright record.
- Link to the canonical Bright record.
- Keep material limitations with the claim they qualify.
- Link to the original evidence when repeating a substantive claim.
- Do not describe a source check or organization-reported result as independent verification.
Linked source material, quotations, trademarks and media remain subject to their owners’ terms. No reuse right is granted for third-party media.