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

Parameterizing Node type for Base and Upgrade version #1824

Closed
imabdulbasit opened this issue Aug 6, 2024 · 1 comment
Closed

Parameterizing Node type for Base and Upgrade version #1824

imabdulbasit opened this issue Aug 6, 2024 · 1 comment

Comments

@imabdulbasit
Copy link
Contributor

With the marketplace, we will have 3 supported versions of the sequencer: "regular" 0.1, "fee upgrade" 0.2, and "marketplace" 0.3. Since we want to be able to test upgrades between any pair of consecutive version with the same binary (e.g. in native demo or staging), we are looking at parameterizing the whole sequencer on Base and Upgrade versions, and selecting which parameterization to use at runtime at the top level, by looking at the upgrades config or environment or whatever.

more details in zulip thread
https://espresso.zulipchat.com/#narrow/stream/311646-Consensus/topic/Specifying.20base.20and.20upgrade.20version.20dynamically

@imabdulbasit imabdulbasit self-assigned this Aug 6, 2024
@imabdulbasit imabdulbasit changed the title Parametrizing Node type for Base and Upgrade version Parameterizing Node type for Base and Upgrade version Aug 6, 2024
@imabdulbasit
Copy link
Contributor Author

done in #1878

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