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.

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

[Refactor]: Update SSV Docker Image Tag (with next SSV mainnet release) #2090

Open
daverolo opened this issue Oct 5, 2024 · 0 comments · May be fixed by #2096
Open

[Refactor]: Update SSV Docker Image Tag (with next SSV mainnet release) #2090

daverolo opened this issue Oct 5, 2024 · 0 comments · May be fixed by #2096
Labels
refactor Refactoring tasks aimed at improving code without altering functionality

Comments

@daverolo
Copy link
Contributor

daverolo commented Oct 5, 2024

Refactor Description

Docker image for SSV service must be updated to ssvlabs/ssv-node, starting from version v2.0.0

SSV release of v2.0.0 is expected arround calendar week 43

Version v1.3.8 is the last release that works with the old repo bloxstaking/ssv-node.
This implies that Stereum can only support updates for higher SSV releases if the suggested change is implemented and Stereum has a new release.

To fix this issue we need to change the image to ssvlabs/ssv-node in launcher/src/backend/ethereum-services/SSVNetworkService.js and write playbooks for the Stereum release to adjust existing nodes.

Reason for Refactor

SSV Breaking Change since v2.0.0

Potential Risks

None as long as the next Stereum release includes this change with the next SSV mainnet release.

@daverolo daverolo added the refactor Refactoring tasks aimed at improving code without altering functionality label Oct 5, 2024
@daGscheid daGscheid linked a pull request Oct 24, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
refactor Refactoring tasks aimed at improving code without altering functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant