Skip to content

v4.1.0
Compare
Choose a tag to compare
@crodriguezvega crodriguezvega released this 20 Sep 14:54
· 32 commits to release/v4.1.x since this release
v4.1.0
197555e
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

  • 25th May 2023: This release is NOT recommended since it is impacted by the huckleberry security advisory. Please use version >= 4.1.3.
  • 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 >= 4.1.1.
  • 20th September 2022: fee-enabled Interchain Accounts channels cannot be reopened in case of channel closure due to packet timeout. Regular Interchain Accounts channels (i.e. non fee-enabled) can be reopened. In order to be able to reopen fee-enabled Interchain Accounts channels, please upgrade to v5.0.0 or above.

This release includes a fix for a security vulnerability identified in the ICS27 host submodule. User funds in accounts and staking delegations are NOT at risk.

This release uses Cosmos SDK v0.45.8 and Tendermint v0.34.21. For more information, see Cosmos SDK v0.45.8 Release Notes and Tendermint v0.34.21 Changelog.

We present here the other changes in this release. Please see the v4.1.0 changelog for more information.

apps/27-interchain-accounts

  • The InterchainAccount query RPC method and CLI query have been added to the controller submodule to allow end users the ability to inspect the interchain account address generated on the host chain.
  • Nil checks have been added to ensure services are not registered for nil host or controller keepers.

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.8 and ibc-go v4.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 from ibc-go v3 to v4.
Assets 11
Loading