Releases: cosmos/ibc-go
v4.4.1
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.
This release includes a fix for the huckleberry security advisory. Credits to Felix Wilhelm (@felixwilhelm) of Jump Crypto for the discovery and responsible disclosure via our bug bounty program.
Please see the v4.4.1 changelog for the full set of changes included in this release.
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.15 and ibc-go v4.4.1, please follow:
Contributors
Assets 11
v4.3.1
This release includes a fix for the huckleberry security advisory. Credits to Felix Wilhelm (@felixwilhelm) of Jump Crypto for the discovery and responsible disclosure via our bug bounty program.
Please see the v4.3.1 changelog for the full set of changes included in this release.
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.1, please follow:
Contributors
Assets 11
v4.2.2
This release reverts a state-machine breaking improvement that was mistakingly released in v4.2.1. See the v4.2.2 changelog for more details. Please do not use v4.2.1.
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.2, please follow:
v4.2.1
UPDATES
- 25th May 2023: This release is NOT recommended since it includes by mistake a state-machine breaking change. Please use version >= 4.2.2.
This release includes a fix for the huckleberry security advisory. Credits to Felix Wilhelm (@felixwilhelm) of Jump Crypto for the discovery and responsible disclosure via our bug bounty program.
Please see the v4.2.1 changelog for the full set of changes included in this release.
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.1, please follow:
Contributors
Assets 11
v4.1.3
This release reverts a state-machine breaking improvement that was mistakingly released in v4.1.2. See the v4.1.3 changelog for more details. Please do not use v4.1.2.
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.1.3, please follow:
v4.1.2
UPDATES
- 25th May 2023: This release is NOT recommended since it includes by mistake a state-machine breaking change. Please use version >= 4.1.3.
This release includes a fix for the huckleberry security advisory. Credits to Felix Wilhelm (@felixwilhelm) of Jump Crypto for the discovery and responsible disclosure via our bug bounty program.
Please see the v4.1.2 changelog for the full set of changes included in this release.
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.1.2, please follow:
Contributors
Assets 11
v5.3.0
UPDATES
- 25th May 2023: This release is NOT recommended since it is impacted by the huckleberry security advisory. Please use version >= 5.3.1.
This release updates dependencies. Please see the v5.3.0 changelog for more information.
dependencies
- Cosmos SDK has been bumped to v0.46.12.
- Tendermint has been replaced with CometBFT v0.34.27.
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.46.11 and ibc-go v5.3.0, please follow:
v4.4.0
UPDATES
- 25th May 2023: This release is NOT recommended since it is impacted by the huckleberry security advisory. Please use version >= 4.4.1.
This release updates dependencies. Please see the v4.4.0 changelog for more information.
dependencies
- Cosmos SDK has been bumped to v0.45.15.
- Tendermint has been replaced with CometBFT v0.34.27.
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.15 and ibc-go v4.4.0, please follow:
v7.0.0
UPDATES
- 25th May 2023: This release is NOT recommended since it is impacted by the huckleberry security advisory. Please use version >= 7.0.1.
This release main addtions are:
02-client refactor
This refactor will make the development of light clients easier. The ibc-go implementation will finally align with the spec and light clients will be required to set their own client and consensus states. This will allow more flexibility for light clients to manage their own internal storage and do batch updates. For more infomation, please check the following resources:
- This Medium blog post by @adiraviraj.
- ADR-006.
- ADR-007.
Cosmos SDK v0.47 upgrade
Authz support for 20-transfer
We present here a summary of the most relevant changes. Please see the v7.0.0 changelog for the full set of changes included in this release.
dependencies
- Cosmos SDK has been bumped to v0.47.0.
- Tendermint has been replaced with CometBFT v0.37.
IMPORTANT: relaying between a chain on Tendermint/CometBFT v0.34 (ibc-go < v7.0.0) and a chain on CometBFT v0.37 (ibc-go >= v7.0.0):
- is supported by cosmos/relayer v2.2.0 and above;
- will be supported by informalsystems/hermes v1.4.0 (see tracking issue for more details) and above.
light-clients/07-tendermint
- Governance is now able to update the
TrustingPeriodof Tendermint light clients. See ADR-026 for more information.
light-clients/09-localhost
- The localhost light client implementation has been removed, since it was not functional. A new implementation will be released in ibc-go v7.1.0.
core/04-channel
- Optimistic sends have been disabled. And packet can only be sent if the channel is open.
apps/transfer
- Authz support has been added to transfer application. See transfer documentation for more information.
Special thanks to our external contributors on this release: @tac0turtle @Anmol1696 @fedekunze @seunlanlege @Daniyal98 @notbdu
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.47.0 and ibc-go v7.0.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.
- The migration from ibc-go v4 to v5.
- The migration from ibc-go v5 to v6.
- The migration from ibc-go v6 to v7.
Contributors
Assets 11
v7.0.0-rc1
This release main additions are:
02-client refactor
This refactor will make the development of light clients easier. The ibc-go implementation will finally align with the spec and light clients will be required to set their own client and consensus states. This will allow more flexibility for light clients to manage their own internal storage and do batch updates. For more infomation, please check the following resources:
- This Medium blog post by @adiraviraj.
- ADR-006.
- ADR-007.
Cosmos SDK v0.47 upgrade
Authz support 20-transfer
We present here a summary of the most relevant changes in comparison to v7.0.0-rc0. Please see the v7.0.0 changelog for the full set of changes included in this pre-release.
dependencies
- Cosmos SDK has been bumped to v0.47.0-rc3.
- Tendermint has been replaced with CometBFT v0.37.
Special thanks to our external contributors on this release: @tac0turtle @Anmol1696 @fedekunze @seunlanlege @Daniyal98 @notbdu
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.47.0-rc3 and ibc-go v7.0.0-rc1, 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.
- The migration from ibc-go v4 to v5.
- The migration from ibc-go v5 to v6.
- The migration from ibc-go v6 to v7.