Skip to content

Conversation

@AnkushinDaniil
Copy link

Add support for using Nethermind as an alternative execution client
alongside op-geth

Add support for using Nethermind as an alternative execution client
alongside op-geth
AnkushinDaniil and others added 2 commits April 23, 2025 10:11
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
Copy link

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?

Copy link
Collaborator

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.

@Chomtana
Copy link
Collaborator

A concern is if we require --profile op-geth it might affect user who have used to use simple down and up to upgrade the node.

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.
@AnkushinDaniil AnkushinDaniil requested a review from Chomtana April 28, 2025 12:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants