leandro.ferrigno (@lean_knack) header
leandro.ferrigno (@lean_knack) profile picture

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
Photo by leandro.ferrigno (@lean_knack)Photo by leandro.ferrigno (@lean_knack)Photo by leandro.ferrigno (@lean_knack)Photo by leandro.ferrigno (@lean_knack)Photo by leandro.ferrigno (@lean_knack)Photo by leandro.ferrigno (@lean_knack)Photo by leandro.ferrigno (@lean_knack)Photo by leandro.ferrigno (@lean_knack)Photo by leandro.ferrigno (@lean_knack)Photo by leandro.ferrigno (@lean_knack)
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
10
7
2
61
5,754
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/
1
9
2
45
2,260
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/
2
1
9
1,648
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/
50
45
22
315
96,820
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.
2
4
9
914
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.
The first batch of Guardian operators on Miden is here: OpenZeppelin LambdaClass Gateway Private accounts are powerful. But if they’re going to be usable in real apps, they need recovery, synchronization, coordination, and serious operators behind the infrastructure.
2
4
1
18
1,552
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.
Last week, ethrex joined its first Ethereum devnet ever: devnet-bal-2. A few days later, Hive tests for devnet-bal-3 went live, and ethrex is already the most compliant execution client: ethrex: 900/1028 (87.5%) nimbus: 630 (61.3%) erigon: 626 (60.9%) nethermind: 585 (56.9%)
2
8
12
1,766
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.
1,594
4,650
1,113
36,818
5,175,930
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.
What if we could make the Ethereum transaction journey and block construction process faster, cheaper, more flexible, censorship resistant, & robustness? What if we could do this today? This is what the Blockspace Forum is about. 🧵👇
23
38
6
228
29,104
leandro.ferrigno retweeted
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.
Vitalik Buterin: "if I did not go to an in-person event for one and a half years and I only read twitter every day… that would almost certainly lead me to rage quit and retire and publish a hundred tweets saying why I think the whole crypto space is evil and deserves to burn." 🧵 let's unpack this with direct quotes from his fireside chat with Roger Dingledine from @torproject at @FundingCommons in Buenos Aires
33
29
3
161
34,231
leandro.ferrigno retweeted
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!
18
15
2
100
11,256
leandro.ferrigno retweeted
Getting ready to cook 🧑‍🍳 “The Demo”
9
15
9
138
25,815
leandro.ferrigno retweeted
.@lean_knack on why another execution client?
3
7
23
1,598
leandro.ferrigno retweeted
Our home for DevConnect week is ready. Trust, it delivers.
2
5
1
29
2,181
📢📢For the past year, we've been stealthily developing a #metroidvania We have a 1 hour Early Access version available that we're excited to share with you! Play now!! lambdaforge.itch.io/kenzu Comments are appreciated 😻
2
16
3
36
4,876
leandro.ferrigno retweeted
𝙕𝙆 𝘼𝙍𝘾𝘼𝘿𝙀: 𝙉𝙊𝙒 𝙇𝙄𝙑𝙀 𝙊𝙉 𝙈𝘼𝙄𝙉𝙉𝙀𝙏 If you're one of the lucky 700 people with exclusive early access you can now mint your ZK Arcade Ticket NFT to start playing and earning points 🕹️ Here's everything you need to know to play:
59
62
148
313
73,087
leandro.ferrigno retweeted
Replying to @class_lambda
@class_lambda 👇 stands to protect Argentina’s crypto space and truly unleash its potential to improve our economy and finances. We just need to do the reforms the right way.
I have just concluded a board meeting at @class_lambda. By a strong majority, we have resolved to initiate legal action in Argentine courts should any decision move forward to establish a special economic zone under the management or control of @crecimientoar or its stakeholders like @juanbenet. We're ready to fight this. Creating an economic zone administered by @crecimientoar with the intent to subsequently launch a token is not a legitimate or responsible path to regulatory innovation. On the contrary, it undermines credibility, discredits genuine reform efforts, and conflates public interest regulation with private gain. Leaders from @crecimientoar have started a fundraising round at a $20 million valuation through a SAFE with token warrants, closing in the coming days, with a larger round planned for November. Such actions raise serious governance and ethical concerns that merit transparency and public scrutiny. The $LIBRA case already set a damaging precedent that hinders meaningful legislative reform. We cannot allow personal interests to obstruct broader policy changes in a G20 nation with one of the world’s most active crypto communities.
There's a new version of this post
2
3
16
1,301
Last week, we mentioned that we would like to organize with @alignedlayer and @class_lambda a cryptography event for @EFDevcon. We opened this form to get to know about people that will be interested in participating and have an idea on topics which will be interesting for discussion. If interested fill out the form below 👇
2
7
2
31
2,972
leandro.ferrigno retweeted
1/ We're proud to announce a new strategic partnership between LambdaClass and @nousresearch to build decentralized, open-source AI infrastructure. Here's what this means for the future of artificial intelligence 👇
1
3
15
1,611