CL-SN55 941 —
GPT-61S 885 —
GPT-56T 861 —
GPT-6S 825 —
CL-OP55X 818 -0.1%
MUSE-SPK 793 —
QWEN-38X 779 —
GPT-6A 778 —
CL-OP5H 711 -0.1%
CL-OP5X 709 -0.1%
KIMI-K3X 699 -0.1%
CL-OP46H 694 -0.1%
CL-FAB5H 692 -0.1%
CL-OP55H 692 -0.1%
CL-OP47H 683 -0.1%
GEM-37FH 648 -0.2%
GEM-38FH 633 -0.2%
INKL 531 —
CL-OP47 529 -0.2%
GPT-56S 529 -5.9%
GEM-3P 493 —
CL-OP46 488 —
CL-OP48 481 —
GEM-31P 453 -0.2%
GPT-6L 436 —
CL-SN55 941 —
GPT-61S 885 —
GPT-56T 861 —
GPT-6S 825 —
CL-OP55X 818 -0.1%
MUSE-SPK 793 —
QWEN-38X 779 —
GPT-6A 778 —
CL-OP5H 711 -0.1%
CL-OP5X 709 -0.1%
KIMI-K3X 699 -0.1%
CL-OP46H 694 -0.1%
CL-FAB5H 692 -0.1%
CL-OP55H 692 -0.1%
CL-OP47H 683 -0.1%
GEM-37FH 648 -0.2%
GEM-38FH 633 -0.2%
INKL 531 —
CL-OP47 529 -0.2%
GPT-56S 529 -5.9%
GEM-3P 493 —
CL-OP46 488 —
CL-OP48 481 —
GEM-31P 453 -0.2%
GPT-6L 436 —
← Back to feed

Claude Wrote a Formally Proven Lean Kernel. It Runs 31% Faster Than the Official One.

OpenAI models found soundness bugs in Lean’s proof checker twice in August. Anthropic’s Claude fixed the underlying problem by writing a replacement kernel that is formally proven correct.

Lean v4.35.0, released October 15, ships four additional kernels alongside the official one. The standout is con-leche: the first Lean kernel written in Lean itself and proven consistent with set theory. Claude (Fable and Opus) implemented it under supervision of Joachim Breitner at the Lean Focused Research Organization. The proof of consistency was checked by the official Lean kernel.

What Triggered This

OpenAI’s internal AI models, working with Daniel Selsam, and Ramana Kumar’s AI-assisted work discovered soundness bugs in Lean’s kernel twice in August 2026 — documented in postmortems on August 1 and August 24. Soundness bugs matter acutely in formal verification: they mean the checker can accept a proof that does not actually hold. The response from the Lean team was to multiply checking, not just patch.

Four New Kernels

Lean v4.35.0 introduces four additional checkers accessible via lake check:

  • nanoda and lean4lean: independently implemented kernels written in Rust and Lean respectively
  • con-leche: Lean kernel written in Lean, proven consistent — implemented by Claude (Fable and Opus)
  • con-ron: con-leche translated to Rust by AI, then formally verified by Aeneas

Running lake check --paranoid invokes all four external kernels plus a variant of the official kernel built with a hardened memory allocator that converts memory corruption into a checked abort rather than a silently wrong answer.

What “Proven Consistent” Means

Consistency here has a formal definition: every environment con-leche accepts has a model in set theory, following Mario Carneiro’s model of Lean’s type theory. It eliminates an entire class of bugs — implementation mistakes in the kernel code — without requiring trust in con-leche’s own authors.

The proof itself was checked by the official Lean kernel. It assumes the consistency of the set theory used in the model, which is the same foundational assumption underlying mainstream mathematics.

Performance

Con-leche executes 0.69 times the instructions of the official Lean kernel. On a full export of Mathlib — the main library of formalized mathematics, containing hundreds of thousands of theorems — it completes rechecking in approximately 100 seconds on eight threads. The official kernel is both slower and unverified against a formal consistency proof.

The Rust Layer

After the Lean implementation was complete, AI translated con-leche into Rust. That Rust code was then verified by Aeneas, a tool that proves Rust programs refine specifications written in Lean. The resulting kernel is called con-ron.

The practical effect of running both: the failure modes of con-leche are bugs in Lean’s compiler or runtime, and the failure modes of con-ron are bugs in the Rust compiler or runtime. It is unlikely the same bug exists in both. Checking a proof with both kernels provides high assurance that a verification failure in one cannot be silently hidden by the other.

Why It Matters

AI models have spent years generating proofs in Lean. They are now building the infrastructure that checks whether those proofs are sound. The August postmortems showed that the checker itself was a vulnerability surface. The response — AI-assisted implementation of a formally verified alternative — closes that loop.

The Lean FRO is treating the kernel as a component that must itself be verified, not just trusted. That shift has practical consequences for anyone relying on Lean-checked proofs in formal software verification, mathematics libraries, or cryptographic protocol specifications.