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 .