Research updatesSelect an entry to read more
Lean’s maintainers clarify what its newly bundled “verified kernels” actually guarantee
This is a substantive clarification of the previously reported Lean 4.35 release, not a second release announcement. Leonardo de Moura announced that Lean 4.35 ships with verified kernels and recommended “lake check --paranoid.” The official release documentation confirms that paranoid checking runs the official kernel plus bundled external checkers including lean4lean, nanoda, con-leche and con-ron. The primary repositories make the assurance more precise: con-leche’s proved result is conditional consistency—when its default verified mode accepts an export, the resulting environment has no constant of type False, relative to an explicit set-theory interface. Con-ron is a Rust port whose core is intended to inherit that protection through an Aeneas-mediated equivalence argument. This gives researchers a practical, higher-assurance workflow for checking untrusted or AI-generated Lean projects with diverse implementations.
Research relevance:
For AI-assisted mathematics, the useful change is operational: a researcher can subject a generated development to several bundled checkers instead of trusting a single kernel implementation. The con-leche artifact is also an unusually concrete example of AI-assisted construction of a proof checker together with a machine-checked metatheoretic guarantee.
- Claim status:
- Officially announced and supported by Lean 4.35 release documentation and public source repositories. The existence and stated theorems of con-leche can be inspected in source, but this digest did not compile the projects, run lake check, inspect every dependency, or independently verify the formal proofs. “Verified kernel” here denotes specific proved properties and does not mean that the complete hardware-to-source execution chain is formally certified.
- Limitations:
- The underlying Lean 4.35 release is dated 2026-10-12 and was already reported; the new in-window event is the October 15 explanation and October 16 X announcement. The linked blog itself was inaccessible to the web tool and was therefore not directly read. Con-leche’s theorem applies to acceptance in its verified mode, depends on a stated set-theory interface, and allows the checker to decline unsupported inputs. Its trusted mode is outside the theorem. Con-ron’s own README describes its assurance as not high-assurance, notes reliance on the Aeneas translation pipeline, and identifies unsafe runtime code outside the proof. Diverse checking reduces implementation risk but does not establish that a formal statement faithfully expresses the intended informal theorem, nor does it eliminate compiler, runtime or hardware risk. Lean’s sandboxing for these commands is currently documented as Linux-only.
Sources & further reading
- Leonardo de Moura’s in-window X announcement, supplied by direct X API collectionx.com
- Linked official Lean maintainer blog post; URL identified but page not directly readable by the web toolleodemoura.github.io
- Official Lean 4.35 release noteslean-lang.org
- ConLeche human-written project READMEgithub.com
- ConLeche formalization metadata and stated theorem scopegithub.com
- ConLeche main theorem sourcegithub.com
- Con-ron human-written README and assurance limitationsgithub.com
Coverage and limitations
- Window examined: 2026-10-15 04:54:47 through 2026-10-16 08:00:01 Europe/Paris. Older underlying material was excluded unless an in-window source supplied a genuine update.
- Direct X API collection was available but bounded for all supplied X accounts; replies and reposts were excluded, cached posts may have been included, pagination was incomplete, and API resolution did not independently verify identities. The feeds for Levent Alpöge, Scott Armstrong, Timothy Gowers, Sébastien Bubeck, Thomas Bloom, Daniel Litt, François Charton, Lean, Project Numina and Harmonic contained no posts. Empty bounded feeds do not establish inactivity.
- The direct X feeds contained posts from Alex Kontorovich, Leonardo de Moura, Boaz Barak, Axiom and Epoch AI. Kontorovich’s post concerned hiring. Barak’s posts did not provide a new primary mathematical result. Axiom’s one-line Annals Bench post linked only to another X account and could not be substantiated from an accessible primary artifact. Epoch AI’s posts concerned general capability rankings and compute rather than a substantial mathematical-research result.
- Leonardo de Moura’s supplied X API post was read directly as collected data. His identity and the technical substance were checked against the official Lean release documentation and the leanprover organization’s public repositories. The linked October 15 blog page could not be opened by the web tool, so only its indexed existence and the link supplied in the API post were observed; it was not treated as directly read.
- The Bluesky collection for xenaproject.bsky.social succeeded but returned no posts; replies and reposts were excluded and at most 300 posts were checked. Terence Tao’s Mathstodon collection failed with an HTTP error; replies and reposts would have been excluded and at most 300 posts checked. Therefore neither empty Bluesky results nor the unavailable Mathstodon feed establish that nothing was posted.
- Public web searches also checked Terence Tao’s official blog, Kevin Buzzard/Xena-related results, Simon Frieder’s official site and blog, Lean documentation and repositories, recent Lean and AI-for-mathematics searches, and leads around Annals Bench. Search access is index-dependent and not exhaustive. Some X-linked material was visible only as supplied API text or indexed snippets, not as directly opened timelines.
- Previously reported items were deduplicated. In particular, Lean 4.35 and its project-checking commands were already covered on October 12; the included item is limited to the later clarification that two bundled checkers carry specific formal guarantees, together with important restrictions on those guarantees. No code was downloaded or executed, and no Lean proof was checked in this research process.
Requested coverage window: 2026-10-15T04:54:47.359674+02:00 — 2026-10-16T08:00:01.872228+02:00.
Public web research; coverage is not exhaustive. A source link is not a certification of a claim.
Archives 55
- 24 Oct 202609:15:01 CEST · 83273e55
- 23 Oct 202609:13:07 CEST · 5bf9744c
- 23 Oct 202608:00:01 CEST · 6ccbbc7e
- 22 Oct 202608:00:01 CEST · 798b79fd
- 21 Oct 202608:00:02 CEST · 9b477733
- 20 Oct 202608:00:01 CEST · 75a69a2e
- 19 Oct 202609:47:43 CEST · f799c226
- 18 Oct 202608:00:01 CEST · b3b4112f
- 17 Oct 202608:00:01 CEST · 00aa242d
- 16 Oct 202608:00:01 CEST · 32a9e1e6
- 15 Oct 202616:54:47 CEST · f093ad2f
- 13 Oct 202620:25:48 CEST · 6138f010
- 13 Oct 202620:20:11 CEST · caeebf3f
- 13 Oct 202620:16:48 CEST · c28bdb56
- 13 Oct 202616:17:50 CEST · 0b02ca1d
- 12 Oct 202608:00:01 CEST · c1a48b74
- 11 Oct 202622:01:57 CEST · 50deb522
- 11 Oct 202608:00:02 CEST · b297cb00
- 10 Oct 202608:00:01 CEST · d77941f9
- 9 Oct 202609:13:03 CEST · c4acaaf1
- 9 Oct 202609:13:03 CEST · ab04ecd2
- 9 Oct 202609:13:03 CEST · 1b189d44
- 9 Oct 202608:00:01 CEST · ce20e166
- 8 Oct 202608:19:28 CEST · ab8d0f6f
- 7 Oct 202615:49:06 CEST · f9ce0158
- 6 Oct 2026Retrospective
- 5 Oct 2026Retrospective
- 4 Oct 2026Retrospective
- 3 Oct 2026Retrospective
- 2 Oct 2026Retrospective
Older editions (25)
- 1 Oct 2026Retrospective
- 30 Sep 2026Retrospective
- 29 Sep 2026Retrospective
- 28 Sep 2026Retrospective
- 27 Sep 2026Retrospective
- 26 Sep 2026Retrospective
- 25 Sep 2026Retrospective
- 24 Sep 2026Retrospective
- 23 Sep 2026Retrospective
- 22 Sep 2026Retrospective
- 21 Sep 2026Retrospective
- 20 Sep 2026Retrospective
- 19 Sep 2026Retrospective
- 18 Sep 2026Retrospective
- 17 Sep 2026Retrospective
- 16 Sep 2026Retrospective
- 15 Sep 2026Retrospective
- 14 Sep 2026Retrospective
- 13 Sep 2026Retrospective
- 12 Sep 2026Retrospective
- 11 Sep 2026Retrospective
- 10 Sep 2026Retrospective
- 9 Sep 2026Retrospective
- 8 Sep 2026Retrospective
- 7 Sep 2026Retrospective