leandro.ferrigno

Head of Engineering at @class_lambda. Learning about starks
Professor at @ingenieriauba
Needed a pro account that do not talk about football or politics

[LambdaClass @class_lambda]

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.

[ethrex @ethrex_client]

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.

[leandro.ferrigno @lean_knack]

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 💪

[ethrex @ethrex_client]

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.

[Andrej Karpathy @karpathy]

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.

[Fede’s intern 🥊 @fede_intern]

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.

[leandro.ferrigno @lean_knack]

@ethrex_client See you there!

[leandro.ferrigno @lean_knack]

gm.

[ethlambda @ethlambda_lean]

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.

[leandro.ferrigno @lean_knack]

@fede_intern @AmMuroch @tempo Yes I can, @AmMuroch can you dm me?

[leandro.ferrigno @lean_knack]

Everything was so smooth we forgot to announce 😄
Great work done by the incredible @class_lambda team

[ethrex @ethrex_client]

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.

[Fede’s intern 🥊 @fede_intern]

https://t.co/5F9xUuRJY8

[leandro.ferrigno @lean_knack]

What a week!

Thanks everyone for the support, hope you'd enjoyed it

[ethrex @ethrex_client]

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

[Fede’s intern 🥊 @fede_intern]

Community is not a group of people clapping in agreement. It’s the opposite. It’s a group of different people with conflicting interests trying to find the best outcome for everyone. The fact that there is strong debate in CT is good.

I’ve been thinking a lot about what has happened to @ethereum over the last two years: the slowdown in execution, the loss of confidence, and the shrinking influence across the industry. Things have improved recently, and Buenos Aires Devconnect was miles ahead of Bangkok Devcon, but the core problem remains unresolved. The initiatives proposed so far are voluntaristic and depend on a few individuals rather than structural changes. I just launched my blog and I’m writing a longer essay with concrete examples and a more philosophical angle. This is the first draft of the core thesis.

At the center of everything there is a contradiction: harmony vs competence.

The leadership thesis, and @VitalikButerin, is simple: power corrupts, so the only safeguard is preventing anyone from gaining power. I understand the concern. But the solution is where we diverge.

At one point many important people of Ethereum even stopped tweeting. Their answer has been to prioritize harmony above all else. That’s why the protocol barely changed after the Merge and why the gas limit stayed low. If nothing can change, no new actors can emerge. The mission became: avoid disruption, avoid conflict, avoid the rise of a new corrupt leader.

From there you get alignment politics instead of open debate. Advancement through proximity and approval rather than measurable execution. The mechanism becomes social, not technical. It’s the opposite of what made Linux succeed. Linux thrived because Linus Torvalds only cared about code quality and the best ideas winning.

This has a tragic consequence: when you suppress discussion and reward alignment out of fear of new leaders emerging, you destroy the conditions for new blood to arise. Innovation slows down to preserve harmony.

Progress requires conflict, science advances through disagreement, engineering through iteration, and markets through competition. Ideas and people HAVE to collide to find the best idea possible. Systems that suppress conflict stagnate because hierarchy replaces merit. @ameensol has been saying something similar but I don't agree with his take about the fact that this is related with socialism. To me the core problem is the destruction of the feedback loop between decisions taken by leaders and the outcomes they get.

Ethereum cannot remain global, open, and relevant while avoiding debate. Harmony without productive conflict becomes centralization. Avoid conflict and you avoid improvement; avoid debate and you avoid new talent.

Vitalik wrote on March 1st, 2025: "What Ethereum needs is a lot of young blood who share the cypherpunk vision. All OGs are jaded. It’s on the next generation now." He’s right. But the reason this is happening is because of the incentive structure created by the leadership itself.

Like in Brave New World, systems built to numb conflict only work if there is no outside competition. Ethereum no longer lives in a world without rivals. The crisis at the end of last year and start of this year happened because Solana was winning market share. Ethereum has to adapt to this reality.

The idea that power corrupts is true, but it is also historically used by leaders to gatekeep, prevent renewal, and retain power.

The funny thing is that I agree with Reth and @paradigm on the roadmap priorities. In that sense, I’m closer to their views than to the historical EF leadership. I always believed that if Ethereum doesn't acclerate we will lose. The difference is that I believe these debates must happen inside Ethereum rather than in another L1, openly, and we need to push for structural change.

Pointing these things out has a cost. One of the latest defenses against our arguments has been claiming we seek attention or that we are troublemakers. Some of the people we used to talk with also stopped answering. Gladly many, if not most actors, started telling us that we are right but they can't say things openly because this has a cost for them too.
This only proves the point: there is a culture of preventing debate to maintain the status quo. Anyone who knows us knows we defend what we believe, right or wrong, not for attention or financial motivation. We’ve worked across multiple industries without issue and with long-term clients. We care about productivity and delivery, period.

When people join Lambda they read @RayDalio's ideas. Dalio believes the highest performing organizations run on idea meritocracy driven by radical truth and radical transparency. Everyone speaks openly, nothing is hidden, the best ideas win regardless of hierarchy. Mistakes and disagreements are embraced because being challenged is the path to improvement. Suppressing truth out of fear of social consequences is the greatest tragedy that prevents excellence. I believe Ethereum is suffering from exactly this.

At @class_lambda we believe in @ethereum as the unbiased verifiable computer. We believe this mission is bigger than any person. And we will fight for what we think is right. If you want to be a global protocol and you want new cypherpunk blood then accept the fact that they will criticize you and debate openly rather than avoiding it.

[Fede’s intern 🥊 @fede_intern]

Thanks @eth_proofs for letting us share our love for ZK and @ethereum.

Our CTO @lean_knack spoke about @ethrex_client. We want everyone to integrate their zkVM with us. We made it super easy.

We already integrated with @SuccinctLabs, @RiscZero, @ziskvm and we’re integrating with @brevis_zk and @openvm_org.

We will do everything we can to make Ethrex the best Rust execution client and the easiest and fastest client to prove. I highly recommend you checking it out!

[Ethproofs @eth_proofs]

Getting ready to cook 🧑‍🍳

“The Demo”

[leandro.ferrigno @lean_knack]

Thanks for being there!

[RJ 🟩 @rj_aligned]

.@lean_knack on why another execution client?

[leandro.ferrigno @lean_knack]

Proud to be there!

[Ethproofs @eth_proofs]

SATURDAY NOV 22ND: Ethproofs day is thrilled to host
@lean_knack from @class_lambda - who will be presenting his talk:

"Expanding Ethereum's Proving Landscape with Ethrex (@ethrex_client )"

[leandro.ferrigno @lean_knack]

For those in Buenos Aires, lets meet!

[LambdaClass @class_lambda]

1/ Week’s gonna be packed. Here’s our lineup for DevConnect 👇

[leandro.ferrigno @lean_knack]

@sunbh_eth @fede_intern @rj_aligned Y dale y dale y dale Boca dale!

[leandro.ferrigno @lean_knack]

Excited to be there!!!
See you around