v10.1.1

ibc-go v10.1.1 Release Notes

Notable changes introduced in ibc-go v10.1.1 are highlighted below, view the full changelog for more details.

New Features

The iteration of the protocol, IBC v2 is added alongside the existing IBC protocol:

• The new protocol removes channel and connection handshakes, minimising the application interface, reducing complexity and making it easier to use IBC in new domains: connectivity with Ethereum is now possible.
• This blog provides an overview of the new protocol, a more technical overview is found in the IBC v2 specification.
• Token transfer, and the callbacks middleware is supported with IBC v2.
• Existing IBC channels will remain functional, there is no migration to the v2 protocol in this release.

New versioning scheme for modules

Previously, modules in ibc-go have been versioned and branched separately. Starting with the v10 line, modules/light-clients/08-wasmwill follow and release together with ibc-go. The first stable release of 08-wasm will be 08-wasm/v10.0.0. The callbacks module has been included in ibc-go's own module, and is therefore not a separate module anymore.

You can find releases and notes for 08-wasm seperately.

Removal to ease maintenance and reduce attack surface

• Removal of the capabilities module
• Removal of the fee middleware module
• Removal of channel upgradability

Other noteworthy changes

Since the early work started on v10, some important changes also include:

• Redaction of ibc-go v9, so that we could also remove ICS20v2 (ics20-2)
• Cleanup of API surface, bringing back multiple functions as deprecated to reduce upgrade burden from v8

Migration Guide

Migration documentation is found here.

modules/light-clients/08-wasm/v10.1.1

08-wasm v10.1.1 Release Notes

Notable changes introduced in modules/light-clients/08-wasm v10.1.1 are highlighted below, view the full changelog for more details.

New features

• A new CosmWasm querier that enables 08-wasm light clients to perform BLS signature aggregation and verification.

New versioning scheme for modules

Previously, modules in ibc-go have been versioned and branched separately. Starting with the v10 line, modules/light-clients/08-wasmwill follow and release together with ibc-go. The first stable release of 08-wasm will be 08-wasm/v10.0.0. The callbacks module has been included in ibc-go's own module, and is therefore not a separate module anymore.

Migration Guide

Migration documentation is found here.

v8.7.0

This release contains a fix for ISA-2025-001.

This version addresses a security vulnerability in IBC-go's deserialisation of acknowledgements and we strongly encourage everyone in the affected versions to update their chain immediately. This patch is not state-breaking, so chains can upgrade in a rolling manner. This does not have to be a co-ordinated upgrade. However, validators should upgrade as soon as possible when the release is made available. If the vulnerability is exploited before 2/3 is patched, the chain will halt.

Full Changelog: v8.6.1...v8.7.0

---

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.50.9 and ibc-go v8.5.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.
4. The migration from ibc-go v3 to v4.
5. The migration from ibc-go v4 to v5.
6. The migration from ibc-go v5 to v6.
7. The migration from ibc-go v6 to v7.
8. The migration from ibc-go v7 to v7.1.
9. The migration from ibc-go v7.2 to v7.3.
10. The migration from ibc-go v7 to v8.
11. The migration from ibc-go v8 to v8.1.

v7.10.0

This release contains a fix for ISA-2025-001.

This version addresses a security vulnerability in IBC-go's deserialisation of acknowledgements and we strongly encourage everyone in the affected versions to update their chain immediately. This patch is not state-breaking, so chains can upgrade in a rolling manner. This does not have to be a co-ordinated upgrade. However, validators should upgrade as soon as possible when the release is made available. If the vulnerability is exploited before 2/3 is patched, the chain will halt.

Full Changelog: v7.9.2...v7.10.0

---

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.50.9 and ibc-go v8.5.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.
4. The migration from ibc-go v3 to v4.
5. The migration from ibc-go v4 to v5.
6. The migration from ibc-go v5 to v6.
7. The migration from ibc-go v6 to v7.
8. The migration from ibc-go v7 to v7.1.
9. The migration from ibc-go v7.2 to v7.3.

v8.6.1

This release contains a fix to ASA-2025-004

It is recommended to upgrade to this version as soon as possible.

Full Changelog: v8.5.3...v8.6.1

---

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.50.9 and ibc-go v8.5.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.
4. The migration from ibc-go v3 to v4.
5. The migration from ibc-go v4 to v5.
6. The migration from ibc-go v5 to v6.
7. The migration from ibc-go v6 to v7.
8. The migration from ibc-go v7 to v7.1.
9. The migration from ibc-go v7.2 to v7.3.
10. The migration from ibc-go v7 to v8.
11. The migration from ibc-go v8 to v8.1.

v7.9.2

This release contains a fix to ASA-2025-004

It is recommended to upgrade to this version as soon as possible.

Full Changelog: v7.8.0...v7.9.2

---

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.50.9 and ibc-go v8.5.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.
4. The migration from ibc-go v3 to v4.
5. The migration from ibc-go v4 to v5.
6. The migration from ibc-go v5 to v6.
7. The migration from ibc-go v6 to v7.
8. The migration from ibc-go v7 to v7.1.
9. The migration from ibc-go v7.2 to v7.3.

modules/light-clients/08-wasm/v0.5.0+ibc-go-v8.4-wasmvm-v1.2

‼️ Please note: This is a state machine breaking change and will require a coordinated upgrade.

The changes in this release:

Dependencies

• #7735 Bump wasmvm to v2.1.4 * (NOTE: This is a state machine breaking dependency update)

---

In order to use this release, please follow the steps to import git commit 3f2a900.

Full Changelog: modules/light-clients/08-wasm/v0.4.1+ibc-go-v8.4-wasmvm-v2.0...modules/light-clients/08-wasm/v0.5.0+ibc-go-v8.4-wasmvm-v1.2

modules/light-clients/08-wasm/v0.4.0+ibc-go-v7.4-wasmvm-v1.5

‼️ Please note: This is a state machine breaking change and will require a coordinated upgrade.

The changes in this release:

Dependencies

• #7744 Bump wasmvm to 1.5.6 * (NOTE: This is state machine breaking change)

---

In order to use this release, please follow the steps to import git commit 8392c48.

Full Changelog: modules/light-clients/08-wasm/v0.3.1+ibc-go-v7.4-wasmvm-v1.5...modules/light-clients/08-wasm/v0.4.0+ibc-go-v7.4-wasmvm-v1.5

v8.5.2

We present here a summary of the most relevant changes, please see the v8.5.2 changelog for more details.

Testing

• #7430 Update the block proposer in test chains for each block.

Bug Fixes

• (core/03-connection) #7397 Skip the genesis validation connectionID for localhost client.

v8.5.1

This release fixes a panic that occurred during instantiation of the interchain accounts host keeper when populating the list of all module safe queries and port definitions were not found. The solution implemented is to use the cosmos/gogoproto registry instead of including the entire merged global files registry. Please check the v8.5.1 changelog for more details. Big thanks to @damiannolan for resolving this issue!

---

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.50.9 and ibc-go v8.5.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.
4. The migration from ibc-go v3 to v4.
5. The migration from ibc-go v4 to v5.
6. The migration from ibc-go v5 to v6.
7. The migration from ibc-go v6 to v7.
8. The migration from ibc-go v7 to v7.1.
9. The migration from ibc-go v7.2 to v7.3.
10. The migration from ibc-go v7 to v8.
11. The migration from ibc-go v8 to v8.1.