Head of Engineering at @class_lambda. Learning about starks Professor at @ingenieriauba Needed a pro account that do not talk about football or politics
Joined February 2014
- Tweets334
- Following414
- Followers609
- Likes817
leandro.ferrigno retweeted
Discussing with the guys on the latest talks about zkvms, formal verification and others @class_lambda @ethrex_client @alignedlayer
Still one more day to go! If you're at @EFDevcon, any of these topics interest you, and we haven't met yet, please reach out!
See you! 🪷 🇮🇳
(5/5)
The DeFi ecosystem keeps growing, with PropAMMs gaining traction. We've been talking with many teams about the work we've been on this and the many opportunities to onboard new projects.
If you don't know what I'm talking about, check this out:
blog.lambdaclass.com/announc…
(4/5)
Learning a lot and discussing all the work being done around formal verification. So many teams are pushing to make software more secure in the AI era, and there's a lot happening in this space.
(3/5)
Great to catch up with fellow Ethereum core developers and all the EF people in real life. Also very happy to see how @ethrex_client is finding its place in the ecosystem and how @ethlambda_lean is getting more and more recognition.
(2/5)
Amazing journey at @EFDevcon so far. I've met so many friends and colleagues, all pushing to make Ethereum better, faster, and more secure, and ready for what's coming next.
(1/5)
Day 3 at @EFDevcon and I still haven't learned which way to enter a room and which way to exit it. – at Mumbai, India
leandro.ferrigno retweeted
Ethlambda is in the house 🪷🇮🇳
Be one of the first to try our new consensus client.
Reach us out at @EFDevcon , DM us so we meet
We are at @EFDevcon!
We’d love to meet stakers looking to diversify their stack with ethrex, one of Ethereum’s fastest execution clients, built in Rust.
Come chat about running ethrex in your setup. DM us to meet up!
Ready for today's workshop at @EFDevcon .
Lets meet if you want to meet and chat about @ethrex_client or @ethlambda_lean . W/ @ivanlitteri
leandro.ferrigno retweeted
Congratulations to @ethlambda_lean on v1.0.0!
We're proud to see lessons from building ethrex help shape another Ethereum client. With ethlambda supporting the beacon chain, we can work together on improvements across Ethereum's execution and consensus layers.
ethlambda v1.0.0 is here!
Our Lean Ethereum consensus client now has full beacon chain support, including Gloas.
We're running it on mainnet, Sepolia, Hoodi, and Platåberget. Our Sepolia validators successfully transitioned to Glamsterdam without a single issue.
Built in Rust, ethlambda brings together what we've learned from Lean Ethereum devnets and years of developing ethrex. With @ethrex_client on execution and @ethlambda_lean on consensus, we're contributing to client diversity across both layers of Ethereum.
Next, we're pushing performance further, participating in Hegotá interoperability devnets, and working to bring post-quantum cryptography to the beacon chain.
Explore ethlambda and what we're building next in the full announcement: blog.lambdaclass.com/ethlamb…
leandro.ferrigno retweeted
Ok all is ready for Monday now! Come and do stuff on our mainnet! We have an awesome wallet, we are connected to many chains already and maybe there is something like fomo3d
Mumbai is getting closer and we are wrapping up our @EFDevcon talk.
See you there friends! cc: @ivanlitteri
Ps: Sorry about the mess but Boca and hungry Luffy drive me – at Buenos Aires City Region, Argentina
leandro.ferrigno retweeted
From our point of view, yesterday's ACDC decision on EIP-8025 was the wrong call for Ethereum's long-term interests.
EIP-8025 proposes optional execution proofs, a first step toward the zkEVM roadmap, and the client teams declined to commit to it.
Framing the proposal as an "optional feature" may have worked against it. Calling something optional makes it easy to dismiss as low priority. To be clear, it was a proposal, and proposals can be accepted or rejected; nothing obligated anyone to approve it. And it is true that this feature does not inherently require a hard fork. But that is precisely what makes the question of commitment unavoidable: with nothing at the protocol level forcing the work to happen, progress depends entirely on whether people are actually assigned to it. Execution proofs only become real if client developers implement them, if testing teams build the coverage they need, and if DevOps keeps the infrastructure running. Declining to prioritize the proposal means the work simply does not happen. The optionality was meant for operators, those choosing whether to enable execution proofs, not for the people deciding whether the work happens at all. Operators should be able to opt in regardless of which client they run, and a decision taken without all teams present cannot credibly settle a question that depends on all teams delivering.
Optional proofs are the foundation of Ethereum's zkEVM roadmap. That roadmap is complex, and it demands extensive integration and testing across teams. Getting there requires a shared, sustained commitment.
We need to test under realistic conditions and investigate failures before consensus depends on proofs, and that work should proceed alongside research into mandatory proofs. Every integration bug we uncover now is one we won't be discovering after consensus depends on it. The more groundwork we lay today, the more bandwidth we have later for the challenges specific to mandatory proofs, including the ones we haven't found yet.
hegota scoping ⚡
ACDC #189 - ultra tl;dr
DFI:
🪓 7716: Anti-Correlation Attestation Penalties
🪓 8025: Optional Execution Proofs
🪓 8359: Beacon Block Reporting Field
🪓 8371: RowDAS
generally liked EIPs, but teams found that they weren't urgent enough to schedule (7716, 8359, 8371) or that they could be tackled without CFI (8025)
5 more EIPs to assess next meeting
video and summary:
forkcast.org/calls/acdc/189/
leandro.ferrigno retweeted
LAMBDA ALL THE THINGS
We're sponsoring the first Hardware Hackathon at @Exactas_UBA.
On October 23–24, teams of 4 will have two days to build and present a physical product. No hardware experience required: the event starts from the basics.
Applications are open and the event is free.
Apply: comcom.dc.uba.ar/hackaton/
We have @ethrex_client running on Platåberget, the first public Glamsterdam testnet.
And for Hegota, among other things we are running a public testnet for the EIPs behind Ethereum's privacy roadmap.
RPC, explorer, and tooling notes: faucet.privacy.ethrex.xyz
Today is a great day. After being mainnet ready for almost a year, we got the chance not only to give our take on the future of Ethereum but to actually do it, with @ethrex_client as the default testing area for the execution EIPs.
Following up on our execution EIP tier list, we wanted to share our combined execution and consensus rankings for Hegota. We've followed the same EF Protocol scoring system and tier definitions for both lists.
We'd also like to make a special mention of the post-quantum-ready deposit contract proposal. It didn't make it onto the Hegota EIP selection list, but we think proposals like this one should be included in the fork to prepare validator deposits for future post-quantum credentials.
We'll expand on our thoughts about Hegota and the reasoning behind our rankings in the blog post we're preparing.
