You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
The text was updated successfully, but these errors were encountered: