Please turn JavaScript on
LambdaClass Blog icon

LambdaClass Blog

Following LambdaClass Blog's news feed is very easy. Subscribe using the "follow" button on the top right and if you want to, choose the updates by topic or tag.

We will deliver them to your inbox, your phone, or you can use follow.it like your own online RSS reader. You can unsubscribe whenever you want with one click.

Keep up to date with LambdaClass Blog!

LambdaClass Blog: LambdaClass Blog

Is this your feed? Claim it!

Publisher:  Unclaimed!
Message frequency:  0.12 / day

Message History

During the last two weeks, cryptographic research moved to Rome with a host of events: May 7th featured the return of zkSummit 14, May 9th-10th had zkProof 8 and several Eurocrypt side-events and from the 11th until the 13th Eurocrypt 2026 took place. Lambda, together with Aligned, and the Center on Cryptography and Distributed Systems of the University of Buenos Aires (


Read full story

In a previous post, we explained how LMD-GHOST worked. This post is about its problems, and how Goldfish fixes them.

Latest Message Driven GHOST (LMD-GHOST) is the fork-choice rule of Ethereum's beacon chain. Balancing a...


Read full story

Last week, just over a hundred Ethereum core contributors gathered in Longyearbyen, Svalbard, for the Soldøgn interop: a single-track week of focused, multi-client work on the Glamsterdam network upgrade, above the 78th parallel, under ...


Read full story

Stakers told us they want to switch between execution clients without friction, sometimes leaving a node off for several days before switching back. Over the last month we shipped a series of fixes across ethrex's P2P stack. Restarts are more reliable. Bandwidth consumption dropped by a meaningful factor on every node we run. Header downloads continue across imperfect peers, ...


Read full story

Devnet 4 of the post-quantum leanConsensus testnet introduced recursive signature aggregation through leanMultisig. The change is good for the network (fewer proofs to verify per block), but it pushed enough work onto aggregators that our node started missing slots and slipping on finalization.

Two changes got us back to parity: moving aggregation off the hot path, and...


Read full story