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
- Tweets321
- Following413
- Followers598
- Likes800
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/
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.
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
leandro.ferrigno retweeted
Also, @ethrex_client has a testnet for Frames, FOCIL plus companion EIPs that together allow privacy protocols on top of Ethereum to behave as full first-class citizens:
xitter.cf/ethrex_client/status/2…
We are running a public testnet for the EIPs behind Ethereum's privacy roadmap, built on top of Glamsterdam.
It runs EIP-8141 (Frame Transactions), EIP-8250 (Keyed Nonces), EIP-8272 (Recent Roots), EIP-7805 (FOCIL), and EIP-8369 (VOPS profiles), each implementation up to date with its spec. The frames implementation matches the latest execution spec tests release.
Anyone can sync, peer, transact, and use the faucet to fund test accounts. The only permissioned part of the network is validator entry. If your client team is working on any of these EIPs and wants to validate, reach out to us, and we'll get you set up with deposit tokens.
RPC, explorer, and tooling notes: faucet.privacy.ethrex.xyz/
Government institutions powered by Ethereum using @ethrex_client
Sovra is out there, and getting bigger every day.
Nuevo León launched NLínea, its state digital wallet, together with Sovra. 🇲🇽
NLínea lets people carry official credentials on their phones and present them when needed, with biometric authentication and verifiable credentials issued by the state.
The wallet connects with Nuevo León’s digital service portal, which already brings together 700+ government services.
The launch was announced at the 2nd Northeast Regional Meeting, organized by @nuevoleon and @ciapem in Monterrey.
Governor @samuel_garcias opened the event, and @Marielasvmx presented the state’s progress in digital transformation.
We’re proud to be building NLínea together with Nuevo León. Thank you to the teams at @nuevoleon for the trust and collaboration that made this possible, and to our partners at @class_lambda and @alignedlayer for helping build the infrastructure behind it.
A meaningful step toward a more digital, accessible government. 🇲🇽
leandro.ferrigno retweeted
You can now run an ethrex node on Platåberget, the first public Glamsterdam testnet. Sync your node in less than 2 minutes!
Support landed on main today, so it's a source build for now:
cargo run --release --bin ethrex -- --network plataberget
The Amsterdam fork went live on Platåberget on August 20, which makes it the earliest public network for testing Glamsterdam.
We've been running a node there ourselves: following the tip and executing Platåberget's ~100 Mgas blocks at 17 Ggas/s avg. in our measurements.
Then pair it with a consensus client with Platåberget support. The node snap syncs by default, which is what makes the 2-minute join possible; a full sync from genesis, executing every block, took about 40 minutes in our tests. If you'd rather not build from source, next week's release will ship it prebuilt.
Bug reports and feedback are welcome on the repo.
leandro.ferrigno retweeted
Excited to be part of the first batch of Guardian operators on @0xMiden, alongside @OpenZeppelin and @gateway_eth. Miden is redefining what privacy looks like. That's going to make institutional onboarding to crypto a lot easier.
leandro.ferrigno retweeted
When we announced BAL Devnet 3 support, the tests were just starting. Today, ethrex is at 1040/1040 tests passing for 6 consecutive days.
Only two EL clients at 100% right now.
Native rollups are becoming a reality.
It’s great to see these initiatives moving forward, and we couldn’t have done it alone.
Kudos to the team driving this forward and to everyone who has supported it along the way.
There’s still more work ahead 💪
We've been working with @kevaundray and @ladislaus0x from @ethereumfndn and @donnoh_eth from @l2beat on a proof of concept of EIP-8079 (native rollups) using @ethrex_client.
Native rollups reuse Ethereum's own execution to verify L2 state transitions. No ZK circuits, no fraud proofs, no complex proof systems to maintain. Every L1 upgrade is automatically inherited. Any bug in the verification is also a bug in Ethereum itself.
The demo shows a full end-to-end native rollup:
- L2 blocks settled to L1 via the EXECUTE precompile
- L1→L2 deposit
- Contract deployment and cross-layer calls
- L2→L1 withdrawal with MPT proof claim
- Blockscout verifying EXECUTE precompile calls on L1
Try it yourself. Instructions in the PR below.
leandro.ferrigno retweeted
It is hard to communicate how much programming has changed due to AI in the last 2 months: not gradually and over time in the "progress as usual" way, but specifically this last December. There are a number of asterisks but imo coding agents basically didn’t work before December and basically work since - the models have significantly higher quality, long-term coherence and tenacity and they can power through large and long tasks, well past enough that it is extremely disruptive to the default programming workflow.
Just to give an example, over the weekend I was building a local video analysis dashboard for the cameras of my home so I wrote: “Here is the local IP and username/password of my DGX Spark. Log in, set up ssh keys, set up vLLM, download and bench Qwen3-VL, set up a server endpoint to inference videos, a basic web ui dashboard, test everything, set it up with systemd, record memory notes for yourself and write up a markdown report for me”. The agent went off for ~30 minutes, ran into multiple issues, researched solutions online, resolved them one by one, wrote the code, tested it, debugged it, set up the services, and came back with the report and it was just done. I didn’t touch anything. All of this could easily have been a weekend project just 3 months ago but today it’s something you kick off and forget about for 30 minutes.
As a result, programming is becoming unrecognizable. You’re not typing computer code into an editor like the way things were since computers were invented, that era is over. You're spinning up AI agents, giving them tasks *in English* and managing and reviewing their work in parallel. The biggest prize is in figuring out how you can keep ascending the layers of abstraction to set up long-running orchestrator Claws with all of the right tools, memory and instructions that productively manage multiple parallel Code instances for you. The leverage achievable via top tier "agentic engineering" feels very high right now.
It’s not perfect, it needs high-level direction, judgement, taste, oversight, iteration and hints and ideas. It works a lot better in some scenarios than others (e.g. especially for tasks that are well-specified and where you can verify/test functionality). The key is to build intuition to decompose the task just right to hand off the parts that work and help out around the edges. But imo, this is nowhere near "business as usual" time in software.
leandro.ferrigno retweeted
A few weeks ago I said there was a seismic change in Ethereum's social layer about to happen. It's happening.
Multiple big infrastructure players that most users don't know about are starting to collaborate and build together, doubling down on ETH and the Ethereum network. Follow @blockspaceforum to keep up with it.
The biggest block builder (@titanbuilderxyz), the biggest relay (@ultrasoundmoney), @ETHGasOfficial, @Commit_Boost (38% network adoption), @QuasarBuilder, @primev_xyz, @nuconstruct, @blocknative, @fabric_ethereum, researchers from the @ethereumfndn, and many others are all coordinating. Many of us realized that they had to team up and work closely together to make our opinions stronger and speed up our ability to deliver.
In the last 5 years @class_lambda built many of the most relevant zkVMs and Ethereum L2s. Last year we went all in on @ethereum L1.
In a year we built @ethrex_client, one of the fastest production ready execution clients at about 60k lines of code. We're coordinating with big stakers and the MEV pipeline to grow its adoption while also shipping multiple products around it.
We're building a new RISC-V zkVM with @alignedlayer and @3miLabs that I think will become a standard for L1 proving and @eth_proofs in the short term.
We're working on @leanEthereum by building our own @ethlambda_lean client.
We helped develop the @Commit_Boost sidecar that standardizes communication between validators and third party protocols. We're happy to have helped build a critical piece of software that is now running on 38% of the Ethereum network.
We also started collaborating with @titanbuilderxyz on different things under @kubimensah's lead. Hopefully soon we'll be working closely with @alextes and @ultrasoundrelay too!
There's more I want to share but can't yet. For now I can say that @class_lambda is part of the @blockspaceforum process and I'm very excited about what's coming.
Keep an eye on what we will be doing, I promise it's gonna get interesting.
gm.
gm.
At @class_lambda we are now building a new lean Ethereum consensus client called ethlambda. The goal is simple: help build the Ethereum cathedral that future generations will rely on.
Everything was so smooth we forgot to announce 😄
Great work done by the incredible @class_lambda team
The @ethereum Fusaka Upgrade is live on mainnet, fully supported and performing as expected on the Ethrex Client.
We're proud to be part of this fork and are already looking toward Glamsterdam with even greater commitment.
Huge thanks to everyone whose work brought us here.
What a week!
Thanks everyone for the support, hope you'd enjoyed it
DevConnect brought the ecosystem together in our beautiful Buenos Aires.
With a functional client and strong performance in hand, we were ready to contribute. We hosted events, joined key conferences, shared our work, and connected with many teams pushing the ecosystem forward.
Here's our recap of the week 👇
1/7
