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

[Task architecture] - Simplify the upgrade process for sequencer upgrades #3214

Open
Tracked by #3191
ss-es opened this issue May 23, 2024 · 0 comments
Open
Tracked by #3191

Comments

@ss-es
Copy link
Contributor

ss-es commented May 23, 2024

What is this task and why do we need to work on it?

The process for performing an upgrade involving a transition of NodeType is currently tricky and error-prone. With task restartability, this should be a relatively smooth experience where HotShot automatically proposes, votes on and adopts an upgrade.

What work will need to be done to complete this task?

No response

Are there any other details to include?

No response

What are the acceptance criteria to close this issue?

Upgrades can be performed with minimal configuration, by simply instantiating HotShot with two different NodeTypes.

Branch work will be merged to (if not the default branch)

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant