Use the latest ibc-go and interchain-security modules - Notional & CryptoCrew #235
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
|
Should most likely be merged before launch, after speaking with Informal Systems |
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 updates ibc-go to v4.4.0 and interchain-security to the latest commit from the main branch.
The goal is to comply with our mutually adopted new chain launch standards (to be updated "soonTM" with consumer chain launch standards.)
Since state-breaking upgrades are much more challenging than genesis, we recommend that genesis include these changes, after conferring with Informal systems about weather or not 0a000ff can be a proper release tag, so that Neutron's go.mod file will be somewhat cleaner than it is in this PR.