Making the 47 experience a good one

[faddat]

for sdk 47 we should ensure that core libraries keep pace with its development so that the release can be deployed with ease and teams can trust it.

from my perspective, this means:

• work on integrating IBC
• work on integrating cosmwasm

I've begun this, but wanted to flag this because the majority of hesitance and uncertainty around 46 (to this day) comes from the fact that we don't have a final release of ibc-go v5.0.0 -- this means that most chains are unlikely to upgrade.

I've been working with the umee team today, and the first instinct was to look into ibc, because it is still at an rc version.

I'll be linking to this issue with PR's into the two relevant repositories...

[faddat]

cosmwasm: CosmWasm/wasmd#1022

[alexanderbez]

How would you imagine integration into the SDK? Couldn't you make the argument that the respective frameworks integrate the SDK into their e2e/integration testing suites instead?

[faddat]

Both directions work, but this repository is most central.

For wasmd, I think there's a real world where we simply do:

github.com/cosmos/cosmos-sdk/x/wasm

And then it's done.

Anyhow, in this case I intend to just make the needed PR's manually to the external repositories and make sure we get off the ground with the trifecta:

• cosmwasm
• ibc-go
• ica

[tac0turtle]

I'm onboard with spinning up a public testnet with these modules.

[tac0turtle]

we have been integrting with wasm and ibc and have a testnet going with all three.