Releases: cosmos/ibc-go
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
InitModuleto the interchain accountsAppModule. This function should be called within the upgrade handler when adding the interchain accounts module to a chain. It should be called in place ofInitGenesis(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.
Contributors
Assets 11
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
ChannelIdfield toMsgChannelOpenInitResponse - changes the type of
acknowledgementparameter inWriteAcknowledgementto beexported.Acknowledgementinstead 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.
Contributors
Assets 11
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.
v3.0.0-beta1
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-alpha2 this release:
- addresses all issues raised by Trail of Bits during an audit of ICS27
- simplifies controller chain portID to only contain a prefix and the owner address
- introduces JSON encoded metadata to ICS27 to store the version, connection sequences, encoding/txtype, and the interchain account address
- the ics27 host chain will include the MsgResponse in the packet acknowledgement upon successful transaction execution. Please see the auth module documentation for more information
- bumps Cosmos SDK version to 0.45.
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: @nir1218, @assafmo, @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.
Contributors
Assets 11
v3.0.0-alpha2
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.🥇
Comparing to v3.0.0-alpha1 this release improves version negotiation flow for relayers and allows ICS20 to connect to middleware (this is an API-breaking change that requires migration).
Please read the migration doc, which provides information on updating from v2 to v3.
Please see the CHANGELOG for all the changes included in this release.
Special thanks to our external contributors on this release: @technicallyty.
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.
Contributors
Assets 2
v3.0.0-alpha1
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.🥇
Please read the migration doc, which provides information on updating from v2 to v3.
Please see the CHANGELOG for all the changes included in this release.
Special thanks to our external contributors on this release: @technicallyty.
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.
Contributors
Assets 2
v2.0.2
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.
Please read the migration doc, which provides information on updating from v1 to v2.
Dependencies
- #589 Bump SDK version to v0.44.5
Bug Fixes
- (modules/core) #603 Fix module name emitted as part of
OnChanOpenInitevent. Replacingconnectionmodule name withchannel.
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.2.5
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 fixes the module name emitted as part of OnChanOpenInit event and bumps the Cosmos SDK from v0.44.4 to v0.44.5 (for more information, see Cosmos SDK v0.44.5 Release Notes).
Check out the v1.2.5 changelog for more information about the changes and see previous changes in the v1.2.x release series.
To learn more about ibc-go versioning, please read our RELEASES.md.