-
Notifications
You must be signed in to change notification settings - Fork 283
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
chore: audit x/upgrade
module
#2072
Conversation
Codecov Report
@@ Coverage Diff @@
## main #2072 +/- ##
==========================================
+ Coverage 24.28% 24.41% +0.12%
==========================================
Files 125 126 +1
Lines 14248 14300 +52
==========================================
+ Hits 3460 3491 +31
- Misses 10432 10448 +16
- Partials 356 361 +5
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why add the x/upgrade module to our state machine? What behavior do we want to use from the upstream x/upgrade module?
Does the abstract answer this question? I can add portions of #1562 here as well if that would help. We don't want to be able to vote on upgrades, but we do still need some functionality so that IBC continue to compile/work. We also want to use the migration functionality, and we could even utilize the the halting/switching binaries mechanism as well should those things be needed.
IMO it didn't so I tried to elaborate on it in this PR. ADR-016 contains some more useful context so I copied that in.
It's not immediately clear what functionality is preserved in the forked x/upgrade module that is needed for IBC to work. Maybe we clarify that in a follow-up. |
Does our fork intentionally not register the CLI command? I can't do
Ref: https://docs.cosmos.network/v0.46/modules/upgrade/04_client.html#cli also can't use tx commands
https://github.com/cosmos/cosmos-sdk/blob/v0.46.14/x/upgrade/client/cli/tx.go |
ref #1629 (comment) unfortunately we are unable to compile using the ibc module since it relies on some upgrade module types |
re: the cli commands since we are unable to submit the software upgrade proposals, imo we should also remove the cli commands that create them since there is no reason to create them |
Closes #1961