Umee v3 (Calypso) Upgrade Tracking

[alexanderbez]

Mainly creating this issue as a brain dump of things to keep in mind when getting ready for the Umee v2 (Calypso) on-chain upgrade:

• SDK v0.46 breaking changes
• Dep updates
  • IBC (state-machine breaking patch)
  • TM v0.35
  • SDK v0.46
• Upgrade handler

[toteki]

SDK 0.46 required for message prioritization (umee #510 and peggo #179)

Leverage mainnet should likely wait until then.

[toteki]

Outside advisors warned not to jump on 0.46 upgrade too quickly - wait at least until alpha is over and it's in beta. It's better not to be the first major chain to do it.

[toteki]

ibc-go 3.0.0 is out now, but we should do it simultaneously with SDK 0.46

This contains interchain accounts functionality, which we won't be directly using yet but might allow us to more easily develop meTokens (from the whitepaper) and deploy the relevant upgrade when the time comes. That's not in scope now though.

[toteki]

Public testnet will actually go through the upgrade procedure (NOT including SDK 0.46) starting from 1.0.x to 2.0.x in order to more closely simulate what we'll be doing in reality.