v3.2.0
UPDATES
- 27th October 2022: This release is NOT recommended since it uses a version of the Cosmos SDK impacted by the dragonberry security advisory. Please use version >= 3.3.1.
- 20th September 2022: It is NOT recommended to use the ICS27 host submodule of this release, since it contains a security vulnerability. Please use version >= 3.3.0.
Please note that, according to ibc-go's semantic versioning, this release requires a coordinated upgrade because it contains state-machine breaking changes. This release requires also running a migration.
This release bumps the Go version to v1.18 and the Cosmos SDK to v0.45.7 (for more information, see Cosmos SDK v0.45.7 Release Notes), and introduces several improvements and bug fixes. We present here a summary of the most relevant changes. Please see the v3.2.0 changelog for the full set of changes included in this release.
apps/transfer
- A new migration has been added to correct any malformed trace path information of tokens whose base denomination contains slashes. The transfer module consensus version has been bumped to 2.
- The channel ID is now used to split the complete denomination into the trace path and the base denomination. Previously the port ID
transferwas used. - A check has been added to ensure that the sender is not a blocked address. Thanks to @asalzmann for reporting a problem with blocked addresses that resulted in this fix.
light-clients/07-tendermint
- Client upgrade proposals are now able to update the
TrustingPeriodof the light client.
Special thanks to our external contributors on this release: @pyramation @devashishdxt @joeabbey
To learn more about ibc-go versioning, please read our RELEASES.md.
IMPORTANT: Please read the migration guides for any versions of ibc-go that you might be going through when upgrading to this version. For example: if you upgrade from the IBC module contained in the Cosmos SDK 0.42.0 to SDK v0.45.6 and ibc-go v3.2.0, please follow:
