Merge branch 'main' into Susannah/multiplexed-ICA-requirements

cosmos · Jan 3, 2025 · 5e1c673 · 5e1c673
2 parents f0d6c3e + fc63b5c
commit 5e1c673
Show file tree

Hide file tree

Showing 139 changed files with 1,548 additions and 1,783 deletions.
diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
@@ -1,52 +1,5 @@
 # CODEOWNERS: https://help.github.com/articles/about-codeowners/
 
-*       @AdityaSripal @damiannolan @DimitrisJim @gjermundgaraba
-
-# Our appreciation and gratitude to past code owners: @fedekunze @seantking @tmsdkeys @charleenfei @crodriguezvega @colin-axner @chatton @bznein
-
-# Order is important; the last matching pattern takes the most
-# precedence. When someone opens a pull request that only
-# modifies 27-interchain-accounts files, only the interchain account owners 
-# and not the global owner(s) will be requested for a review.
-
-# CODEOWNERS for the CODEOWNER file
-
-/.github/CODEOWNERS @AdityaSripal @damiannolan
-
-# CODEOWNERS for the core IBC module
-
-/modules/core/ @AdityaSripal @damiannolan
-/proto/ibc/core/ @AdityaSripal @damiannolan
-
-# CODEOWNERS for the light-clients
-
-/modules/light-clients/ @AdityaSripal @damiannolan
-/proto/ibc/lightclients/ @AdityaSripal @damiannolan
-
-# CODEOWNERS for 08-wasm light client module
-
-/modules/light-clients/08-wasm/ @AdityaSripal @damiannolan @DimitrisJim @srdtrk
-
-# CODEOWNERS for ICS 20
-
-/modules/apps/transfer/ @AdityaSripal @damiannolan @DimitrisJim
-/proto/ibc/applications/transfer/ @AdityaSripal @damiannolan @DimitrisJim
-
-# CODEOWNERS for interchain-accounts module
-
-/modules/apps/27-interchain-accounts/ @AdityaSripal @damiannolan
-/proto/ibc/applications/interchain_accounts/ @AdityaSripal @damiannolan
-
-# CODEOWNERS for fee module
-
-/modules/apps/29-fee/ @AdityaSripal @damiannolan
-/proto/ibc/applications/fee/ @AdityaSripal @damiannolan
-
-# CODEOWNERS for callbacks middleware
-
-/modules/apps/callbacks/ @AdityaSripal @damiannolan @srdtrk
-
-# CODEOWNERS for docs
-
-/docs/ @AdityaSripal @damiannolan @DimitrisJim @srdtrk
+*       @AdityaSripal @gjermundgaraba @srdtrk
 
+# Our appreciation and gratitude to past code owners: @fedekunze @seantking @tmsdkeys @charleenfei @crodriguezvega @colin-axner @chatton @bznein @DimitrisJim @damiannolan
diff --git a/.github/ISSUE_TEMPLATE/bug-report.md b/.github/ISSUE_TEMPLATE/bug-report.md
@@ -12,7 +12,7 @@ v    Please also ensure that this is not a duplicate issue :)
 
 <!--
 IMPORTANT: Prior to opening a bug report, check if it affects one of the core modules
-and if its elegible for a bug bounty on `SECURITY.md`. Bugs that are not submitted
+and if its eligible for a bug bounty on `SECURITY.md`. Bugs that are not submitted
 through the appropriate channels won't receive any bounty.
  -->
 
@@ -39,4 +39,4 @@ ____
 - [ ] Not duplicate issue
 - [ ] Appropriate labels applied
 - [ ] Appropriate contributors tagged/assigned
-- [ ] Estimate provided
+- [ ] Estimate provided
diff --git a/.github/mergify.yml b/.github/mergify.yml
@@ -46,6 +46,14 @@ pull_request_rules:
       backport:
         branches:
           - 08-wasm/release/v0.3.x+ibc-go-v7.4.x-wasmvm-v1.5.x
+  - name: backport patches to v0.4.x wasm ibc-go v7.4.x & wasmvm 1.5.x branch
+    conditions:
+      - base=main
+      - label=backport-wasm-v0.4.x+ibc-go-v7.4.x-wasmvm-v1.5.x
+    actions:
+      backport:
+        branches:
+          - 08-wasm/release/v0.4.x+ibc-go-v7.4.x-wasmvm-v1.5.x
   - name: backport patches to v0.4.x wasm ibc-go v8.4.x & wasmvm 2.0.x branch
     conditions:
       - base=main
@@ -54,6 +62,14 @@ pull_request_rules:
       backport:
         branches:
           - 08-wasm/release/v0.4.x+ibc-go-v8.4.x-wasmvm-v2.0.x
+  - name: backport patches to v0.5.x wasm ibc-go v8.4.x & wasmvm 2.1.x branch
+    conditions:
+      - base=main
+      - label=backport-wasm-v0.5.x+ibc-go-v8.4.x-wasmvm-v2.1.x
+    actions:
+      backport:
+        branches:
+          - 08-wasm/release/v0.5.x+ibc-go-v8.4.x-wasmvm-v2.1.x
   - name: backport patches to v0.5.x wasm ibc-go v9.0.x & wasmvm 2.1.x branch
     conditions:
       - base=main

diff --git a/.github/workflows/callbacks.yml b/.github/workflows/callbacks.yml
@@ -23,7 +23,7 @@ jobs:
           fetch-depth: 0
       - uses: golangci/[email protected]
         with:
-          version: v1.60
+          version: v1.62
           only-new-issues: true
           args: --timeout 5m
           working-directory: modules/apps/callbacks

diff --git a/.github/workflows/discord-notify.yml b/.github/workflows/discord-notify.yml
diff --git a/.github/workflows/e2e.yaml b/.github/workflows/e2e.yaml
@@ -65,6 +65,6 @@ jobs:
       chain-a-tag: '${{ needs.determine-image-tag.outputs.simd-tag }}'
       chain-b-tag: '${{ needs.determine-image-tag.outputs.simd-tag }}'
       # on regular PRs we won't run upgrade tests.
-      # NOTE: we are exluding TestTransferTestSuite as we run this full suite instead of each individual test.
+      # NOTE: we are excluding TestTransferTestSuite as we run this full suite instead of each individual test.
       test-exclusions: 'TestUpgradeTestSuite,TestIBCWasmUpgradeTestSuite,TestTransferTestSuite,TestAuthzTransferTestSuite,TestTransferTestSuiteSendReceive,TestTransferTestSuiteSendEnabled,TestTransferLocalhostTestSuite,TestConnectionTestSuite,TestInterchainAccountsGovTestSuite,TestIncentivizedTransferTestSuite,TestTransferForwardingTestSuite'
       temp-run-full-suite: true
diff --git a/.github/workflows/e2emodule.yml b/.github/workflows/e2emodule.yml
@@ -24,7 +24,7 @@ jobs:
           fetch-depth: 0
       - uses: golangci/[email protected]
         with:
-          version: v1.60
+          version: v1.62
           only-new-issues: true
           args: --timeout 5m
           working-directory: e2e/

diff --git a/.github/workflows/golangci-feature.yml b/.github/workflows/golangci-feature.yml
@@ -29,6 +29,6 @@ jobs:
       - name: golangci-lint
         uses: golangci/[email protected]
         with:
-          version: v1.60
+          version: v1.62
           only-new-issues: true
           args: --timeout 10m
diff --git a/.github/workflows/golangci.yml b/.github/workflows/golangci.yml
@@ -25,6 +25,6 @@ jobs:
       - name: golangci-lint
         uses: golangci/[email protected]
         with:
-          version: v1.60
+          version: v1.62
           only-new-issues: true
           args: --timeout 10m
diff --git a/.github/workflows/proto-registry.yml b/.github/workflows/proto-registry.yml
@@ -13,7 +13,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
-      - uses: bufbuild/buf-setup-action@v1.47.2
+      - uses: bufbuild/buf-setup-action@v1.48.0
       - uses: bufbuild/buf-push-action@v1
         with:
           input: "proto"

diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
@@ -11,27 +11,6 @@ env:
   IMAGE_NAME: ibc-go-simd
 
 jobs:
-  goreleaser:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-
-      - uses: actions/setup-go@v5
-        with:
-          go-version: '1.23'
-
-      - name: Release
-        uses: goreleaser/goreleaser-action@v6
-        if: startsWith(github.ref, 'refs/tags/')
-        with:
-          version: latest
-          args: release --rm-dist
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-
   publish-docker-image:
     runs-on: ubuntu-latest
     steps:

diff --git a/.github/workflows/slack-notify.yaml b/.github/workflows/slack-notify.yaml
diff --git a/.github/workflows/spell-checker.yml b/.github/workflows/spell-checker.yml
@@ -1,6 +1,7 @@
 name: Spell Check
 
 on:
+  workflow_dispatch:
   pull_request:
   schedule:
     - cron: "0 12 * * *"
@@ -15,11 +16,14 @@ jobs:
 
     steps:
       - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: '3.12'
+      - name: Install codespell
+        run: pip install codespell
       - name: Run codespell
-        continue-on-error: true
-        run: |
-          sudo apt-get install codespell -y
-          codespell -w --skip="*.pb.go,*.pb.gw.go,*.json,*.git,*.js,*.h,*.bin,go.sum,go.mod,.github" --ignore-words=.github/.codespellignore
+        continue-on-error: ${{ github.event_name != 'pull_request' }}
+        run: codespell -w --skip="*.pb.go,*.pb.gw.go,*.json,*.git,*.js,*.h,*.bin,go.sum,go.mod,*.pdf,*.tla" --ignore-words=.github/.codespellignore --check-hidden
       - uses: peter-evans/create-pull-request@v7
         if: github.event_name != 'pull_request'
         with:

diff --git a/.github/workflows/wasm-client.yml b/.github/workflows/wasm-client.yml
@@ -22,7 +22,7 @@ jobs:
           fetch-depth: 0
       - uses: golangci/[email protected]
         with:
-          version: v1.60
+          version: v1.62
           only-new-issues: true
           args: --timeout 10m
           working-directory: modules/light-clients/08-wasm

diff --git a/.goreleaser.yml b/.goreleaser.yml
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -65,6 +65,8 @@ Ref: https://keepachangelog.com/en/1.0.0/
 
 ### Features
 
+* (apps/transfer) [\#7650](https://github.com/cosmos/ibc-go/pull/7650) Add support for transfer of entire balance for vesting accounts
+
 ### Bug Fixes
 
 * (apps/27-interchain-accounts) [\#7277](https://github.com/cosmos/ibc-go/pull/7277) Use `GogoResolver` when populating module query safe allow list to avoid panics from unresolvable protobuf dependencies.

diff --git a/Dockerfile b/Dockerfile
@@ -1,4 +1,4 @@
-FROM golang:1.23.3-alpine as builder
+FROM golang:1.23.4-alpine as builder
 ARG IBC_GO_VERSION
 
 RUN set -eux; apk add --no-cache gcc git libusb-dev linux-headers make musl-dev;

diff --git a/docs/docs/05-migrations/07-v5-to-v6.md b/docs/docs/05-migrations/07-v5-to-v6.md
@@ -198,10 +198,10 @@ func DefaultParams() Params {
 
 `SerializeCosmosTx` takes in a `[]proto.Message` instead of `[]sdk.Message`. This allows for the serialization of proto messages without requiring the fulfillment of the `sdk.Msg` interface.
 
-The `27-interchain-accounts` genesis types have been moved to their own package: `modules/apps/27-interchain-acccounts/genesis/types`.
+The `27-interchain-accounts` genesis types have been moved to their own package: `modules/apps/27-interchain-accounts/genesis/types`.
 This change facilitates the addition of the ICS27 controller submodule `MsgServer` and avoids cyclic imports. This should have minimal disruption to chain developers integrating `27-interchain-accounts`.
 
-The ICS27 host submodule `NewKeeper` function in `modules/apps/27-interchain-acccounts/host/keeper` now includes an additional parameter of type `ICS4Wrapper`.
+The ICS27 host submodule `NewKeeper` function in `modules/apps/27-interchain-accounts/host/keeper` now includes an additional parameter of type `ICS4Wrapper`.
 This provides the host submodule with the ability to correctly unwrap channel versions in the event of a channel reopening handshake.
 
 ```diff

diff --git a/docs/docusaurus.config.js b/docs/docusaurus.config.js
@@ -353,19 +353,19 @@ const config = {
   scripts: [
     {
       src: "https://widget.kapa.ai/kapa-widget.bundle.js",
-      "data-website-id": "806aa1dc-0d46-4563-a8b8-880eecac59f1",
+      "data-website-id": "33cd677e-ea9e-437e-a3c1-dbacbe03afc1",
       "data-project-name": "Interchain",
       "data-user-analytics-fingerprint-enabled": "true",
       "data-project-color": "#1878FF",
       "data-modal-title": "IBC Docs AI",
-      "data-modal-disclaimer": "This is a custom LLM for the Inter-Blockchain Communication Protocol in Golang (ibc-go). It is trained on the IBC developer documentation, code base, and resources. Answers are AI-generated. Please use your best judgment before implementing. The bot is not trained on documentation, code, or resources for the Cosmos SDK, CometBFT, CosmJS, CosmWasm, or interchain ecosystem blockchains. Please refer to those specific documentation sites for answers to those questions.",
+      "data-modal-disclaimer": "This is a custom LLM for the Interchain Stack with access to developer documentation and resources across the core Cosmos components. Please note that answers are generated by an AI so please use your best judgement before implementing.",
       "data-modal-ask-ai-input-placeholder": "Ask me a question about IBC...",
       "data-modal-disclaimer-text-color": "#000000",
       "data-modal-disclaimer-font-size": "14px",
       "data-modal-image":
         "/img/black-ibc-logo-400x400.svg",
       "data-project-logo":
-        "/img/white-ibc-logo-400x400.svg",
+        "/img/spirograph-white.svg",
       async: true,
     },
   ],

diff --git a/docs/static/img/spirograph-white.svg b/docs/static/img/spirograph-white.svg
diff --git a/docs/versioned_docs/version-v4.6.x/01-ibc/05-upgrades/00-intro.md b/docs/versioned_docs/version-v4.6.x/01-ibc/05-upgrades/00-intro.md
@@ -9,7 +9,7 @@ slug: /ibc/upgrades/intro
 
 This directory contains information on how to upgrade an IBC chain without breaking counterparty clients and connections.
 
-IBC-connnected chains must be able to upgrade without breaking connections to other chains. Otherwise there would be a massive disincentive towards upgrading and disrupting high-value IBC connections, thus preventing chains in the IBC ecosystem from evolving and improving. Many chain upgrades may be irrelevant to IBC, however some upgrades could potentially break counterparty clients if not handled correctly. Thus, any IBC chain that wishes to perform an IBC-client-breaking upgrade must perform an IBC upgrade in order to allow counterparty clients to securely upgrade to the new light client.
+IBC-connected chains must be able to upgrade without breaking connections to other chains. Otherwise there would be a massive disincentive towards upgrading and disrupting high-value IBC connections, thus preventing chains in the IBC ecosystem from evolving and improving. Many chain upgrades may be irrelevant to IBC, however some upgrades could potentially break counterparty clients if not handled correctly. Thus, any IBC chain that wishes to perform an IBC-client-breaking upgrade must perform an IBC upgrade in order to allow counterparty clients to securely upgrade to the new light client.
 
 1. The [quick-guide](./01-quick-guide.md) describes how IBC-connected chains can perform client-breaking upgrades and how relayers can securely upgrade counterparty clients using the SDK.
 2. The [developer-guide](./02-developer-guide.md) is a guide for developers intending to develop IBC client implementations with upgrade functionality.
diff --git a/docs/versioned_docs/version-v4.6.x/04-migrations/05-v3-to-v4.md b/docs/versioned_docs/version-v4.6.x/04-migrations/05-v3-to-v4.md
@@ -41,7 +41,7 @@ where `icaAuthIBCModule` is the Interchain Accounts authentication IBC Module.
 
 The Fee Middleware module, as the name suggests, plays the role of an IBC middleware and as such must be configured by chain developers to route and handle IBC messages correctly.
 
-Please read the Fee Middleware [integration documentation](../03-middleware/01-ics29-fee/02-integration.md) for an in depth guide on how to congfigure the module correctly in order to incentivize IBC packets. 
+Please read the Fee Middleware [integration documentation](../03-middleware/01-ics29-fee/02-integration.md) for an in depth guide on how to configure the module correctly in order to incentivize IBC packets. 
 
 Take a look at the following diff for an [example setup](https://github.com/cosmos/ibc-go/pull/1432/files#diff-d18972debee5e64f16e40807b2ae112ddbe609504a93ea5e1c80a5d489c3a08aL366) of how to incentivize ics27 channels. 
 

diff --git a/docs/versioned_docs/version-v5.4.x/01-ibc/05-upgrades/00-intro.md b/docs/versioned_docs/version-v5.4.x/01-ibc/05-upgrades/00-intro.md
@@ -2,7 +2,7 @@
 
 This directory contains information on how to upgrade an IBC chain without breaking counterparty clients and connections. 
 
-IBC-connnected chains must be able to upgrade without breaking connections to other chains. Otherwise there would be a massive disincentive towards upgrading and disrupting high-value IBC connections, thus preventing chains in the IBC ecosystem from evolving and improving. Many chain upgrades may be irrelevant to IBC, however some upgrades could potentially break counterparty clients if not handled correctly. Thus, any IBC chain that wishes to perform an IBC-client-breaking upgrade must perform an IBC upgrade in order to allow counterparty clients to securely upgrade to the new light client.
+IBC-connected chains must be able to upgrade without breaking connections to other chains. Otherwise there would be a massive disincentive towards upgrading and disrupting high-value IBC connections, thus preventing chains in the IBC ecosystem from evolving and improving. Many chain upgrades may be irrelevant to IBC, however some upgrades could potentially break counterparty clients if not handled correctly. Thus, any IBC chain that wishes to perform an IBC-client-breaking upgrade must perform an IBC upgrade in order to allow counterparty clients to securely upgrade to the new light client.
 
 1. The [quick-guide](./01-quick-guide.md) describes how IBC-connected chains can perform client-breaking upgrades and how relayers can securely upgrade counterparty clients using the SDK.
 2. The [developer-guide](./02-developer-guide.md) is a guide for developers intending to develop IBC client implementations with upgrade functionality.
diff --git a/docs/versioned_docs/version-v5.4.x/04-migrations/05-v3-to-v4.md b/docs/versioned_docs/version-v5.4.x/04-migrations/05-v3-to-v4.md
@@ -41,7 +41,7 @@ where `icaAuthIBCModule` is the Interchain Accounts authentication IBC Module.
 
 The Fee Middleware module, as the name suggests, plays the role of an IBC middleware and as such must be configured by chain developers to route and handle IBC messages correctly.
 
-Please read the Fee Middleware [integration documentation](../03-middleware/01-ics29-fee/02-integration.md) for an in depth guide on how to congfigure the module correctly in order to incentivize IBC packets. 
+Please read the Fee Middleware [integration documentation](../03-middleware/01-ics29-fee/02-integration.md) for an in depth guide on how to configure the module correctly in order to incentivize IBC packets. 
 
 Take a look at the following diff for an [example setup](https://github.com/cosmos/ibc-go/pull/1432/files#diff-d18972debee5e64f16e40807b2ae112ddbe609504a93ea5e1c80a5d489c3a08aL366) of how to incentivize ics27 channels. 
 

diff --git a/docs/versioned_docs/version-v6.3.x/01-ibc/05-upgrades/00-intro.md b/docs/versioned_docs/version-v6.3.x/01-ibc/05-upgrades/00-intro.md
@@ -9,7 +9,7 @@ slug: /ibc/upgrades/intro
 
 This directory contains information on how to upgrade an IBC chain without breaking counterparty clients and connections.
 
-IBC-connnected chains must be able to upgrade without breaking connections to other chains. Otherwise there would be a massive disincentive towards upgrading and disrupting high-value IBC connections, thus preventing chains in the IBC ecosystem from evolving and improving. Many chain upgrades may be irrelevant to IBC, however some upgrades could potentially break counterparty clients if not handled correctly. Thus, any IBC chain that wishes to perform an IBC-client-breaking upgrade must perform an IBC upgrade in order to allow counterparty clients to securely upgrade to the new light client.
+IBC-connected chains must be able to upgrade without breaking connections to other chains. Otherwise there would be a massive disincentive towards upgrading and disrupting high-value IBC connections, thus preventing chains in the IBC ecosystem from evolving and improving. Many chain upgrades may be irrelevant to IBC, however some upgrades could potentially break counterparty clients if not handled correctly. Thus, any IBC chain that wishes to perform an IBC-client-breaking upgrade must perform an IBC upgrade in order to allow counterparty clients to securely upgrade to the new light client.
 
 1. The [quick-guide](./01-quick-guide.md) describes how IBC-connected chains can perform client-breaking upgrades and how relayers can securely upgrade counterparty clients using the SDK.
 2. The [developer-guide](./02-developer-guide.md) is a guide for developers intending to develop IBC client implementations with upgrade functionality.