v11.1.0

Description

This release introduces packet forward middleware (moved from ibc-apps) and includes several validation, dependency updates, and fixes. For a complete list of updates, see the full changelog.

New Features

Packet Forward Middleware

Packet Forward Middleware enables multi-hop ICS20 transfers by allowing packets to include forwarding metadata. Chains can use this middleware to forward received transfer packets to another IBC channel, supporting routed token transfers across multiple chains.

What's Changed

• feat(apps/pfm): backport of packet forward middleware by @srdtrk in #8921
• imp(simapp): added upgrade handler for v11.1 by @srdtrk in #8934
• imp(apps/pfm): use addressCodec in GetReceiver (backport #8932) by @mergify[bot] in #8940
• imp(apps/pfm): use channeltypes.NewErrorAcknowledgement instead of internal functions (backport #8933) by @mergify[bot] in #8941
• fix(light-clients/attestation): allow initial height to be zero (backport #8910) by @mergify[bot] in #8947
• imp(transfer): add extra validation to v2 module based on v1 validation (backport #8939) by @mergify[bot] in #8949
• chore(light-clients/08-wasm): bump to wasmvm@v3 (backport #8922) by @mergify[bot] in #8950
• imp(apps/27-gmp): add extra validation during unmarshals (backport #8945) by @mergify[bot] in #8953

Full Diff: v11.0.0...v11.1.0

v10.7.0

Description

This small release improves IBC v2 reliability by tightening transfer validation and fixing channel v2 queries for packet commitments and acknowledgements that use binary store keys.

Migration Guide

No migration is required.

What's Changed

• imp(transfer): add extra validation to v2 module based on v1 validation (backport #8939) by @mergify[bot] in #8948
• fix(channel/v2): parse binary store keys in PacketCommitments and PacketAcknowledgements queries (backport #8778) by @mergify[bot] in #8954

Full Diff: v10.6.0...v10.7.0

modules/light-clients/08-wasm/v11.1.0

Description

The 08-wasm light client module now uses wasmvm v3.

Migration Guide

No migration is required.

v10.6.0

ibc-go v10.6.0 Release Notes

This release fixes a potential blockage of the IBC v2 packet life cycle, caused by incorrect handling of an error in the callbacks middleware.

Migration Guide

This version requires a coordinated upgrade as it contains a state breaking change.

What's Changed

• fix(callbacks/v2): OnTimeoutPacket blocked by UnmarshalPacketData error (backport #8856) by @mergify[bot] in #8911

Full Changelog: v10.5.1...v10.6.0

v11.0.0

ibc-go v11.0.0 Release Notes

This release introduces several notable changes in ibc-go v11.0.0. For a complete list of updates, see the full changelog.

New Features

This release adds new modules that must be explicitly wired into your application before they can be used. The IBC-Go documentation includes integration and migration guides.

ICS27-GMP (General Message Passing)

ICS27-GMP is a new IBC application that is supported only over IBC v2 connections. It serves as the IBC v2 successor to Interchain Accounts.

This application enables cross-chain contract calls and message execution across EVM, Cosmos SDK, and Solana environments. See the IBC specifications for more details.

Attestation Light Client

The Attestation Light Client is an m-of-n multisig light client that implements the IBC Light Client interface. An attester set signs state attestations and packet commitment attestations.

At this stage, this light client is intended primarily for connecting to chains that do not have a native light client protocol, or for testing purposes. It is not a replacement for the 07-tendermint light client.

Dependency Updates

We have upgraded to Cosmos SDK v0.54 and CometBFT v0.39.

Improvements

Middleware Wiring

Middleware wiring for IBC v1 applications has been improved. See the IBC-Go documentation for more details.

v10.5.1

ibc-go v10.5.1 Release Notes

This release fixes a failure caused by non-UTF8 values being included in error/event emission. View the full changelog for more details.

Migration Guide

This version does not contain any state or API breaking changes.

What's Changed

• chore(simapp): wireup IBC v2 router by @srdtrk in #8847
• fix(transfer): use packet sender and receiver string in unauthorized error (backport #8874) by @mergify[bot] in #8879
• chore(docs): removed docs in release branch by @srdtrk in #8880

Full Changelog: v10.5.0...v10.5.1

v10.5.0

ibc-go v10.5.0 Release Notes

This release adds more integrity validations to ProtoJSON encoded ICA packets. View the full changelog for more details.

Migration Guide

This version does not contain any breaking changes to any API, but it is state-breaking and can be migrated to with a coordinated chain upgrade. If you are upgrading from v8 or earlier, see the migration documentation below.

Migration documentation is found here.

v8.8.0

ibc-go v8.8.0 Release Notes

This release adds more integrity validations to ProtoJSON encoded ICA packets. View the full changelog for more details.

Migration Guide

This version does not contain any breaking changes to any API, but it is state-breaking and can be migrated to with a coordinated chain upgrade. If you are upgrading from v7 or earlier, see the migration documentation below.

Migration documentation is found here.

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

08-wasm v10.5.0 Release Notes

There are no significant changes to the 08-wasm module itself beyond using ibc-go v10.5.0, to view all the changes in ibc-go v10.5.0, see the release notes for more details.

Migration Guide

This version does not contain any breaking changes to any API, and can be migrated to with a coordinated chain upgrade. If you are upgrading from v8 or earlier, see the migration documentation below.

Migration documentation is found here.

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

08-wasm v10.4.0 Release Notes

There are no significant changes to the 08-wasm module itself beyond using ibc-go v10.4.0, to view all the changes in ibc-go v10.4.0, see the release notes for more details.

Migration Guide

This version does not contain any breaking changes to any API, and can be migrated to with a coordinated chain upgrade. If you are upgrading from v8 or earlier, see the migration documentation below.

Migration documentation is found here.