[Hub] cosmoshub-4.6 tracking

[shahankhatch]

The branch cosmoshub-4.6 is going to be used for the upcoming upgrade.

The current soft target for the cosmos hub upgrade is June, 2021.

• [ ] latest version of sdk, at alpha
• [ ] latest version of tendermint, awaiting v0.35 rc
• [ ] latest version of ibc-go, at alpha
• [ ] latest version of dex, to be imported after updating to sdk alpha
• [ ] documentation
  • [ ] upgrade
  • [ ] breaking changes
  • [ ] cosmovisor
  • [ ] ibc
• [ ] governance
  • [ ] cip
  • [ ] dex parameter change proposal
  • [ ] ibc upgrade proposal
• [ ] upgrade policies, e.g., cosmosvisor
  • [ ] cip?

[shahankhatch]

The branch hub/cosmoshub-5 is the target.

[shahankhatch]

Renaming this to become a cosmoshub-5 tracking issue.

[shahankhatch]

The cosmoshub-5 chain id won't be used, so I'm going to delete the branch (there were no new commits into it).

I created an interim branch cosmoshub-4.6 that is importing available alpha releases.

I'm going to update this issue to track the upcoming upgrade.

[hxrts]

Shall I change the discord channel title accordingly?

[shahankhatch]

Yes, please and thanks @hxrts. Wdyt of titling it something like cosmoshub upgrades?

[shahankhatch]

I have the permissions so I changed the channel title

[hxrts]

Yes, please and thanks @hxrts. Wdyt of titling it something like cosmoshub upgrades?

Up to you. If you'd prefer to have a catch-all channel for upgrades vs a chan for specific upgrades that works for me. I could see concurrent conversations on n and n+1 upgrades potentially being helpful in certain scenarios. Could be more trouble than it's worth though.