Skip to content

Releases: lambdaclass/lambda_ethereum_consensus

Lambda Ethereum Consensus Client v0.1.0 - Deneb Release

24 Apr 21:12
@rodrigo-o rodrigo-o
v0.1.0-alpha.1
c3b54c4
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
Lambda Ethereum Consensus Client v0.1.0 - Deneb Release Pre-release
Pre-release

We're releasing version v0.1.0-alpha.1 of the Lambda Ethereum Consensus Client, marking a step stone of our work through deneb and prior forks before beginning the Electra implementation.

Status

This release represents a spec-wise complete implementation of the Ethereum consensus client in Elixir (beacon chain, fork_choice, p2p and validators), 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.

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 issues.

Current Implementation

The client currently includes:

  • A working implementation of the beacon chain spec with it's spec-test passing
  • A working implementation of the p2p communication tested in Kurtosis and Sepolia.
  • A working implementation of Validator duties as part of the node (not a separate validator client) tested on Kurtosis.
  • Testing infrastructure with spec-test, Kurtosis and an initial Assertoor check

Known limitations

We have some known limitation and we plan to tackle them as soon as we finish the electra upgrades:

  • Sepolia long running sessions with known issues that stop the node
    • This test check the node stability regarding to p2p and state transitions, not validator duties
    • Sessions have been running for a week in the best cases
  • Performance optimization needed specially in block and epoch processing (most notable in Holesky and Mainnet)
  • Assertoor test enhancement
  • Full API support
  • Other lesser priority missing components (like lightclient's support)

Note: 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.

For information on how to run the node please refer to the README.md, for more information regarding the electra update status refer to this document still in the electra-support branch: electra-gap.md.

Loading