LambdaClass

It’s been a couple of weeks since the first official Frame Transactions devnet launched.

frames-devnet-0, which includes only EIP-8141, will soon give way to frames-devnet-1, adding EIP-8250, EIP-8272, and EIP-7906.

The execution-spec tests for frames-devnet-1 (frames-devnet@v1.0.0) came out today, and ethrex already implements the required changes and passes the full suite!

We’ve been working on these EIPs for a while, and it shows 😉. Getting ready for devnets is starting to feel routine 💅.

ethrex continues to push Ethereum client performance forward.

Leading stateful Glamsterdam repricing benchmarks and in the top 3 for the compute ones, with more optimizations on the way.

Ethrex Community Call x.com/i/broadcasts/1…

Don't forget, our Community Call is tomorrow at 2:30 PM UTC on X. We'll cover what we've been shipping and where we're headed next.

ethrex handled Glamsterdam on Sepolia smoothly across 100 validators and multiple setups.

One more step toward Hoodi and mainnet.

we just made @ethrex_client again the fastest client in @ethereum. i've always said, lambda would deliver and push the boundaries of ethereum.

after a couple of months focused on Glamsterdam hardening and Hegota prototyping, including hosting several public testnets for the most important EIPs coming in Hegota, we've turned our attention back to performance. this doesn't mean we're stepping away from that work, where we still have a lot to contribute.

The early results are very promising. In just a couple of days, we brought block processing time down from ~40ms to ~26ms in mainnet, making ethrex the fastest client once again. The image below compares how we perform today (ethrex-baseline) with what we've been cooking (ethrex-testing).

congrats @class_lambda, i'm proud of the team we've built. i love working with people that are way smarter than me.

thanks @ethereumfndn for the constant support.

Back to making @ethrex_client faster. Great work by the team pushing performance forward once again.

LambdaVM is a RISC-V zkVM small enough for one person to audit end to end.

You give it a program, you get a STARK proof that it ran correctly. In collaboration with @class_lambda and @3miLabs.

Here's why we built it this way 🧵

A proof convinces a verifier.
A spec convinces a person.

Lambda VM gives you both. ~60k lines of Rust, one chip per file, each next to its spec.

Being built in collaboration with @class_lambda and @3miLabs

Ethrex Community Call x.com/i/broadcasts/1…

ethrex v29.0.0 hardens how a node serves and verifies block access lists. Every Sepolia node starts exchanging them at the Glamsterdam fork on 6 October at 13:53:36 UTC (timestamp 1791294816), so it is worth running this release even if you already upgraded to v28.0.0 for the fork. Mainnet and Hoodi have no Glamsterdam time scheduled and are not affected.

⚠️ The stateless input format changed: sender public keys are no longer part of it, following the execution-specs change, and the stateless-validator guests move to ERE v0.18.1. Anything that produces or consumes ethrex's stateless input, such as external provers and zkEVM integrations, has to move to this release together. Node operators who do not use the stateless input are unaffected.

Serving access lists is now bounded in both work and memory, and the eth/71 request counts toward the same per-peer rate limit the snap/2 one already did. Responses to requests a connection never sent are dropped before they are decoded, and a block whose access list exceeds the EIP-7928 item cap is rejected without processing that list first. On the receiving side, an eth/71 access list is checked against the header commitment across the whole full-sync path, as EIP-8159 requires, and a peer that sends one that does not match is penalized.

Also in v29.0.0:
- Sync: snap sync pivots onto the forkchoice head instead of a guessed block number, and a canonical block is never marked bad because re-executing it failed.
- Engine API and RPC: engine_newPayloadWithWitnessV4, and the raw transaction getters return the EIP-2718 envelope.
- Performance: the bytecode cache budget rises from 256 MiB to 2 GiB, with random eviction and per-entry overhead accounting. It is a ceiling rather than a reservation, since the cache only grows with code that blocks actually load, and --code-cache-size (ETHREX_CODE_CACHE_SIZE) lowers it on memory-constrained hosts. Block access list accounts are warmed in chunks, and mempool prewarming stops filling a slot once it reaches the code cache's budget.

If you run ethrex on Sepolia, run this one before the fork: v28.0.0 is the minimum that follows it, and v29.0.0 adds the access list hardening on top. Everyone else, upgrade at your convenience. No resync is needed.

We also left something in the logs for the first Amsterdam block. We are not going to spoil it, so watch your node cross the fork.

Our consensus client is now adding support for @ethereum mainnet. Client diversity is important for us, and for Ethereum's future.

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/

Thanks @drakefjustin for sitting down with us to discuss your vision and roadmap for Ethereum. Really enjoyed the conversation.

We have a lot of confidence in your leadership and in Ethereum’s future.

Lambdaclass PropAMM Router new audited version, now live on mainnet. Same address, same interface.

Access all ethereum PropAmm liquidity, with JIT requoting for optimal swaps and spoofing protection.

Full write-up: blog.lambdaclass.com/lambdaclass-pr…

We spent the last few days at the 29th Argentine Conference on Structural Engineering at the UNC Cultural Center.

We presented our work on a structural engineering agent built on a verified solver, and introduced Stabileo (stabileo.com/es/) to universities across Argentina. Several researchers and academics showed interest in contributing to or using the project. AI is becoming a much more concrete topic in civil engineering.

Today we had the honor of attending the thesis defense of one of the students from our scholarship program at @Exactas_UBA.

His thesis, “Preference Systems in LLMs: Effects of Textual Perturbations and Profile Elicitation on Consistency and Robustness in Decision-Making”. With LLMs becoming more capable and influential, research into how their preferences and values behave under different conditions is becoming increasingly important.

Our program ran for a year and a half across three editions, supporting students in the final stages of their degrees and their research work.

It was great to be there and see that journey come full circle. Congratulations, Augusto!

Ethrex Community Call x.com/i/broadcasts/1…

Bread is here.

This is a major milestone for @0xMiden and for making privacy practical and accessible. Proud that our team contributed to the technology behind it and helped bring this vision closer to users.

The Research Center for Cryptography and Distributed Systems just kicked off a new study group, a continuation of their seminar on Coding Theory, Low-Degree Testing, and PIOPs, starting with a session on STARKs.

We hosted it at our office, with Lambdaworks team taking part in the discussion.

ccsd.uba.ar