Merge branch 'main' into marko/15780

.github/.codespellignore

@@ -0,0 +1,6 @@
+cips
+pullrequest
+keypair
+pastTime
+hasTables
+Nam

.github/pr_labeler.yml

@@ -70,7 +70,7 @@
   - docker-compose.yml
   - scripts/*
 "Type: CI":
-  - .github/**/*.yml
+  - .github/**
   - buf.yaml
   - .mergify.yml
   - .golangci.yml

.github/workflows/codeql-analysis.yml

@@ -29,7 +29,7 @@ jobs:
           check-latest: true
       # Initializes the CodeQL tools for scanning.
       - name: Initialize CodeQL
-        uses: github/codeql-action/init@v2
+        uses: github/codeql-action/init@v3
         with:
           languages: "go"
           queries: +security-and-quality,github/codeql/go/ql/src/experimental/InconsistentCode/DeferInLoop.ql@main,github/codeql/go/ql/src/experimental/Unsafe/WrongUsageOfUnsafe.ql@main,github/codeql/go/ql/src/experimental/CWE-369/DivideByZero.ql@main
@@ -42,7 +42,7 @@ jobs:
       # Autobuild attempts to build any compiled languages  (C/C++, C#, or Java).
       # If this step fails, then you should remove it and run the build manually (see below)
       - name: Autobuild
-        uses: github/codeql-action/autobuild@v2
+        uses: github/codeql-action/autobuild@v3
 
       # ℹ️ Command-line programs to run using the OS shell.
       # 📚 https://git.io/JvXDl
@@ -56,4 +56,4 @@ jobs:
       #   make release
 
       - name: Perform CodeQL Analysis
-        uses: github/codeql-action/analyze@v2
+        uses: github/codeql-action/analyze@v3

.github/workflows/gosec.yml

@@ -32,7 +32,7 @@ jobs:
           args: "-exclude=G101,G107 -no-fail -fmt sarif -out results.sarif ./..."
 
       - name: Upload SARIF file
-        uses: github/codeql-action/upload-sarif@v2
+        uses: github/codeql-action/upload-sarif@v3
         with:
           # Path to SARIF file relative to the root of the repository
           sarif_file: results.sarif

.github/workflows/misspell.yml

@@ -0,0 +1,28 @@
+name: Fix typos nightly
+
+on:
+  schedule:
+    - cron: "0 12 * * *"
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+      - name: Run codespell
+        continue-on-error: true
+        run: |
+          sudo apt-get install codespell -y
+          codespell -w --skip="*.pulsar.go,*.pb.go,*.pb.gw.go,*.cosmos_orm.go,*.json,*.git,*.js,crypto/keys,fuzz,*.h,proto/tendermint,*.bin" --ignore-words=.github/.codespellignore
+      - uses: peter-evans/create-pull-request@v5
+        with:
+          token: ${{ secrets.PRBOT_PAT }}
+          commit-message: "chore: spelling errors fixes"
+          title: "chore: fix spelling errors"
+          branch: "bot/fix-typos"
+          delete-branch: true
+          body: |
+            This PR fixes typos in the codebase.
+            Please review it, and merge if everything is fine.
+            If there are proto changes, run `make proto-gen` and commit the changes.

.github/workflows/pr_labeler.yml

@@ -8,11 +8,11 @@ permissions:
 jobs:
   labeler:
     permissions:
-      contents: read  # for actions/labeler to determine modified files
-      pull-requests: write  # for actions/labeler to add labels to PRs
+      contents: read # for actions/labeler to determine modified files
+      pull-requests: write # for actions/labeler to add labels to PRs
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/labeler@main
+      - uses: actions/labeler@v4 # v5 is broken, ref https://github.com/actions/labeler/issues/712. Do not bump.
         with:
           configuration-path: .github/pr_labeler.yml
           repo-token: "${{ secrets.GITHUB_TOKEN }}"

.gitignore

@@ -18,6 +18,7 @@ dist
 tools-stamp
 buf-stamp
 artifacts
+simapp/simd/simd
 
 # Go
 go.work

CODING_GUIDELINES.md

@@ -102,7 +102,7 @@ When testing a function under a variety of different inputs, we prefer to use
 [table driven tests](https://github.com/golang/go/wiki/TableDrivenTests).
 Table driven test error messages should follow the following format
 `<desc>, tc #<index>, i #<index>`.
-`<desc>` is an optional short description of whats failing, `tc` is the
+`<desc>` is an optional short description of what's failing, `tc` is the
 index within the test case table that is failing, and `i` is when there
 is a loop, exactly which iteration of the loop failed.
 The idea is you should be able to see the

CONTRIBUTING.md

@@ -47,11 +47,15 @@ contributors, the general procedure for contributing has been established:
       to begin work.
 5. To submit your work as a contribution to the repository follow standard GitHub best practices. See [pull request guideline](#pull-requests) below.
 
-**Note:** For very small or blatantly obvious problems such as typos, you are
+**Note:** For very small or blatantly obvious problems, you are
 not required to an open issue to submit a PR, but be aware that for more complex
 problems/features, if a PR is opened before an adequate design discussion has
 taken place in a GitHub issue, that PR runs a high likelihood of being rejected.
 
+**Note 2:** At this time, we will not be accepting contributions that only fix spelling
+or grammar errors in documentation, code or elsewhere. The repository has a nightly job that
+spell checks all files and will automatically open PRs for any spelling errors.
+
 ## Teams Dev Calls
 
 The Cosmos SDK has many stakeholders contributing and shaping the project. The Core SDK team is composed of Interchain GmbH and Regen Network Development developers. Any long-term contributors and additional maintainers from other projects are welcome. We use self-organizing principles to coordinate and collaborate across organizations in structured "EPIC" that focus on specific problem domains or architectural components of the Cosmos SDK.

README.md

@@ -29,7 +29,7 @@
     <img alt="Imported by" src="https://sourcegraph.com/github.com/cosmos/cosmos-sdk/-/badge.svg" />
   </a>
     <img alt="Sims" src="https://github.com/cosmos/cosmos-sdk/workflows/Sims/badge.svg" />
-    <img alt="Lint Satus" src="https://github.com/cosmos/cosmos-sdk/workflows/Lint/badge.svg" />
+    <img alt="Lint Status" src="https://github.com/cosmos/cosmos-sdk/workflows/Lint/badge.svg" />
 </div>
 
 The Cosmos SDK is a framework for building blockchain applications. [CometBFT (BFT Consensus)](https://github.com/cometbft/cometbft) and the Cosmos SDK are written in the Go programming language. Cosmos SDK is used to build [Gaia](https://github.com/cosmos/gaia), the implementation of the Cosmos Hub.

RELEASES.md

@@ -7,13 +7,13 @@ The Cosmos-SDK follows both [0ver](https://0ver.org/) and [Semver](https://semve
 Although we adhere to semantic versioning (semver), we have introduced a few modifications to accommodate the unique characteristics of blockchains. One significant divergence is that the major version (Y.x.x) is incremented solely when a consensus-breaking change occurs. On the other hand, the minor version (x.Y.x) is increased when there is a non-consensus-breaking alteration that also results in an incompatible API change. Patch versions will be bumped for all other changes that dont break the API nor Consensus. 
 
 <p align="center">
-  <img src="docs/static/img/semver.png?raw=true" alt="Releases Semver decision tree" width="40%" />
+  <img src="docs/semver.png?raw=true" alt="Releases Semver decision tree" width="40%" />
 </p>
 
 ## 0ver Dependencies
 
 In terms of the Cosmos-SDK dependency, we adhere to a simpler versioning approach known as 0ver. This flow differs from the previous Semver flow. Under this system, when a consensus-breaking change or an API-breaking change occurs, the Cosmos-SDK team increments the minor version (x.Y.x). Conversely, when a non-consensus-breaking change and a non-API-breaking change take place, the team bumps the patch version (x.x.Y).
 
 <p align="center">
-  <img src="docs/static/img/0ver.png?raw=true" alt="Releases 0ver decision tree" width="40%" />
+  <img src="docs/0ver.png?raw=true" alt="Releases 0ver decision tree" width="40%" />
 </p>

RELEASE_PROCESS.md

@@ -206,7 +206,7 @@ The **Stable Release Managers** evaluate and approve or reject updates and backp
 according to the [stable release policy](#stable-release-policy) and [release procedure](#major-release-procedure).
 Decisions are made by consensus.
 
-Their responsibilites include:
+Their responsibilities include:
 
 * Driving the Stable Release Exception process.
 * Approving/rejecting proposed changes to a stable release series.
@@ -235,7 +235,7 @@ Note: The Cosmos SDK team is in an active process of limiting Go modules that de
 The Cosmos SDK team should strive to release modules that depend on the Cosmos SDK at the same time or soon after a major version Cosmos SDK itself.
 Those modules can be considered as part of the Cosmos SDK, but features and improvements are released at a different cadence.
 
-* When a module is supposed to be used in an app (e.g `x/` modules), due to the dependency on the SDK, tagging a new version of a module must be done from a Cosmos SDK release branch. A compability matrix must be provided in the `README.md` of that module with the corresponding versions.
+* When a module is supposed to be used in an app (e.g `x/` modules), due to the dependency on the SDK, tagging a new version of a module must be done from a Cosmos SDK release branch. A compatibility matrix must be provided in the `README.md` of that module with the corresponding versions.
 * Modules that import the SDK but do not need to be imported in an app (`e.g. cosmovisor`) must be released from the `main` branch and follow the process defined below.
 
 ### Modules that do not depend on the Cosmos SDK

ROADMAP.md

@@ -116,7 +116,7 @@ Issue: https://github.com/cosmos/iavl/issues/548
         * Users should be able to pick between delayed execution and optimistic
         * RFC/ADR is merged
         * Implementation started. 
-    * Progess:
+    * Progress:
         * On pause till ABCI 2.0 is merged
 
 ### Client UX
@@ -159,14 +159,14 @@ Issue: https://github.com/cosmos/iavl/issues/548
         * KvStoreService is being added to all modules
 * [ ] [Remove global bech32](https://github.com/cosmos/cosmos-sdk/issues/13140) 
     * Objective:
-        * Depreacte global bech32 setting
+        * Deprecate global bech32 setting
     * Progress:
         * All modules except bank use the `address.Codec`
 * [ ] Make sdk.Msg only be `proto.message`
     * Objectives: 
         * Reduce sdk.Msg to only be proto.message
         * Reduce boilerplate in `msgs.go`
-    * Progess: 
+    * Progress: 
         * [x] [Make ValidateBasic Optional](https://github.com/cosmos/cosmos-sdk/issues/15648)
         * [ ] [Make GetSigners be optional](https://github.com/cosmos/cosmos-sdk/issues/15677)
         * [ ] Remove GetsignBytes for legacy amino encoding

UPGRADING.md

@@ -14,6 +14,11 @@ Note, always read the **SimApp** section for more information on application wir
 In this section we describe the changes made in Cosmos SDK' SimApp.
 **These changes are directly applicable to your application wiring.**
 
+#### AnteHandlers
+
+The GasConsumptionDecorator and IncreaseSequenceDecorator have been merged with the SigVerificationDecorator, so you'll
+need to remove them both from your app.go code, they will yield to unresolvable symbols when compiling.
+
 #### Client (`root.go`)
 
 The `client` package has been refactored to make use of the address codecs (address, validator address, consensus address, etc.).
@@ -192,7 +197,7 @@ is `BeginBlock` -> `DeliverTx` (for all txs) -> `EndBlock`.
 ABCI++ 2.0 also brings `ExtendVote` and `VerifyVoteExtension` ABCI methods. These
 methods allow applications to extend and verify pre-commit votes. The Cosmos SDK
 allows an application to define handlers for these methods via `ExtendVoteHandler`
-and `VerifyVoteExtensionHandler` respectively. Please see [here](https://docs.cosmos.network/v0.50/building-apps/vote-extensions)
+and `VerifyVoteExtensionHandler` respectively. Please see [here](https://docs.cosmos.network/v0.50/build/abci/03-vote-extensions)
 for more info.
 
 #### Set PreBlocker