<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>Leonardo de Moura</title>
  <description>Blog posts and notes from Leonardo de Moura — creator of Lean and Z3.</description>
  <link>https://leodemoura.github.io</link>
  <atom:link href="https://leodemoura.github.io/feed.xml" rel="self" type="application/rss+xml" />
  <lastBuildDate>Mon, 20 Apr 2026 00:00:00 +0000</lastBuildDate>
  <item>
    <title>Signal Shot: The Platform Is Ready</title>
    <link>https://leodemoura.github.io/blog/2026-4-20-signal-shot-the-platform-is-ready/</link>
    <guid isPermaLink="true">https://leodemoura.github.io/blog/2026-4-20-signal-shot-the-platform-is-ready/</guid>
    <pubDate>Mon, 20 Apr 2026 00:00:00 +0000</pubDate>
    <category>Blog</category>
    <description>Signal Shot is a public moonshot to verify the Signal protocol and its Rust implementation using Lean. Not the math on paper. The actual code. It is a joint effort of Signal (Rolfe Schmidt), the Beneficial AI Foundation (Max Tegmark), and the Lean FRO. BAIF&apos;s launch post is here.</description>
  </item>
  <item>
    <title>Why Lean?</title>
    <link>https://leodemoura.github.io/blog/2026-4-2-why-lean/</link>
    <guid isPermaLink="true">https://leodemoura.github.io/blog/2026-4-2-why-lean/</guid>
    <pubDate>Thu, 02 Apr 2026 00:00:00 +0000</pubDate>
    <category>Blog</category>
    <description>Markus de Medeiros wanted to understand garbled circuits. He had no formal training in cryptography. He spent an afternoon in Lean: a circuit evaluator in functional style, a custom DSL via metaprogramming, OpenSSL bindings via FFI, a correctness proof for his serializer, and a mutable garbling algorithm in imperative style. All in one tool. His conclusion: &quot;I genuinely do not know of another tool that can do all of the following.&quot; And then: &quot;I fucking love this shit.&quot; That reaction keeps happen…</description>
  </item>
  <item>
    <title>Cray Colloquium at the University of Minnesota</title>
    <link>https://leodemoura.github.io/notes/2026-3-28-cray-colloquium-at-the-university-of-minnesota/</link>
    <guid isPermaLink="true">https://leodemoura.github.io/notes/2026-3-28-cray-colloquium-at-the-university-of-minnesota/</guid>
    <pubDate>Sat, 28 Mar 2026 00:00:00 +0000</pubDate>
    <category>Notes</category>
    <description>Next Monday, I am giving the Cray Distinguished Colloquium at the University of Minnesota Department of Computer Science &amp; Engineering. The Cray Colloquium Series was founded more than 30 years ago with a donation from Cray Inc. to honor the contributions and legacies of Dr. Seymour Cray. Past speakers include Turing Award winners and members of the National Academy of Engineering.</description>
  </item>
  <item>
    <title>Who Watches the Provers?</title>
    <link>https://leodemoura.github.io/blog/2026-3-16-who-watches-the-provers/</link>
    <guid isPermaLink="true">https://leodemoura.github.io/blog/2026-3-16-who-watches-the-provers/</guid>
    <pubDate>Mon, 16 Mar 2026 00:00:00 +0000</pubDate>
    <category>Blog</category>
    <description>In 2026, a skilled researcher using Claude (Opus 4.6), with real-time support from the Rocq development team, found seven kernel bugs in Rocq, a widely used proof assistant. Seven independent paths to proving something false. Rocq is a serious system with decades of foundational work. But even Rocq is vulnerable when AI applies sustained adversarial pressure to a single implementation. The question is not whether AI will find the bugs, but whether the architecture is built to survive them.</description>
  </item>
  <item>
    <title>This website is now powered by Verso</title>
    <link>https://leodemoura.github.io/notes/2026-3-15-this-website-is-now-powered-by-verso/</link>
    <guid isPermaLink="true">https://leodemoura.github.io/notes/2026-3-15-this-website-is-now-powered-by-verso/</guid>
    <pubDate>Sun, 15 Mar 2026 00:00:00 +0000</pubDate>
    <category>Notes</category>
    <description>This website is now built with Verso, the documentation tool for Lean. Verso is developed by David Thrane Christiansen at the Lean FRO. It powers the Lean language reference manual, the Lean website, and now this site. The main motivation: Lean code examples in blog posts are type-checked at build time and include interactive hover information. Try hovering over the code in Teaching AI to Make Proof Automation Work.</description>
  </item>
  <item>
    <title>Teaching AI to Make Proof Automation Work</title>
    <link>https://leodemoura.github.io/blog/2026-3-14-teaching-ai-to-make-proof-automation-work/</link>
    <guid isPermaLink="true">https://leodemoura.github.io/blog/2026-3-14-teaching-ai-to-make-proof-automation-work/</guid>
    <pubDate>Sat, 14 Mar 2026 00:00:00 +0000</pubDate>
    <category>Blog</category>
    <description>Consider this goal: example {α} [CommRing α] [IsCharP α 0] [NoNatZeroDivisors α] (d t d_inv : α) (Δ40 : d * (d + t + d * t) = 0) (Δ41 : d^2 * (d + d * t - 2 * d * t^2 + d * t^4 + d^2 * t^4) = 0) (_ : d * d_inv = 1) : t + 2 * t^2 - t^3 - 2 * t^4 + t^5 = 0 := by grind</description>
  </item>
  <item>
    <title>sym =&gt; : interactive mode for scalable verification</title>
    <link>https://leodemoura.github.io/notes/2026-3-13-sym---interactive-mode-for-scalable-verification/</link>
    <guid isPermaLink="true">https://leodemoura.github.io/notes/2026-3-13-sym---interactive-mode-for-scalable-verification/</guid>
    <pubDate>Fri, 13 Mar 2026 00:00:00 +0000</pubDate>
    <category>Notes</category>
    <description>We are building sym =&gt;, a new interactive tactic mode for writing scalable verification proofs in Lean. It extends grind&apos;s interactive mode with tactics from the Sym framework — our infrastructure for symbolic manipulation that achieves linear scaling on verification tasks where traditional approaches break down.</description>
  </item>
  <item>
    <title>When AI Writes the World&apos;s Software, Who Verifies It?</title>
    <link>https://leodemoura.github.io/blog/2026-2-28-when-ai-writes-the-worlds-software-who-verifies-it/</link>
    <guid isPermaLink="true">https://leodemoura.github.io/blog/2026-2-28-when-ai-writes-the-worlds-software-who-verifies-it/</guid>
    <pubDate>Sat, 28 Feb 2026 00:00:00 +0000</pubDate>
    <category>Blog</category>
    <description>Code Metal recently raised $125 million to rewrite defense industry code using AI. Google and Microsoft both report that 25–30% of their new code is AI-generated. AWS used AI to modernize 40 million lines of COBOL for Toyota. Microsoft&apos;s CTO predicts that 95% of all code will be AI-generated by 2030. The rewriting of the world&apos;s software is not coming. It is underway. Anthropic recently built a 100,000-line C compiler using parallel AI agents in two weeks, for under $20,000. It boots Linux and c…</description>
  </item>
  <item>
    <title>Proof Assistants in the Age of AI</title>
    <link>https://leodemoura.github.io/blog/2026-2-18-proof-assistants-in-the-age-of-ai/</link>
    <guid isPermaLink="true">https://leodemoura.github.io/blog/2026-2-18-proof-assistants-in-the-age-of-ai/</guid>
    <pubDate>Wed, 18 Feb 2026 00:00:00 +0000</pubDate>
    <category>Blog</category>
    <description>AI is transforming how we write formal proofs. Language models can now generate thousands of lines of verified mathematics with minimal human guidance, and the cost keeps dropping. This is exciting, and it raises a natural question: what role does the choice of proof assistant play when AI is doing more of the work? I believe the answer is that it matters more, not less.</description>
  </item>
</channel>
</rss>
