-
Notifications
You must be signed in to change notification settings - Fork 609
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
remove bech32 ibc #1994
remove bech32 ibc #1994
Conversation
I can't fully remove bech32 ibc repo as a dependency because its used in the v5 upgrade code. Is it okay to remove old upgrade migrations from newer code releases? |
yeah, just comment out those lines (comment out import as well please) |
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.
LGTM.
E2E test atm covers sends working AFAIK, so should be confident things are still working. CC'ing @p0mvn to confirm
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.
LGTM - yes as long as e2e tests pass, this should be safe IMO
Sanity checked IBC token transfer e2e test in CI: https://github.com/osmosis-labs/osmosis/runs/7238675443?check_suite_focus=true#step:9:124 . Looks good
* remove bech32 ibc * comment out in v5 upgrade code * CHANGELOG
Closes: #XXX
What is the purpose of the change
This PR removes bech32 ibc from the state machine, because it is unmaintained.
Brief Changelog
(for example:)
Testing and Verifying
(Please pick one of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)
Documentation and Release Note
Unreleased
section inCHANGELOG.md
? (yes / no)x/<module>/spec/
) / Osmosis docs repo / not documented)