tag:github.com,2008:https://github.com/lambdaclass/lambda_ethereum_consensus/releases 2025-04-23T19:28:53Z tag:github.com,2008:Repository/664716838/v0.1.0-alpha.1 2025-04-24T21:12:54Z <p>We're releasing version v0.1.0-alpha.1 of the <code>Lambda Ethereum Consensus Client</code>, marking a step stone of our work through <code>deneb</code> and prior forks before beginning the Electra implementation.</p> <h3>Status</h3> <p>This release represents a spec-wise complete implementation of the Ethereum consensus client in Elixir (<a href="https://github.com/lambdaclass/lambda_ethereum_consensus/tree/main/docs/specs#:~:text=..-,beacon%2Dchain.md,-docs%3A%20remove%20broken">beacon chain</a>, <a href="https://github.com/lambdaclass/lambda_ethereum_consensus/blob/main/docs/specs/fork-choice.md">fork_choice</a>, <a href="https://github.com/lambdaclass/lambda_ethereum_consensus/blob/main/docs/specs/p2p-interface.md">p2p</a> and <a href="https://github.com/lambdaclass/lambda_ethereum_consensus/blob/main/docs/specs/validator.md">validators</a>), but its not fully functional due to known issues and performance bottlenecks on bigger networks (like Holesky and Mainnet). It's purpose is to serve as a checkpoint in our development process and contains known limitations that will be addressed in future versions.</p> <p>The following is a high-level overview of the current status and known limitation, we are still in development phase but wanted to have a clear checkpoint of the current situation, for more information you can look the <a href="https://github.com/lambdaclass/lambda_ethereum_consensus/issues">issues</a>.</p> <h3>Current Implementation</h3> <p>The client currently includes:</p> <ul> <li>A working implementation of the beacon chain spec with it's spec-test passing</li> <li>A working implementation of the p2p communication tested in Kurtosis and Sepolia.</li> <li>A working implementation of Validator duties as part of the node (not a separate validator client) tested on Kurtosis.</li> <li>Testing infrastructure with spec-test, Kurtosis and an initial Assertoor check</li> </ul> <h3>Known limitations</h3> <p>We have some known limitation and we plan to tackle them as soon as we finish the electra upgrades:</p> <ul> <li>Sepolia long running sessions with known issues that stop the node <ul> <li>This test check the node stability regarding to p2p and state transitions, not validator duties</li> <li>Sessions have been running for a week in the best cases</li> </ul> </li> <li>Performance optimization needed specially in block and epoch processing (most notable in Holesky and Mainnet)</li> <li>Assertoor test enhancement</li> <li>Full API support</li> <li>Other lesser priority missing components (like lightclient's support)</li> </ul> <p><strong>Note:</strong> Sepolia sessions were run before the electra upgrade, right now the node as is just works on mainnet but due to performance is not able to finish syncing.</p> <p>For information on how to run the node please refer to the <a href="https://github.com/lambdaclass/lambda_ethereum_consensus/blob/main/README.md">README.md</a>, for more information regarding the electra update status refer to this document still in the <a href="https://github.com/lambdaclass/lambda_ethereum_consensus/tree/electra-support">electra-support</a> branch: <a href="https://github.com/lambdaclass/lambda_ethereum_consensus/blob/electra-support/electra-gap.md">electra-gap.md</a>.</p> rodrigo-o