Skip to content

v7.3.0
Compare
Choose a tag to compare
@crodriguezvega crodriguezvega released this 31 Aug 19:25
· 18 commits to release/v7.3.x since this release
v7.3.0
c75650a
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

UPDATES

This release main additions are:

Support for JSON encoding of ICA transactions

We have added support for JSON encoding of transactions in the Interchain Accounts packet data. During ICA channel handshake it is possible, using the encoding of the channel version metadata , to indicate that the ICA transactions in the data field of InterchainAccountPacketData will be proto3 JSON encoded. See the Transaction Encoding section in the documentation for more information.

Support for ADR 8 middleware

We have added a set of optional interfaces that IBC applications can implement, so that the callbacks middleware can target these interfaces in order to get the desired callback addresses on the source and destination chains and execute actions on packet lifecycle events. See the Callbacks Middleware section in the documentation for more information.

Shout-out to @srdtrk for all the 🌟🦄 amazing🥇🙇 work on both features.

Please see the v7.3.0 changelog for the full set of changes included in this release. Please also note that this release requires a coordinated upgrade. We present here a summary of other relevant changes included in this release:

dependencies

  • Cosmos SDK has been bumped to v0.47.4.

light-clients/06-solomachine

  • Solo machines are now expected to sign data on a path that 1) does not include a connection prefix (e.g. ibc) and 2) does not escape any characters. Because of this change we recommend NOT using the solo machine light client of versions lower than v7.3.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.47.4 and ibc-go v7.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 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.

Contributors

srdtrk
Assets 11
Loading