Upgrade cosmos-sdk v0.50 get error "max inflation less than min inflation"

[ledanghuy1811]

Context

Before we run upgrade to cosmos-sdk v0.50 in our mainnet, we fork current mainnet to a testnet with fully data of our mainnet. The purpose of this is that we want to upgrade in our fork-mainnet (testnet) first to see if we got error.

We run e2e-upgrade script first to check if there is error or not and it work without errors but when we try to upgrade to cosmos-sdk v0.50 in our testnet, the error is show up:

To Reproduce

Steps to reproduce the behavior:

1. Need to fork mainnet and run node
2. Clone our old repo and build oraid binary
3. Try to make proposal to upgrade fork-mainnet
4. Clone this repo and checkout to this commit
5. Build new binary and re run node to see error

Expected behavior

The upgrade process pass and node start to commit block.

Additional context

• The error is come from this method: https://github.com/oraichain/cosmos-sdk/blob/cae2f186c240bed6f0244eab0fae42b3cb6f504f/x/mint/module.go#L130, RegisterServices
• When the function above reach line 136, it will call function m.Migrate1to2
• 
• At Migrate1to2 fucntion, it get mint param then validate it. The error come up at line 31

[ledanghuy1811]

The error come up because when in old version, mint params we set have max inflation less than min inflation. When upgrade chain to cosmos-sdk v0.50, when reach logic migrate mint module, it come with error when validate old mint params.

[ledanghuy1811]

To fix this error, in upgrade chain handler logic, we get mint params first and then set max inflation equal to min inflation, set this modified params back to store.

Fixed in here