governance: create upgrade messages #2957
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
erwanor
force-pushed
the
upgrade_message
branch
from
5426d98 to
f3cc664
Compare
erwanor
force-pushed
the
upgrade_message
branch
from
feae410 to
22645b1
Compare
|
I am going to add the actual mechanism for triggering a chain halt / epoch change in a follow-up PR. The rough idea is that we will write a This PR does not add any stateless/stateful check for the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds an
UpgradePlanproposal type that specifies a height for an upgrade. If an upgrade is ratified, then the chain will trigger an epoch change at that height and gracefully shutdown.