v4.0.0-rc0

This release includes v1 of the Fee Middleware module. 🍾 Please read the introduction blog post and the documentation!

It also bumps the Go version to v1.18 and the Cosmos SDK to v0.45.6 (for more information, see Cosmos SDK v0.45.6 Release Notes), and introduces several improvements and bug fixes. We present here a summary of the most relevant changes, but please see the v4.0.0 changelog for the full set of changes included in this pre-release.

core/04-channel

• The OnChanOpenInit application callback now returns a version string in line with the latest spec change.
• The NewErrorAcknowledgement function accepts now an error instead of a string, removing therefore the possibility of non-deterministic writes to application state. Please read the relevant section in the migration documentation for more details.

apps/transfer

• The NewErrorAcknowledgement function has been removed in favour of 04-channel's NewErrorAcknowledgement.

apps/27-interchain-accounts

• The RegisterInterchainAccount function includes now an additional version argument to support ICS29 fee middleware functionality in ICS27 interchain accounts. Please read the relevant section in the documentation for more information.
• The NewErrorAcknowledgement function has been removed in favour of 04-channel's NewErrorAcknowledgement.

Special thanks to our external contributors on this release: @faddat @vuong177

---

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.6 and ibc-go v4.0.0-rc0, please follow:

1. 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.
2. The migration from ibc-go v1 to v2.
3. The migration from ibc-go v2 to v3.
4. The migration from ibc-go v3 to v4.
5. The migration to add support for transfers of tokens whose base denomination contains slashes.

v3.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 >= 3.3.1.
• 20th September 2022: It is NOT recommended to use the ICS27 host submodule of this release, since it contains a security vulnerability. Please use version >= 3.3.0.

---

Please note that, according to ibc-go's semantic versioning, this release requires a coordinated upgrade because it contains state-machine breaking changes. This release requires also running a migration.

This release bumps the Cosmos SDK to v0.45.4 (for more information, see Cosmos SDK v0.45.4 Release Notes), and introduces several improvements and bug fixes. We present here a summary of the most relevant changes, but please see the v3.1.0 changelog for the full set of changes included in this release.

core/02-client

• A gRPC query method and CLI query has been added to retrieve the heights of all consensus states associated with the a given client ID.

core/04-channel

• A version field has been added to MsgChannelOpenInitResponse and MsgChannelOpenTryResponse that is set with the selected channel version.
• A channel closed event is now emitted when a timeout occurs for an ordered channel.

apps/transfer

• The DenomTrace gRPC method and CLI query can now take as argument either a trace hash or a full IBC denom prefixed with ibc/.
• The sender address is now added in the event emitted in the OnRecvPacket and OnAcknowledgementPacket callbacks.
• A gRPC query method has been added to retrieve the escrow address for a particular channel.
• Support for token transfers of coins whose base denomination contains slashes has been added. For the transfer of coins whose base denomination contains slashes to succeed, both the sending and the receiving chains need to upgrade to add this support. Please follow also the migration guide.

apps/27-interchain-accounts

• The "*" wildcard can now be used in AllowMessages param to allow any type of message to be executed by the interchain account on the host.

light-clients/07-tendermint

• The use of allow_update_after_expiry and allow_update_after_misbehaviour has been deprecated. See ADR-26 for more information.

Special thanks to our external contributors on this release: @catShaark @vuong177 @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.45.4 and ibc-go v3.1.0, please follow:

1. 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.
2. The migration from ibc-go v1 to v2.
3. The migration from ibc-go v2 to v3.
4. The migration to add support for transfers of tokens whose base denomination contains slashes.

v3.0.1

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 >= 3.3.1.
• 20th September 2022: It is NOT recommended to use the ICS27 host submodule of this release, since it contains a security vulnerability. Please use version >= 3.3.0.

---

This release bumps the Cosmos SDK to v0.45.4 (for more information, see Cosmos SDK v0.45.4 Release Notes), and introduces several improvements and bug fixes. We present here a summary of the most relevant changes, but please see the v3.0.1 changelog for the full set of changes included in this release.

core/04-channel

• A channel closed event is now emitted when a timeout occurs for an ordered channel.

apps/transfer

• The DenomTrace gRPC method and CLI query can now take as argument either a trace hash or a full IBC denom prefixed with ibc/.
• The sender address is now added in the event emitted in the OnRecvPacket and OnAcknowledgementPacket callbacks.

Special thanks to our external contributors on this release: @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.45.4 and ibc-go v3.0.1, please follow:

1. 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.
2. The migration from ibc-go v1 to v2.
3. The migration from ibc-go v2 to v3.

v2.3.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.

---

Please note that, according to ibc-go's semantic versioning, this release requires a coordinated upgrade because it contains state-machine breaking changes. This release requires also running a migration.

This release bumps the Go version to v1.17 and the Cosmos SDK to v0.45.4 (for more information, see Cosmos SDK v0.45.4 Release Notes), and introduces several improvements and bug fixes. We present here a summary of the most relevant changes, but please see the v2.3.0 changelog for the full set of changes included in this release.

core/02-client

• A gRPC query method and CLI query has been added to retrieve the heights of all consensus states associated with the a given client ID.

core/04-channel

• A channel closed event is now emitted when a timeout occurs for an ordered channel.

apps/transfer

• The DenomTrace gRPC method and CLI query can now take as argument either a trace hash or a full IBC denom prefixed with ibc/.
• The sender address is now added in the event emitted in the OnRecvPacket and OnAcknowledgementPacket callbacks.
• A gRPC query method has been added to retrieve the escrow address for a particular channel.
• Support for token transfers of coins whose base denomination contains slashes has been added. For the transfer of coins whose base denomination contains slashes to succeed, both the sending and the receiving chains need to upgrade to add this support. Please follow also the migration guide.

light-clients/07-tendermint

• The use of allow_update_after_expiry and allow_update_after_misbehaviour has been deprecated. See ADR-26 for more information.

Special thanks to our external contributors on this release: @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.45.4 and ibc-go v2.3.0, please follow:

1. 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.
2. The migration from ibc-go v1 to v2.
3. The migration to add support for transfers of tokens whose base denomination contains slashes.

v2.2.1

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 introduces some improvements and bug fixes. We present here the most relevant changes, but please see the v2.2.1 changelog for the full set of changes included in this release.

core/04-channel

• A channel closed event is now emitted when a timeout occurs for an ordered channel.

apps/transfer

• The DenomTrace gRPC method and CLI query can now take as argument either a trace hash or a full IBC denom prefixed with ibc/.
• The sender address is now added in the event emitted in the OnRecvPacket and OnAcknowledgementPacket callbacks.

Special thanks to our external contributors on this release: @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.45.1 and ibc-go v2.2.1, please follow:

1. 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.
2. The migration from ibc-go v1 to v2.

v2.1.1

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 bumps the Cosmos SDK to v0.44.8 (for more information, see Cosmos SDK v0.44.8 Release Notes) and Tendermint to v0.34.19 (for more information, see Tendermint v0.34.19 Release Notes).

We present here a summary of the most relevant improvements and bug fixes, but please see the v2.1.1 changelog for the full set of changes included in this release.

core/04-channel

• A channel closed event is now emitted when a timeout occurs for an ordered channel.

apps/transfer

• The DenomTrace gRPC method and CLI query can now take as argument either a trace hash or a full IBC denom prefixed with ibc/.
• The sender address is now added in the event emitted in the OnRecvPacket and OnAcknowledgementPacket callbacks.

Special thanks to our external contributors on this release: @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.8 and ibc-go v2.1.1, please follow:

1. 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.
2. The migration from ibc-go v1 to v2.

v1.5.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.

---

Please note that, according to ibc-go's semantic versioning, this release requires a coordinated upgrade because it contains state-machine breaking changes. This release requires also running a migration.

This release bumps the Go version to v1.17 and the Cosmos SDK to v0.45.4 (for more information, see Cosmos SDK v0.45.4 Release Notes), and introduces several improvements and bug fixes. We present here a summary of the most relevant changes, but please see the v1.5.0 changelog for the full set of changes included in this release.

core/02-client

• A gRPC query method and CLI query has been added to retrieve the heights of all consensus states associated with the a given client ID.

core/04-channel

• A channel closed event is now emitted when a timeout occurs for an ordered channel.

apps/transfer

• The DenomTrace gRPC method and CLI query can now take as argument either a trace hash or a full IBC denom prefixed with ibc/.
• The sender address is now added in the event emitted in the OnRecvPacket and OnAcknowledgementPacket callbacks.
• A gRPC query method has been added to retrieve the escrow address for a particular channel.
• Support for token transfers of coins whose base denomination contains slashes has been added. For the transfer of coins whose base denomination contains slashes to succeed, both the sending and the receiving chains need to upgrade to add this support. Please follow also the migration guide.

light-clients/07-tendermint

• The use of allow_update_after_expiry and allow_update_after_misbehaviour has been deprecated. See ADR-26 for more information.

Special thanks to our external contributors on this release: @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.45.4 and ibc-go v1.5.0, please follow:

1. 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.
2. The migration to add support for transfers of tokens whose base denomination contains slashes.

v1.4.1

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 introduces some improvements and bug fixes. We present here the most relevant changes, but please see the v1.4.1 changelog for the full set of changes included in this release.

core/04-channel

• A channel closed event is now emitted when a timeout occurs for an ordered channel.

apps/transfer

• The DenomTrace gRPC method and CLI query can now take as argument either a trace hash or a full IBC denom prefixed with ibc/.
• The sender address is now added in the event emitted in the OnRecvPacket and OnAcknowledgementPacket callbacks.

Special thanks to our external contributors on this release: @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.45.1 and ibc-go v1.4.1, please follow:

1. 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.

v1.3.1

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 bumps the Cosmos SDK to v0.44.8 (for more information, see Cosmos SDK v0.44.8 Release Notes) and Tendermint to v0.34.19 (for more information, see Tendermint v0.34.19 Release Notes).

We present here a summary of the most relevant improvements and bug fixes, but please see the v1.3.1 changelog for the full set of changes included in this release.

core/04-channel

• A channel closed event is now emitted when a timeout occurs for an ordered channel.

apps/transfer

• The DenomTrace gRPC method and CLI query can now take as argument either a trace hash or a full IBC denom prefixed with ibc/.
• The sender address is now added in the event emitted in the OnRecvPacket and OnAcknowledgementPacket callbacks.

Special thanks to our external contributors on this release: @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.8 and ibc-go v1.3.1, please follow:

1. 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

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 >= 3.3.1.
• 20th September 2022: It is NOT recommended to use the ICS27 host submodule of this release, since it contains a security vulnerability. Please use version >= 3.3.0.

---

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-rc2 this release:

• adds support to testing package for custom power reduction.

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: @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.45.1 and ibc-go v3.0.0, please follow:

1. 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.
2. The migration from ibc-go v1 to v2.
3. The migration from ibc-go v2 to v3.