You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The CosmWasm team is releasing a version of wasmd with support for v0.45.0. CosmWasm/wasmd#501 We need to move away from our fork of wasmd and use their version.
Problem Definition
We have been managing our own fork of the wasmd module, because it didn't support the version of cosmos-sdk provenance required. They have a new release that has the cosmos-sdk v0.45.0 support we need.
Proposal
Update the go.mod to use the new version
Update the msg handlers to support our new msg fees handler
For Admin Use
Not duplicate issue
Appropriate labels applied
Appropriate contributors tagged
Contributor assigned/self-assigned
The text was updated successfully, but these errors were encountered:
ibc-2.0 requires these address changes now... and given cosmos hub/osmosis/others are on ibc-2.0 that is where we will want to end up as well... so instead of targeting 1.2 we should target 2.0 and update our fork as needed to bring our setup into alignment. Unfortunately I do not believe the cosmwasm team will have their 1.0.0 release updated on the schedule we need for 1.8.0
channa-figure
changed the title
Update to ibc-go 1.2.0 and upgrade wasmd addresses
Update to ibc-go 2.0.2 and upgrade wasmd addresses
Jan 10, 2022
Summary
The CosmWasm team is releasing a version of wasmd with support for v0.45.0. CosmWasm/wasmd#501 We need to move away from our fork of wasmd and use their version.
Problem Definition
We have been managing our own fork of the wasmd module, because it didn't support the version of cosmos-sdk provenance required. They have a new release that has the cosmos-sdk v0.45.0 support we need.
Proposal
For Admin Use
The text was updated successfully, but these errors were encountered: