v2.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 >= 2.4.2.

---

This release includes a fix for a security vulnerability identified in transfer application. User funds in accounts and staking delegations are NOT at risk.

The only other change in this release (see CHANGELOG) is the bump of the Cosmos SDK to v0.45.1 (for more information, see Cosmos SDK v0.45.1 Release Notes).

---

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.44.3 and ibc-go v2.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 AND the migration from ibc-go v1 to v2.

v2.1.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 >= 2.4.2.

---

This release includes a fix for a security vulnerability identified in transfer application. User funds in accounts and staking delegations are NOT at risk.

For the release line v2.x, we recommend NOT to use any version of ibc-go < v2.1.0.

Please see the CHANGELOG for the full set of changes included in this release.

---

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.44.3 and ibc-go v2.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 AND the migration from ibc-go v1 to v2.

v1.4.0

UPDATES

• 1st July 2022: This release series has reached of life and will not receive any new updates. Please use version >= 2.1.0.

---

This release includes a fix for a security vulnerability identified in transfer application. User funds in accounts and staking delegations are NOT at risk.

The only other change in this release (see CHANGELOG) is the bump of the Cosmos SDK to v0.45.1 (for more information, see Cosmos SDK v0.45.1 Release Notes).

---

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.1 and ibc-go v1.4.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.45.x.

v.1.3.0

UPDATES

• 1st July 2022: This release series has reached of life and will not receive any new updates. Please use version >= 2.1.0.

---

This release includes a fix for a security vulnerability identified in transfer application. User funds in accounts and staking delegations are NOT at risk.

For the release line v1.x, we recommend NOT to use any version of ibc-go < v1.3.0.

Please see the CHANGELOG for the full set of changes included in this release.

---

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.44.6 and ibc-go v1.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.

v3.0.0-rc2

This release includes v1 of the Interchain Accounts application module. 🍾
This is the first major feature addition since the v1.0.0 release of ibc-go. 👏
Kudos to everyone that has contributed to this feature on protocol design, implementation, testing and auditing. 🙏
Shout-out to the team at Chainapsis for the brilliant work that kick-started everything. 🌟
And last but not least, we want to thank @seantking for leading the efforts to bring all this to fruition.🥇

At a high level, when comparing to v3.0.0-rc1 this release:

• fixes the migration documentation for adding store upgrades for the ICS27 module.
• adds counterpartyChannelID to argument list of the OnChanOpenAck callback in the IBCModule interface.
• fixes the rejection of redundant packet messages within the same block. This fix entailed replacing the field of type channelkeeper.Keeper in the AnteDecorator structure with a field of type *keeper.Keeper.

Please see the CHANGELOG for the full set of changes included in this release.

Please read the migration doc, which provides information on updating from v2 to v3.

Special thanks to our external contributors on this release: @joe-bowman @catShaark @fedekunze

---

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.44.3 and ibc-go v2.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 AND the migration from ibc-go v1 to v2.

v3.0.0-rc1

This release includes v1 of the Interchain Accounts application module. 🍾
This is the first major feature addition since the v1.0.0 release of ibc-go. 👏
Kudos to everyone that has contributed to this feature on protocol design, implementation, testing and auditing. 🙏
Shout-out to the team at Chainapsis for the brilliant work that kick-started everything. 🌟
And last but not least, we want to thank @seantking for leading the efforts to bring all this to fruition.🥇

At a high level, when comparing to v3.0.0-rc0 this release:

• bumps the version of ics23/go to v0.7.
• adds a function InitModule to the interchain accounts AppModule. This function should be called within the upgrade handler when adding the interchain accounts module to a chain. It should be called in place of InitGenesis (set the consensus version in the version map).
• adds support for base denoms with slashes.
• classifies client states without consensus states as expired.

Please see the CHANGELOG for the full set of changes included in this release.

Please read the migration doc, which provides information on updating from v2 to v3.

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

---

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.44.3 and ibc-go v2.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 AND the migration from ibc-go v1 to v2.

v3.0.0-rc0

This release includes v1 of the Interchain Accounts application module. 🍾
This is the first major feature addition since the v1.0.0 release of ibc-go. 👏
Kudos to everyone that has contributed to this feature on protocol design, implementation, testing and auditing. 🙏
Shout-out to the team at Chainapsis for the brilliant work that kick-started everything. 🌟
And last but not least, we want to thank @seantking for leading the efforts to bring all this to fruition.🥇

At a high level, when comparing to v3.0.0-beta1 this release:

• adds a ChannelId field to MsgChannelOpenInitResponse
• changes the type of acknowledgement parameter in WriteAcknowledgement to be exported.Acknowledgement instead of a byte array
• adds several improvements to the testing package
• bumps Cosmos SDK version to 0.45.1.

Please see the CHANGELOG for the full set of changes included in this release.

Please read the migration doc, which provides information on updating from v2 to v3.

Special thanks to our external contributors on this release: @rigelrozanski @fedekunze @dkmccandless

---

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.44.3 and ibc-go v2.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 AND the migration from ibc-go v1 to v2.

v2.0.3

UPDATES

15th March 2022: This release is NOT recommended since it contains a security vulnerability in the transfer application. Please use version >= 2.1.0.

---

This release includes an improvement to minimize channel logging by only emitting the packet sequence, source port/channel, destination port/channel upon packet receives, acknowledgements and timeouts.

Check out the v2.0.3 changelog for more information about this change and see previous changes in the v2.0.x release series.

To learn more about ibc-go versioning, please read our RELEASES.md.

v1.2.6

UPDATES

15th March 2022: This release is NOT recommended since it contains a security vulnerability in the transfer application. Please use version >= 1.3.0.

---

This release includes an improvement to minimize channel logging by only emitting the packet sequence, source port/channel, destination port/channel upon packet receives, acknowledgements and timeouts.

Check out the v1.2.6 changelog for more information about this change and see previous changes in the v1.2.x release series.

To learn more about ibc-go versioning, please read our RELEASES.md.

v1.1.6

UPDATES

15th March 2022: This release is NOT recommended since it contains a security vulnerability in the transfer application. Please use version >= 1.3.0.

---

This release includes an improvement to minimize channel logging by only emitting the packet sequence, source port/channel, destination port/channel upon packet receives, acknowledgements and timeouts.

Check out the v1.1.6 changelog for more information about this change and see previous changes in the v1.1.x release series.

To learn more about ibc-go versioning, please read our RELEASES.md.