Upgrade to IBC v4 or v5

[alpe]

Tracking issue to upgrade the ibc-go dependency to v4

This release contains the fee middleware.

See migration guide

Versions currently used

• v3.0 juno main, terra

• v3.1 tgrade main, stargaze main

• v3.2 osmosis main

• v5.0-rc0 gaia main

[faddat]

Basically, as far as I understand things:

We will want ibc-go v4 OR ibc-go v3.2.0 for cosmos-sdk v0.45.7 -- there were some changes to support the sped-up DB, is my understanding. I also noticed a change that related to txCtx.R being included in gentx(...blabla..)

Also, I'd like to share an opinion-- my opinion is that CosmWasm represents the most advanced IBC application and that when possible, it makes sense to keep its IBC version rather aggressively up to date.

[the-frey]

Would vote for v5. Do you have thoughts @jhernandezb ?

[the-frey]

What we're seeing on testnets is ICA is causing a huge increase in relayer fees so as long as we're >v4 it's probably okay - nevertheless I agree with @faddat's reasoning that we should roll with v5

[jhernandezb]

v5 will require moving to sdk 0.46, do we want to push for an sdk upgrade?

[the-frey]

Ah I think (from memory) the notion was that wasmd would go straight to 0.47 when available, so that means v4? or is v4 also predicated on 46?

[jhernandezb]

IBC v4 still depends on sdk 0.45 that will make it easier to upgrade
https://github.com/cosmos/ibc-go/blob/v4.1.0/go.mod#L10

[the-frey]

Okay, I think then my vote would be v4 for 0.30.0 in that case.

[faddat]

Personally I am for version 6 and SDK 46 because we should not whip one another unnecessarily, you see, the dragon and it's berries are so fierce. They have delayed 47, and 46 adds useful stuff to the interchain accounts controller.

[ethanfrey]

ibc-go v4.1.1 looks good: https://github.com/cosmos/ibc-go/blob/v4.1.1/go.mod#L10 (not 4.0 per their RELEASE NOTES)

[alpe]

v4.2.0 it is now out https://github.com/cosmos/ibc-go/blob/v4.2.0/CHANGELOG.md