v4.4.3

UPDATES

• 5th April 2024: This release is NOT recommended since it is impacted by the ASA-2024-007 security advisory . Please use version >= 4.6.0 .

We present here a summary of the most relevant changes, please see the v4.4.3 changelog for the full set of changes included in this release.

apps/transfer

• The REST endpoints `/ibc/apps/transfer/v1/denom_traces/{hash}` and `/ibc/apps/transfer/v1/denom_hashes/{trace}` accept now values for `hash` and `trace` that contain slashes.

Special thanks to our external contributors in this release: @emidev98

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.3.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.15 and ibc-go v4.4.3, please follow:

• 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 .

• The migration from ibc-go v1 to v2 .

• The migration from ibc-go v2 to v3 .

• The migration from ibc-go v3 to v4 .