cosmos/ibc-go v4.2.0

on GitHub

UPDATES

• 25th May 2023: This release is NOT recommended since it is impacted by the huckleberry security advisory. Please use version >= 4.2.2.

This release uses Cosmos SDK v0.45.10 and introduces a couple of improvements requested by the community. Please see the v4.2.0 changelog for more details.

apps/transfer

• The sequence number of the packet sent has been added to MsgTransferResponse.
• An optional memo field has been added to FungibleTokenPacketData. Token transfers that include a non-empty memo field will fail if the receiver chain is not running a version of ibc-go that also supports the memo field. Please read this blog post for more information.

apps/27-interchain-accounts

• The check in OnChanOpenTry callback on the host submodule that required the port ID on the controller chain to be prefixed by icacontroller- has been removed. Thanks to @LaurensKubat and @catShaark for this recommendation.

Special thanks to our external contributors on this release: @faddat @agouin @nicolaslara @LaurensKubat

Please note that the v4 release line contains a bug where fee-enabled Interchain Accounts channels cannot be reopened in case of channel closure due to packet timeout. Regular Interchain Accounts channels (i.e. non fee-enabled) can be reopened. In order to be able to reopen fee-enabled Interchain Accounts channels, please upgrade to v5.2.1 or above.

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.10 and ibc-go v4.2.0, please follow:

1. The migration from SDK 0.41.x or 0.42.x to the IBC module in the ibc-go repository based on the SDK v0.44.x.
2. The migration from ibc-go v1 to v2.
3. The migration from ibc-go v2 to v3.
4. The migration from ibc-go v3 to v4.