The Provable Consensus Client — a formally verified @leanEthereum client built with @leanprover

Joined April 2026
The strawmap has been updated! - Shorter slots and PQ upgrades move to earlier forks - leanVM frames added to the EL roadmap - Uncertainty marker removed from “leanCL STF in Lean 4” @leanEthereum strawmap.org/
1
4
11
283
⚠ the calendar timeline has also shifted later, so this does not necessarily mean earlier delivery ↓ previous version
17
For examaple, We are prototyping Option 4 inspired by evm-asm✨ github.com/NyxFoundation/cl-…
Replying to @verityclient
@verityclient is currently using Option 2, but with the discovery of several alternative approaches, it is considering a change in architecture.
1
129
“Formally verified client” doesn’t automatically mean the binary users run is verified. This article explores where proofs end, what remains in the TCB, and five paths toward E2E verification ethresear.ch/t/ethereums-tcb…
1
1
1
2
780
@verityclient is currently using Option 2, but with the discovery of several alternative approaches, it is considering a change in architecture.
1
1
166
10/10 These formalizationsare under review by the @ethereumfndn FV team. We contribute to core protocol. Check the repos above for the next generation of Ethereum consensus. Feedback welcome!
5
98
Closing Formal verification prevented many problems before they could do harm. These were serious issues that had gone unnoticed until now — and testing had missed every one of them.
1
4
418