-
Notifications
You must be signed in to change notification settings - Fork 169
feat(execution): add Nethermind as alternative client #192
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.
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
base: main
Are you sure you want to change the base?
Conversation
Add support for using Nethermind as an alternative execution client alongside op-geth
Co-authored-by: Ruben Buniatyan <rubo@users.noreply.github.com>
Co-authored-by: Ruben Buniatyan <rubo@users.noreply.github.com>
| @@ -0,0 +1,11 @@ | |||
| FROM nethermind/nethermind:1.31.6 | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a specific reason for not using the latest tag but a hardcoded version? Do we need to update this with each release?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Execution client may not working if it's upgraded ahead of op-node.
|
A concern is if we require |
Removed `start.sh` script in favor of dynamic profile selection via `COMPOSE_PROFILES` environment variable. Updated `.env.example` and `docker-compose.yml` to reflect the new approach, reducing complexity and improving maintainability.
Add support for using Nethermind as an alternative execution client
alongside op-geth