Minimalist, fast and modular implementation of the Lean Ethereum client written in Rust. Built by @class_lambda
Joined January 2026
- Tweets 122
- Following 2
- Followers 303
- Likes 27
40 Photos and videos
Jun 12
We wrapped up our community call, and the recording is already available. Catch up on what we've been building and what's coming next.
Jun 12
Ethlambda Community Call x.com/i/broadcasts/1OxwbbRdj…
1
61
Jun 11
In case anyone missed it, yesterday started the EF devnet 5 client interop runs. We already merged our devnet5 branch to main and are running internal devnets in parallel, looking for issues or performance improvement opportunities.
1
3
13
603
Jun 11
Community Call #20 is tomorrow, live on X at 3:30 PM UTC. We'll walk through what the team has been working on and what's ahead. Don't miss it.
52
Jun 10
We saw an aggregation performance regression in a devnet, when trying out the newest leanVM changes. When running leanVM benchmarks on it, and comparing both the old and new commits, we found that the regression affected the raw XMSS aggregation only (not recursive aggregation).
1
1
8
507
Jun 10
After investigating, we found the cause: a recently-created 256 MB buffer was being copied into a new memory location owned by the new allocator used by the library.
We made a fix for this, which resulted in an overall 7% improvement from the old version.
1
1
100
Jun 10
The PR is already merged to the devnet4 branch of leanVM. You can look at the changes here: github.com/leanEthereum/lean…
1
53
Jun 5
We wrapped up today's community call and the recording is out. Catch up on what we've been building and what's coming next.
Jun 5
Ethlambda Community Call x.com/i/broadcasts/1YxNrrDBV…
1
1
63
Jun 4
We're going live tomorrow on X with our Community Call at 3:30 PM UTC. We'll be sharing what the team has been working on and what's next on our roadmap.
1
41
Jun 3
Post-quantum aggregation is slow, but leanVM recently introduced performance improvements that made it much faster.
On Devnet 5, worst-case proposal latency dropped from 2.5s to 1.3s, nearly a 2x improvement over the previous version.
3
4
12
807
Jun 3
We're continuing to explore additional optimizations to push performance even further.
Follow us for more updates.
70
ethlambda retweeted
May 30
Lean Ethereum is moving forward @leanEthereum.
Great work by all the teams. I'm really happy with what @class_lambda has achieved with @ethlambda_lean.
📢📢📢 we are now devnet5 interop!!! 🚀🚀🚀
which is the culmination of the PQ consensus stack that we have been building and iterating on for @ethereum mainnet.
PQ signatures are different from BLS signatures, the current signature machinery of ethereum. But BLS signatures are not Post Quantum secure because breaking elliptic curve cryptography is not an exponential problem for Quantum Computers. But ethereum is being build to last centuries not just decades.
To that end @leanEthereum has been working on PQ signature cryptography using hash based signatures which are one time signatures (OTS), and not plainly aggregatable. Not only that they are huge (~1.5kb).
So this entire challenge started the "devnets" initiatives of leanEthereum. Herein come's the "leanVM" the ZK rail which can aggregate such signatures and makes the entire PQ strategy possible. We have already been through devnet0 to devnet4, and now devnet5!!!
Devnet5 is monumental in that regard, entire block will carry just 1 signature, all aggregated across packed attestations, block signatures (and anything else that will comeup when we backport the spec to mainnet ethereum)
However this is one side of the puzzle, to maintain a stable node, one should be able to repack the attestations from a side branch especially if it moves justification and finalization. and Voila again with leanVM magic, we are able to split the attestations that we need to repack from the combined block signature and repack/re-aggregate them into a new block proposer wants to propose.
This places leanVM as the centrepiece in the entire ethereum post quantum strategy. and the current aim of all the devnets we have been running is to bring a production level performance and demonstration of the capabilities. There are 8 clients that participate in these devnets each bringing value to the table to add stability and robustness (and chaos lol).
Because we know:
"There's many a slip between the cup and the lip"
Goal of all leanEthereum clients is to remove them, one "slip" at a time (or multiple slips at a time lol). Spec isn't good enough, we need production performance, Spec and production design/performance are unequivocally tied. this isn't just a POC network, this is a proposal for ethereum mainnet!
Thats why we have been rigorously running devents, slowly scaling the validators and subnets and discovering and alleviating the issues so that we end up with a production grade PQ signature scheme that ethereum deserves and needs. And this focus is now gonna magnify 1000X now that we believe we are on a spec that can deliver PQ for mainnet.
And mind you, the time of need is gonna strike soon. We not only intend to solve this conundrum for ethereum but propose to even upstream to bitcoin so that we have a PQ standard this entire space deserves.
And all that based on a humble but extremely powerful leanVM that makes the hashbased cryptography workable for the production grade systems like ethereum and bitcoin.
PS: we are currently heavily focused on debugging and scaling devnet4 spec devnets while we have already started to run sims and preliminary interops for devnet5.
So stay tuned for further progress that we leanEthereum teams have been cranking out with a steady but heavy dose ☕️.
May be all matrix is just ☕️☕️☕️
4
6
84
5,603
May 29
It's great to be part of the first devnet 5 interop run!
📢📢📢 we are now devnet5 interop!!! 🚀🚀🚀
which is the culmination of the PQ consensus stack that we have been building and iterating on for @ethereum mainnet.
PQ signatures are different from BLS signatures, the current signature machinery of ethereum. But BLS signatures are not Post Quantum secure because breaking elliptic curve cryptography is not an exponential problem for Quantum Computers. But ethereum is being build to last centuries not just decades.
To that end @leanEthereum has been working on PQ signature cryptography using hash based signatures which are one time signatures (OTS), and not plainly aggregatable. Not only that they are huge (~1.5kb).
So this entire challenge started the "devnets" initiatives of leanEthereum. Herein come's the "leanVM" the ZK rail which can aggregate such signatures and makes the entire PQ strategy possible. We have already been through devnet0 to devnet4, and now devnet5!!!
Devnet5 is monumental in that regard, entire block will carry just 1 signature, all aggregated across packed attestations, block signatures (and anything else that will comeup when we backport the spec to mainnet ethereum)
However this is one side of the puzzle, to maintain a stable node, one should be able to repack the attestations from a side branch especially if it moves justification and finalization. and Voila again with leanVM magic, we are able to split the attestations that we need to repack from the combined block signature and repack/re-aggregate them into a new block proposer wants to propose.
This places leanVM as the centrepiece in the entire ethereum post quantum strategy. and the current aim of all the devnets we have been running is to bring a production level performance and demonstration of the capabilities. There are 8 clients that participate in these devnets each bringing value to the table to add stability and robustness (and chaos lol).
Because we know:
"There's many a slip between the cup and the lip"
Goal of all leanEthereum clients is to remove them, one "slip" at a time (or multiple slips at a time lol). Spec isn't good enough, we need production performance, Spec and production design/performance are unequivocally tied. this isn't just a POC network, this is a proposal for ethereum mainnet!
Thats why we have been rigorously running devents, slowly scaling the validators and subnets and discovering and alleviating the issues so that we end up with a production grade PQ signature scheme that ethereum deserves and needs. And this focus is now gonna magnify 1000X now that we believe we are on a spec that can deliver PQ for mainnet.
And mind you, the time of need is gonna strike soon. We not only intend to solve this conundrum for ethereum but propose to even upstream to bitcoin so that we have a PQ standard this entire space deserves.
And all that based on a humble but extremely powerful leanVM that makes the hashbased cryptography workable for the production grade systems like ethereum and bitcoin.
PS: we are currently heavily focused on debugging and scaling devnet4 spec devnets while we have already started to run sims and preliminary interops for devnet5.
So stay tuned for further progress that we leanEthereum teams have been cranking out with a steady but heavy dose ☕️.
May be all matrix is just ☕️☕️☕️
1
1
4
252
May 29
Ethlambda is one of the first clients running full-block aggregation, we previously made a thread talking about it: x.com/ethlambda_lean/status/…
May 26
Full-block aggregation is coming to devnet 5.
We've been running initial tests on our servers (shown on the last community call). Here's a look at the dashboard.
1
115
May 29
Our Community Call recording is up, go give it a watch. We walked through our latest release, key highlights, and what's next for the team.
May 29
Ethlambda Community Call x.com/i/broadcasts/1YGNrrRLP…
1
60
May 28
Community Call tomorrow, live on X at 3:30 PM UTC. Fresh updates from the team, a look at recent progress, and what we're building toward. Join us.
2
85
May 26
Full-block aggregation is coming to devnet 5.
We've been running initial tests on our servers (shown on the last community call). Here's a look at the dashboard.
2
5
13
1,183
May 26
We're currently working on bug fixes and chasing performance improvements on block building, the current bottleneck.
1
1
42