Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

levm feature should be part of default #1628

Open
ilitteri opened this issue Jan 6, 2025 · 1 comment · May be fixed by #1682
Open

levm feature should be part of default #1628

ilitteri opened this issue Jan 6, 2025 · 1 comment · May be fixed by #1682
Assignees
@fkrause98
Labels
L1 levm Lambda EVM implementation

Comments

@ilitteri
Copy link
Contributor

ilitteri commented Jan 6, 2025 •
edited
Loading

Important

This issue should be done after #1627

We want the client (L1, and L2) to run under the levm feature by default. The levm feature will be kept as a separate feature and a revm feature will be created to easily be able to switch to using REVM if someone finds a bug in LEVM.
@ilitteri ilitteri added levm Lambda EVM implementation L1 labels Jan 6, 2025
@mpaulucci mpaulucci changed the title LEVM, L1: levm feature should be part of default levm feature should be part of default Jan 9, 2025
@mpaulucci
Copy link
Collaborator

With #1678, this would not be needed

@fkrause98 fkrause98 linked a pull request Jan 10, 2025 that will close this issue
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@fkrause98 fkrause98

Labels
L1 levm Lambda EVM implementation
Projects
ethrex_l1
Status: No status
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(l1, levm): use levm as default lambdaclass/ethrex
3 participants
@mpaulucci @fkrause98 @ilitteri