v4.3.0

UPDATES

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

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

dependencies

• Cosmos SDK has been bumped to v0.45.12 .

• ics23 has been bumped to v0.9.0 .

core

• The writing of the channel in state is now done before invoking the application callbacks in `ChannelOpenAck` and `ChannelOpenConfirm` .

apps/29-fee

• A call to `x\bank` `IsSendEnabledCoins` has been added before escrowing fees in `PayPacketFee` and `PayPacketFeeAsync` .

• Save gas by checking key existence with `KVStore`'s `Has` method in `IsFeeEnabled` .

Special thanks to our external contributors on this release: @alpe

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.12 and ibc-go v4.3.0, 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 .