InjectiveLabs · boleklebovski · Aug 15, 2026
@@ -48,7 +48,7 @@ INJ 用于治理链的所有方面，包括：
 * Peggy 模块参数
 * Wasmx 模块参数
 * 软件升级
-* Cosmos-SDK 模块参数，包括 [auth](https://docs.cosmos.network/main/modules/auth#parameters)、[bank](https://docs.cosmos.network/main/modules/bank)、[crisis](https://docs.cosmos.network/main/modules/crisis)、[distribution](https://docs.cosmos.network/main/modules/distribution)、[gov](https://docs.cosmos.network/main/modules/gov)、[mint](https://docs.cosmos.network/main/modules/mint)、[slashing](https://docs.cosmos.network/main/modules/slashing) 和 [staking](https://docs.cosmos.network/main/modules/staking) 模块。
+* Cosmos-SDK 模块参数，包括 [auth](https://docs.cosmos.network/sdk/latest/modules/auth/auth#parameters)、[bank](https://docs.cosmos.network/sdk/latest/modules/bank/README)、[crisis](https://docs.cosmos.network/sdk/latest/modules/crisis/README)、[distribution](https://docs.cosmos.network/sdk/latest/modules/distribution/README)、[gov](https://docs.cosmos.network/sdk/latest/modules/gov/README)、[mint](https://docs.cosmos.network/sdk/latest/modules/mint/README)、[slashing](https://docs.cosmos.network/sdk/latest/modules/slashing/README) 和 [staking](https://docs.cosmos.network/sdk/latest/modules/staking/README) 模块。
 
 有关治理流程的完整详情，请参阅[这里](https://blog.injectiveprotocol.com/injective-governance-proposal-procedure)。
 

@@ -8,7 +8,7 @@ updatedAt: "2026-02-03"
 <Callout icon="info" color="#07C1FF" iconType="regular">
 了解 Injective 上 `Gas` 和 `Fees` 之间的区别。
 
-前置阅读 → [Cosmos SDK Gas](https://docs.cosmos.network/main/build/modules/auth#gas--fees)
+前置阅读 → [Cosmos SDK Gas](https://docs.cosmos.network/sdk/latest/modules/auth/auth#antehandlers)
 </Callout>
 
 Gas 代表在状态机上执行特定操作所需的计算工作量。
@@ -36,7 +36,7 @@ Gas 用于确保操作不需要过多的计算能力来完成，并阻止恶意
 * `GasMeter`：跟踪导致状态转换的执行期间消耗的 gas。它在每次交易执行时重置。
 * `BlockGasMeter`：跟踪区块中消耗的 gas，并强制 gas 不超过预定义的限制。此限制在 Tendermint 共识参数中定义，可以通过治理参数更改提案进行更改。
 
-有关 Cosmos SDK 中 gas 的更多信息，请参阅[这里](https://docs.cosmos.network/main/learn/beginner/gas-fees)。
+有关 Cosmos SDK 中 gas 的更多信息，请参阅[这里](https://docs.cosmos.network/sdk/latest/learn/concepts/context-gas-events)。
 
 在 Cosmos 中，有些操作类型不是由交易触发的，但也可能导致状态转换。具体例子是 `BeginBlock` 和 `EndBlock` 操作以及 `AnteHandler` 检查，它们可能在运行交易的状态转换之前也会读取和写入存储。
 
@@ -46,4 +46,4 @@ Gas 用于确保操作不需要过多的计算能力来完成，并阻止恶意
 
 #### `AnteHandler`
 
-Cosmos SDK [`AnteHandler`](https://docs.cosmos.network/v0.45/modules/auth/03_antehandlers.html) 在交易执行之前执行基本检查。这些检查通常是签名验证、交易字段验证、交易费用等。
+Cosmos SDK [`AnteHandler`](https://docs.cosmos.network/sdk/latest/modules/auth/auth#antehandlers) 在交易执行之前执行基本检查。这些检查通常是签名验证、交易字段验证、交易费用等。
@@ -10,7 +10,7 @@ updatedAt: "2026-02-03"
 
 前置阅读：
 
-* [Cosmos SDK 账户](https://docs.cosmos.network/main/basics/accounts)
+* [Cosmos SDK 账户](https://docs.cosmos.network/sdk/latest/learn/concepts/accounts)
 * [Ethereum 账户](https://ethereum.org/en/whitepaper/#ethereum-accounts)
 </Callout>
 

@@ -30,7 +30,7 @@ updatedAt: "2026-02-13"
 "/injective.exchange.v1beta1.MsgWithdraw",
 ```
 
-根据 [cosmos sdk 文档](https://docs.cosmos.network/main/modules/authz)，"授权必须针对特定的 Msg 服务方法逐一授予"，因此以下代码片段必须针对您希望 `grantee` 代表 `granter` 拥有授权的每种消息类型重复执行。
+根据 [cosmos sdk 文档](https://docs.cosmos.network/sdk/latest/modules/authz/README)，"授权必须针对特定的 Msg 服务方法逐一授予"，因此以下代码片段必须针对您希望 `grantee` 代表 `granter` 拥有授权的每种消息类型重复执行。
 
 ```ts
 import { Network } from "@injectivelabs/networks";

@@ -3,7 +3,7 @@ title: Web3 Gateway 交易
 updatedAt: "2026-02-13"
 ---
 
-_前置阅读 #1:_ [交易生命周期](https://docs.cosmos.network/main/basics/tx-lifecycle)
+_前置阅读 #1:_ [交易生命周期](https://docs.cosmos.network/sdk/latest/learn/concepts/lifecycle)
 
 _前置阅读 #2:_ Injective 上的交易
 

@@ -3,7 +3,7 @@ title: 链下（任意）数据
 updatedAt: "2026-02-13"
 ---
 
-本页面将提供如何根据 Cosmos 的 [ADR-036](https://docs.cosmos.network/main/build/architecture/adr-036-arbitrary-signature) 规范签名和验证任意数据的示例。
+本页面将提供如何根据 Cosmos 的 [ADR-036](https://docs.cosmos.network/sdk/latest/reference/architecture/adr-036-arbitrary-signature) 规范签名和验证任意数据的示例。
 
 <Callout icon="info" color="#07C1FF" iconType="regular">
 你可以使用 `@injectivelabs/sdk-ts` 中的 `generateArbitrarySignDoc` 函数来生成 ADR-36 兼容的 `signDoc`。然后你可以在浏览器钱包或 CLI 环境中使用它进行签名/验证。请确保使用最新的包版本。

@@ -186,7 +186,7 @@ Peggo 支持两种提供 Cosmos 签名密钥凭证的选项 - 使用 Cosmos keyr
 
 要使用默认的 injectived 密钥配置，你应该将 keyring 路径设置为你的 injectived 节点的主目录，例如 `~/.injectived`。
 
-你也可以在[这里](https://docs.cosmos.network/v0.46/run-node/keyring.html)阅读更多关于 Cosmos Keyring 设置的信息。
+你也可以在[这里](https://docs.cosmos.network/sdk/latest/node/keyring)阅读更多关于 Cosmos Keyring 设置的信息。
 
 #### **选项 2. Cosmos 私钥（不安全）**
 
@@ -282,7 +282,7 @@ journalctl -f -u peggo
 这是一个高级 DevOps 主题，请咨询你的系统管理员。
 </Callout>
 
-在[这里](https://docs.cosmos.network/v0.46/run-node/keyring.html)了解更多关于 Cosmos Keyring 设置的信息。一旦你启动了节点，默认的 keyring 将以加密形式将验证者操作员密钥存储在磁盘上。通常 keyring 位于节点的主目录中，即 `~/.injectived/keyring-file`。
+在[这里](https://docs.cosmos.network/sdk/latest/node/keyring)了解更多关于 Cosmos Keyring 设置的信息。一旦你启动了节点，默认的 keyring 将以加密形式将验证者操作员密钥存储在磁盘上。通常 keyring 位于节点的主目录中，即 `~/.injectived/keyring-file`。
 
 Injective 质押文档的某些部分将指导你使用此密钥进行治理目的，即提交交易和设置以太坊桥接。为了保护密钥免受未授权访问，即使 keyring 密码通过配置泄露，你也可以设置操作系统权限，仅允许 `injectived` / `peggo` 进程访问磁盘。
 

@@ -29,7 +29,7 @@ Peggo 还需要访问你的验证者的 Cosmos 和以太坊凭证来为相应的
 
 如果你想重用那里的密钥，Keyring 路径必须指向你的 injectived 节点的主目录。
 
-在[这里](https://docs.cosmos.network/v0.46/run-node/keyring.html)了解更多关于 Keyring 设置的信息。
+在[这里](https://docs.cosmos.network/sdk/latest/node/keyring)了解更多关于 Keyring 设置的信息。
 
 ### **2. Cosmos 私钥（不安全）**
 
@@ -163,7 +163,7 @@ journalctl -f -u peggo
 这是一个高级 DevOps 主题，请咨询你的系统管理员。
 </Callout>
 
-在[这里](https://docs.cosmos.network/v0.46/run-node/keyring.html)了解更多关于 Cosmos Keyring 设置的信息。一旦你启动了节点，默认的 keyring 将以加密形式将验证者操作员密钥存储在磁盘上。通常，keyring 位于节点的主目录中，即 `~/.injectived/keyring-file`。
+在[这里](https://docs.cosmos.network/sdk/latest/node/keyring)了解更多关于 Cosmos Keyring 设置的信息。一旦你启动了节点，默认的 keyring 将以加密形式将验证者操作员密钥存储在磁盘上。通常，keyring 位于节点的主目录中，即 `~/.injectived/keyring-file`。
 
 Injective 质押文档的某些部分将指导你使用此密钥进行治理目的，即提交交易和设置以太坊桥接。为了保护密钥免受未授权访问，即使 keyring 密码通过配置泄露，你也可以设置操作系统权限，仅允许 `injectived` / `peggo` 进程访问磁盘。
 

@@ -22,7 +22,7 @@ updatedAt: "2026-06-18"
 | [Injective TypeScript SDK](https://github.com/InjectiveLabs/injective-ts)                                 | 使用 TypeScript 在 Injective 上构建 dApp                                                                                   |
 | [Injective API Reference](https://api.injective.exchange)                                     | 面向交易者的 Injective 交互详细 API 文档                                                       |
 | [Cosmovisor](./infra/cosmovisor/)                                                 | 围绕 Cosmos SDK 二进制文件的小型进程管理器，用于监控治理模块                                        |
-| [CosmosSDK](https://docs.cosmos.network/main/build)                                          | Cosmos SDK 文档，是与 Injective 生态系统集成的开发者的宝贵资源         |
+| [CosmosSDK](https://docs.cosmos.network/sdk/latest/learn)                                          | Cosmos SDK 文档，是与 Injective 生态系统集成的开发者的宝贵资源         |
 
 ### 生态系统工具和资源
 

@@ -58,7 +58,7 @@ INJ is used to govern all aspects of the chain, including:
 * Peggy Module Parameters
 * Wasmx Module Parameters
 * Software upgrades
-* Cosmos-SDK module parameters for the [auth](https://docs.cosmos.network/main/modules/auth#parameters), [bank](https://docs.cosmos.network/main/modules/bank), [crisis](https://docs.cosmos.network/main/modules/crisis), [distribution](https://docs.cosmos.network/main/modules/distribution), [gov](https://docs.cosmos.network/main/modules/gov), [mint](https://docs.cosmos.network/main/modules/mint), [slashing](https://docs.cosmos.network/main/modules/slashing), and [staking](https://docs.cosmos.network/main/modules/staking) modules.
+* Cosmos-SDK module parameters for the [auth](https://docs.cosmos.network/sdk/latest/modules/auth/auth#parameters), [bank](https://docs.cosmos.network/sdk/latest/modules/bank/README), [crisis](https://docs.cosmos.network/sdk/latest/modules/crisis/README), [distribution](https://docs.cosmos.network/sdk/latest/modules/distribution/README), [gov](https://docs.cosmos.network/sdk/latest/modules/gov/README), [mint](https://docs.cosmos.network/sdk/latest/modules/mint/README), [slashing](https://docs.cosmos.network/sdk/latest/modules/slashing/README), and [staking](https://docs.cosmos.network/sdk/latest/modules/staking/README) modules.
 
 Full details on the governance process can be found [here](https://blog.injectiveprotocol.com/injective-governance-proposal-procedure).
 

@@ -8,7 +8,7 @@ updatedAt: "2025-10-30"
 <Callout icon="info" color="#07C1FF" iconType="regular">
 Learn about the differences between `Gas` and `Fees` on Injective.
 
-Pre-requisite Readings → [Cosmos SDK Gas](https://docs.cosmos.network/main/build/modules/auth#gas--fees)
+Pre-requisite Readings → [Cosmos SDK Gas](https://docs.cosmos.network/sdk/latest/modules/auth/auth#antehandlers)
 </Callout>
 
 Gas represents the amount of computational effort required to execute specific operations on the state machine.
@@ -36,7 +36,7 @@ In the Cosmos SDK, gas is tracked in the main `GasMeter` and the `BlockGasMeter`
 * `GasMeter`: keeps track of the gas consumed during executions that lead to state transitions. It is reset on every transaction execution.
 * `BlockGasMeter`: keeps track of the gas consumed in a block and enforces that the gas does not go over a predefined limit. This limit is defined in the Tendermint consensus parameters and can be changed via governance parameter change proposals.
 
-More information regarding gas in Cosmos SDK can be found [here](https://docs.cosmos.network/main/learn/beginner/gas-fees).
+More information regarding gas in Cosmos SDK can be found [here](https://docs.cosmos.network/sdk/latest/learn/concepts/context-gas-events).
 
 In Cosmos, there are types of operations that are not triggered by transactions that can also result in state transitions. Concrete examples are the `BeginBlock` and `EndBlock` operations and the `AnteHandler` checks, which might also read and write to the store before running the state transition from a transaction.
 
@@ -46,4 +46,4 @@ These operations are defined by the Tendermint Core's Application Blockchain Int
 
 #### `AnteHandler`
 
-The Cosmos SDK [`AnteHandler`](https://docs.cosmos.network/v0.45/modules/auth/03_antehandlers.html) performs basic checks prior to transaction execution. These checks are usually signature verification, transaction field validation, transaction fees, etc.
+The Cosmos SDK [`AnteHandler`](https://docs.cosmos.network/sdk/latest/modules/auth/auth#antehandlers) performs basic checks prior to transaction execution. These checks are usually signature verification, transaction field validation, transaction fees, etc.
@@ -10,7 +10,7 @@ This document describes the built-in accounts system of Injective.
 
 Pre-requisite Readings:
 
-* [Cosmos SDK Accounts](https://docs.cosmos.network/main/basics/accounts)
+* [Cosmos SDK Accounts](https://docs.cosmos.network/sdk/latest/learn/concepts/accounts)
 * [Ethereum Accounts](https://ethereum.org/en/whitepaper/#ethereum-accounts)
 </Callout>
 

@@ -139,7 +139,7 @@ message BaseAccount {
 
 ### Vesting Account
 
-See [Vesting](https://docs.cosmos.network/main/modules/auth/vesting/).
+See [Vesting](https://docs.cosmos.network/sdk/latest/modules/auth/vesting).
 
 ## AnteHandlers
 

@@ -83,7 +83,7 @@ https://github.com/cosmos/cosmos-sdk/blob/v0.47.0-rc1/x/bank/types/send_authoriz
 
 #### StakeAuthorization
 
-`StakeAuthorization` implements the `Authorization` interface for messages in the [staking module](https://docs.cosmos.network/v0.50/build/modules/staking). It takes an `AuthorizationType` to specify whether you want to authorise delegating, undelegating or redelegating (i.e. these have to be authorised separately). It also takes an optional `MaxTokens` that keeps track of a limit to the amount of tokens that can be delegated/undelegated/redelegated. If left empty, the amount is unlimited. Additionally, this Msg takes an `AllowList` or a `DenyList`, which allows you to select which validators you allow or deny grantees to stake with.
+`StakeAuthorization` implements the `Authorization` interface for messages in the [staking module](https://docs.cosmos.network/sdk/latest/modules/staking/README). It takes an `AuthorizationType` to specify whether you want to authorise delegating, undelegating or redelegating (i.e. these have to be authorised separately). It also takes an optional `MaxTokens` that keeps track of a limit to the amount of tokens that can be delegated/undelegated/redelegated. If left empty, the amount is unlimited. Additionally, this Msg takes an `AllowList` or a `DenyList`, which allows you to select which validators you allow or deny grantees to stake with.
 
 ```protobuf reference
 https://github.com/cosmos/cosmos-sdk/blob/v0.47.0-rc1/proto/cosmos/staking/v1beta1/authz.proto#L11-L35

@@ -13,20 +13,20 @@ Circuit Breaker works with the idea that an address or set of addresses have the
 
 The transactions are checked and can be rejected at two points:
 
-* In `CircuitBreakerDecorator` [ante handler](https://docs.cosmos.network/main/learn/advanced/baseapp#antehandler):
+* In `CircuitBreakerDecorator` [ante handler](https://docs.cosmos.network/sdk/latest/learn/concepts/baseapp#antehandler):
 
 ```go reference
 https://github.com/cosmos/cosmos-sdk/blob/x/circuit/v0.1.0/x/circuit/ante/circuit.go#L27-L41
 ``` 
 
-* With a [message router check](https://docs.cosmos.network/main/learn/advanced/baseapp#msg-service-router):
+* With a [message router check](https://docs.cosmos.network/sdk/latest/learn/concepts/baseapp#message-routing):
 
 ```go reference
 https://github.com/cosmos/cosmos-sdk/blob/v0.50.1/baseapp/msg_service_router.go#L104-L115
 ``` 
 
 :::note
-The `CircuitBreakerDecorator` works for most use cases, but [does not check the inner messages of a transaction](https://docs.cosmos.network/main/learn/beginner/tx-lifecycle#antehandler). This some transactions (such as `x/authz` transactions or some `x/gov` transactions) may pass the ante handler. **This does not affect the circuit breaker** as the message router check will still fail the transaction.
+The `CircuitBreakerDecorator` works for most use cases, but [does not check the inner messages of a transaction](https://docs.cosmos.network/sdk/latest/learn/concepts/lifecycle#step-1-antehandler). This some transactions (such as `x/authz` transactions or some `x/gov` transactions) may pass the ante handler. **This does not affect the circuit breaker** as the message router check will still fail the transaction.
 This tradeoff is to avoid introducing more dependencies in the `x/circuit` module. Chains can re-define the `CircuitBreakerDecorator` to check for inner messages if they wish to do so.
 :::
 
@@ -105,7 +105,7 @@ Reset is called by an authorized account to enable execution for a specific msgU
 ### MsgAuthorizeCircuitBreaker
 
 ```protobuf reference
-https://github.com/cosmos/cosmos-sdk/blob/main/proto/cosmos/circuit/v1/tx.proto#L25-L75
+https://github.com/cosmos/cosmos-sdk/blob/x/circuit/v0.1.0/proto/cosmos/circuit/v1/tx.proto#L25-L40
 ```
 
 This message is expected to fail if:
@@ -115,7 +115,7 @@ This message is expected to fail if:
 ### MsgTripCircuitBreaker
 
 ```protobuf reference 
-https://github.com/cosmos/cosmos-sdk/blob/main/proto/cosmos/circuit/v1/tx.proto#L77-L93
+https://github.com/cosmos/cosmos-sdk/blob/x/circuit/v0.1.0/proto/cosmos/circuit/v1/tx.proto#L47-L60
 ```
 
 This message is expected to fail if:
@@ -125,7 +125,7 @@ This message is expected to fail if:
 ### MsgResetCircuitBreaker
 
 ```protobuf reference
-https://github.com/cosmos/cosmos-sdk/blob/main/proto/cosmos/circuit/v1/tx.proto#L95-109
+https://github.com/cosmos/cosmos-sdk/blob/x/circuit/v0.1.0/proto/cosmos/circuit/v1/tx.proto#L67-L78
 ```
 
 This message is expected to fail if:

@@ -45,7 +45,7 @@ The genutil commands are available under the `genesis` subcommand.
 
 #### add-genesis-account
 
-Add a genesis account to `genesis.json`. Learn more [here](https://docs.cosmos.network/main/run-node/run-node#adding-genesis-accounts).
+Add a genesis account to `genesis.json`. Learn more [here](https://docs.cosmos.network/sdk/latest/node/run-node#3-add-genesis-accounts).
 
 #### collect-gentxs
 

@@ -30,7 +30,7 @@ List of useful message types:
 "/injective.exchange.v1beta1.MsgWithdraw",
 ```
 
-Per [cosmos sdk docs](https://docs.cosmos.network/main/modules/authz), "Authorizations must be granted for a particular Msg service method one by one", so the following code snippet must be repeated for each message type that you would like for the `grantee` to have authorization on behalf of a `granter`.
+Per [cosmos sdk docs](https://docs.cosmos.network/sdk/latest/modules/authz/README), "Authorizations must be granted for a particular Msg service method one by one", so the following code snippet must be repeated for each message type that you would like for the `grantee` to have authorization on behalf of a `granter`.
 
 ```ts
 import { Network } from "@injectivelabs/networks";