sei-protocol · alexander-sei · Aug 1, 2026 · Aug 1, 2026 · Aug 1, 2026 · github-actions
diff --git a/cosmos-sdk/index.mdx b/cosmos-sdk/index.mdx
@@ -14,6 +14,6 @@ Cosmos SDK and CosmWasm functionality is being deprecated in favor of EVM-only.
 
 In addition, [Proposal 115](https://seistream.app/proposals/115) disables CosmWasm code uploads (`MsgStoreCode`) and contract instantiations (`MsgInstantiateContract`) chain-wide. No new CosmWasm contracts can be deployed; only `execute` and `query` against pre-existing contracts remain available via the [CosmWasm precompile](/evm/precompiles/cosmwasm-precompiles/cosmwasm).
 
-[Proposal 116](https://seistream.app/proposals/116) additionally disables inbound IBC transfers. After this passes and is activated, IBC assets bridged from Cosmos chains can no longer arrive on Sei. [Proposal 120](https://seistream.app/proposals/120) re-disables inbound IBC (setting the `ibc` module's `InboundEnabled` parameter to `false`) while leaving outbound IBC unchanged. See the [SIP-03 Migration Guide](/learn/sip-03-migration) for affected assets and migration routes.
+**IBC is now disabled in both directions.** [Proposal 116](https://seistream.app/proposals/116) and [Proposal 120](https://seistream.app/proposals/120) set the `ibc` module's `InboundEnabled` parameter to `false`, and [Proposal 121](https://seistream.app/proposals/121) set `OutboundEnabled` to `false` on July 31, 2026. No asset can be bridged into or out of Sei over IBC, and IBC assets already on Sei can no longer be redeemed on their origin chain. See the [SIP-03 Migration Guide](/learn/sip-03-migration) for the full explanation and the list of affected assets.
 
 </Danger>
diff --git a/docs.json b/docs.json
@@ -663,7 +663,7 @@
     },
     {
       "source": "/evm/precompiles/cosmwasm-precompiles/ibc",
-      "destination": "/learn/sip-03-migration",
+      "destination": "/learn/sip-03-migration#ibc-is-disabled",
       "permanent": true
     },
     {
@@ -1673,7 +1673,7 @@
     "library": "fontawesome"
   },
   "banner": {
-    "content": "**Action required: IBC assets on Sei will become inaccessible**    If you hold [USDC.n](https://seiscan.io/address/0x3894085Ef7Ff0f0aeDf52E2A2704928d1Ec074F1) (USDC via Noble), [USDT.kava](https://seiscan.io/address/0xb75d0b03c06a926e488e2659df1a861f860bd3d1) (Kava USDT), Wormhole-bridged tokens, or any other IBC asset on Sei, you **must** swap, migrate, or bridge out **before the governance proposal to disable inbound/outbound IBC transfers passes and is activated** to avoid permanent loss of access. After this, Sei will no longer support IBC bridging of assets from Cosmos-based chains to and from Sei Network.    Consult the [SIP-03 Migration Guide](/learn/sip-03-migration) for the full list of affected assets, required actions, and supported routes.    For USDC.n specifically, see: [Holders of USDC.n Need to Swap or Migrate](https://blog.sei.io/announcements/holders-of-usdcn-need-to-swap-or-migrate/).",
+    "content": "**IBC is disabled on Sei in both directions**    [Proposal #121](https://seistream.app/proposals/121) passed on July 31, 2026 and disabled outbound IBC transfers. Inbound IBC was already disabled by [Proposal #116](https://seistream.app/proposals/116) and [Proposal #120](https://seistream.app/proposals/120). No asset can be bridged into or out of Sei over IBC.    If you hold [USDC.n](https://seiscan.io/address/0x3894085Ef7Ff0f0aeDf52E2A2704928d1Ec074F1) (USDC via Noble), [USDT.kava](https://seiscan.io/address/0xb75d0b03c06a926e488e2659df1a861f860bd3d1) (Kava USDT), ATOM, WBTC, or any other IBC asset on Sei, it can no longer be redeemed on its origin chain. The balance still exists on Sei and can still be transferred within Sei.    See the [SIP-03 Migration Guide](/learn/sip-03-migration) for what changed, the full list of affected assets, and what remains possible.",
     "dismissible": true
   }
 }
diff --git a/evm/differences-with-ethereum.mdx b/evm/differences-with-ethereum.mdx
@@ -39,7 +39,7 @@
 
 [Proposal 115](https://seistream.app/proposals/115) further disables CosmWasm code uploads and contract instantiations chain-wide — no new CosmWasm contracts can be deployed. Only `execute` and `query` against pre-existing CosmWasm contracts remain available.
 
-[Proposal 116](https://seistream.app/proposals/116) additionally disables inbound IBC transfers — IBC assets bridged from Cosmos chains can no longer arrive on Sei after this passes and is activated. [Proposal 120](https://seistream.app/proposals/120) re-disables inbound IBC (setting the `ibc` module's `InboundEnabled` parameter to `false`) while leaving outbound IBC unchanged. See the [SIP-03 Migration Guide](/learn/sip-03-migration) for affected assets and migration routes.
+**IBC is now disabled in both directions.** [Proposal 116](https://seistream.app/proposals/116) and [Proposal 120](https://seistream.app/proposals/120) set the `ibc` module's `InboundEnabled` parameter to `false`, and [Proposal 121](https://seistream.app/proposals/121) set `OutboundEnabled` to `false` on July 31, 2026. No asset can be bridged into or out of Sei over IBC, and IBC assets already on Sei can no longer be redeemed on their origin chain. See the [SIP-03 Migration Guide](/learn/sip-03-migration) for the full explanation and the list of affected assets.
 
 </Danger>
 
@@ -50,7 +50,7 @@
  - User accounts on Sei have [two addresses](/learn/accounts) derived from the same public key (Cosmos Bech32 and EVM-compatible 0x…)
  - Interoperability between EVM and Cosmos-SDK modules is governed and navigated via [precompiles](/evm/precompiles/example-usage) and [pointer contracts](/learn/pointers)

 ## Sei EVM Release

 Sei EVM was originally deployed at the following block heights and versions:

@@ -66,7 +66,7 @@
 - **Height:** `79123881`
 - **Changelog:** https://github.com/sei-protocol/sei-chain/blob/main/CHANGELOG.md#v552

 ## Opcode Differences

 | Opcode | Sei EVM | Ethereum | Notes |
 | --- | --- | --- | --- |
@@ -80,7 +80,7 @@
 | Blob‑related opcodes | Not supported (Pectra without blobs) | Supported post‑Cancun (EIP‑4844) | Blob transactions are not enabled on Sei. |


 ### PREVRANDAO

 Since Sei doesn't rely on the same pseudo‑randomness way of determining the next
 validator like Proof of Stake (PoS) Ethereum does, it doesn't have the
@@ -94,19 +94,19 @@
 Coinbase address on Sei is always set to (the EVM address of) the global fee
 collector.

 ## State Root

 Since Sei uses AVL-tree instead of Merkle Patricia Trie (MPT) for data storage,
 Sei doesn't have per-account state root. The global state root is the AVL-tree
 root which is also not equivalent to Ethereum's overall state root (which is a
 MPT root)

 ## Block Hash

 The block hash on Sei is computed based on the block header in Tendermint data
 format, and is different from Ethereum's block Hash as a result.

 ## Base Fee & Tips

 Sei supports all non‑blob transaction types, including the Pectra `SetCode` transaction (EIP‑7702). However for a legacy (non EIP‑1559) type
 transaction, you must specify a gas price at or above Sei's governance-set minimum gas price (currently `50 gwei` on mainnet). Query the live value with `eth_gasPrice` rather than hard-coding it. In addition to this, excess
@@ -131,7 +131,7 @@
 value: '"0.007500000000000000"'
 ```

 ## Non-EVM Transactions

 On Sei there exists non-EVM transactions which may update states accessible by
 EVM transactions. The simplest example would be bank balances, which may be
@@ -145,7 +145,7 @@
 committed (~400 ms) — meaning that commitment levels of "safe", "latest",
 "justified", and "finalized" on Ethereum are all the same thing on Sei.

 ## Pending State

 On Ethereum the block proposer would execute its proposed block first (and
 update its local state) before broadcasting the proposal to others (the updated
@@ -156,7 +156,7 @@
 the same time), so Sei does not have a window when "pending state"
 exists.

 ## Gas Model & Fees

 Sei does not implement base‑fee burning. There is no base‑fee burn; all transaction fees accrue to validators. Fees are calculated as:

@@ -178,7 +178,7 @@

 </Info>

 ## SSTORE Gas Cost

 On Sei, the `SSTORE` opcode gas cost is configurable as an on-chain parameter, meaning it can be adjusted via governance proposal without requiring a chain upgrade. This provides flexibility to tune storage costs based on EVM state size and network conditions.

@@ -192,7 +192,7 @@

 <Info>Since `SSTORE` is a governance-controlled parameter, this value may change in the future through a governance proposal.</Info>

 ## ERC Token Standards Compatibility

 Sei’s EVM fully supports the common token standards:

@@ -202,7 +202,7 @@

 Existing OpenZeppelin contracts and tools work unchanged.

 ## Testing & Migration Checklist

 - ✅ Re‑deploy your Solidity code to Sei testnet; most contracts need no changes.
 - ✅ If you used SELFDESTRUCT, refactor to a soft‑close pattern.

diff --git a/evm/precompiles/cosmwasm-precompiles/bank.mdx b/evm/precompiles/cosmwasm-precompiles/bank.mdx
@@ -10,23 +10,23 @@

 <Info> **What is a precompile?** A precompile is a special smart contract deployed at a fixed address by the Sei protocol itself, that exposes custom native chain logic to EVM-based applications. It acts like a regular contract from the EVM's perspective, but executes privileged, low-level logic efficiently. </Info>

 ## How Does the Bank Precompile Work?

 The bank precompile at address `0x0000000000000000000000000000000000001001` exposes functions like `send()`, `sendNative()`, `balance()`, `all_balances()`, and token metadata queries.
 
 - **Direct Integration:** EVM contracts and dApps can call banking functions like any other smart contract method.
 - **Native Execution:** Operations are executed at the Cosmos SDK level for maximum efficiency and security.
-- **Cross-Chain Assets:** Manage both native SEI tokens and IBC assets seamlessly from EVM contracts.
+- **Any native denom:** Manage native SEI, factory tokens, and existing IBC denoms from EVM contracts. IBC is disabled on Sei (see [SIP-03](/learn/sip-03-migration#ibc-is-disabled)), so no new IBC denoms can arrive, but balances already held remain readable and transferable.
 
 **When to use `send` vs `sendNative`:** `send` moves an arbitrary `denom` (any IBC or factory token) between two EVM addresses (`0x...`) by reading the balance directly from the bank module — no `msg.value` is attached. It is gated to the registered ERC20 native pointer for that denom, so it is typically invoked from the auto-deployed pointer contract rather than from arbitrary user code. `sendNative` is for sending native SEI (the attached `msg.value`) from the EVM caller to a Cosmos bech32 (`sei1...`) destination, which is useful for crossing the EVM→Cosmos boundary when the recipient has no associated EVM address (for example, paying a Cosmos-only contract or account).
 
 ## Use Cases

 - **DeFi Applications:** Build decentralized finance protocols that can handle native SEI and Cosmos assets.
 - **Portfolio Management:** Build tools to track and manage multi-asset portfolios across Cosmos and EVM.
 - **Token Information Services:** Query comprehensive token metadata for UI display and analytics.

 ## What You'll Learn in This Guide

 By the end of this guide, you'll be able to:

@@ -38,7 +38,7 @@

 The bank precompile exposes the following functions:

 ### Transaction Functions

 ```solidity
 /// Sends non-native tokens from one address to another. Callable only by the
@@ -64,7 +64,7 @@
 ) payable external returns (bool success);
 ```

 ### Query Functions

 ```solidity
 /// Queries the balance of the given account for the specified denom.
@@ -112,7 +112,7 @@
 ) external view returns (uint256 response);
 ```

 ## Using the Precompile

 ### Setup

@@ -126,7 +126,7 @@
 - **SEI tokens** for gas and testing transfers
 - **Hardhat** for development and testing

 #### Install Dependencies

 Install the required packages for interacting with Sei precompiles:

@@ -141,7 +141,7 @@
 npm install @sei-js/precompiles@2.1.2
 ```

 #### Setup Hardhat Environment

 Create a `hardhat.config.ts` file with the following content:

@@ -169,7 +169,7 @@
 npx hardhat keystore set PRIVATE_KEY
 ```

 #### Import Precompile Components

 <Tabs>
 <Tab title="JavaScript">
@@ -263,7 +263,7 @@
 </Tab>
 </Tabs>

 ### Native SEI vs Custom Tokens

 **Native SEI Transfers:**

@@ -277,9 +277,9 @@
 - Requires prior token approval or ownership
 - Support various decimal configurations

 ## Step-by-Step Guide: Using the Bank Precompile

 ### Send Native SEI Tokens

 <Tabs>
 <Tab title="JavaScript">
@@ -330,7 +330,7 @@
 </Tab>
 </Tabs>

 ### Send Custom Tokens

 <Tabs>
 <Tab title="JavaScript">
@@ -407,7 +407,7 @@
 </Tab>
 </Tabs>

 ### Query Account Balance

 <Tabs>
 <Tab title="JavaScript">
@@ -464,7 +464,7 @@
 </Tab>
 </Tabs>

 ### Query All Balances

 <Tabs>
 <Tab title="JavaScript">
@@ -539,7 +539,7 @@
 </Tab>
 </Tabs>

 ### Query Token Metadata

 <Tabs>
 <Tab title="JavaScript">
@@ -622,7 +622,7 @@
 </Tab>
 </Tabs>

 ### Complete Integration Example

 <Tabs>
 <Tab title="JavaScript">
@@ -1103,15 +1103,15 @@
 </Tab>
 </Tabs>

 ## Security Considerations & Risks

 ### Transaction Security

 - **Amount Validation:** Always validate transfer amounts and ensure sufficient balances
 - **Address Verification:** Verify recipient addresses are valid before sending tokens
 - **Reentrancy Protection:** Be aware of potential reentrancy when combining with other contracts

 ### Permission Management

 ```solidity
 // Example of secure permission patterns
@@ -1129,9 +1129,9 @@

 ## Troubleshooting

 ### Common Issues and Solutions

 #### Transaction Failures

 ```typescript
 // Handle common transfer errors
@@ -1149,7 +1149,7 @@
 }
 ```

 #### Balance Query Issues

 ```typescript
 // Safe balance checking with error handling
@@ -1166,7 +1166,7 @@
 }
 ```

 ### Error Code Reference

 | Error | Cause | Solution |
 | --- | --- | --- |
@@ -1177,7 +1177,7 @@
 | `metadata not found` | Token metadata not available | Handle missing metadata gracefully |


 ## Important Notes

 <Info>

@@ -1189,13 +1189,13 @@

 </Info>

 ### Gas Optimization

 - **Batch Operations:** Use batch functions for multiple operations to save gas
 - **Query Efficiency:** Cache frequently accessed token metadata
 - **Error Handling:** Implement proper error handling to avoid failed transaction costs

 ### Integration Best Practices

 - **Balance Checks:** Always verify sufficient balance before transfers
 - **Error Recovery:** Implement retry logic for failed transactions

diff --git a/evm/precompiles/cosmwasm-precompiles/cosmwasm.mdx b/evm/precompiles/cosmwasm-precompiles/cosmwasm.mdx
@@ -11,7 +11,7 @@
 
   Per [governance Proposal 115](https://seistream.app/proposals/115), CosmWasm code uploads (`MsgStoreCode`) and contract instantiations (`MsgInstantiateContract`) are disabled chain-wide. The `instantiate()` function on this precompile **will revert** for all callers. Only `execute()`, `execute_batch()`, and `query()` against pre-existing CosmWasm contracts remain functional, and all CosmWasm functionality is deprecated in favor of EVM-only per [SIP-3](https://github.com/sei-protocol/sips/blob/main/sips/sip-3.md).
 
-  In addition, [Proposal 116](https://seistream.app/proposals/116) disables inbound IBC transfers — IBC assets bridged from Cosmos chains can no longer arrive on Sei after this passes and is activated. See the [SIP-03 Migration Guide](/learn/sip-03-migration) for affected assets and migration routes.
+  In addition, IBC is disabled in both directions: Proposals [116](https://seistream.app/proposals/116) and [120](https://seistream.app/proposals/120) disabled inbound IBC, and [Proposal 121](https://seistream.app/proposals/121) disabled outbound IBC on July 31, 2026. No asset can be bridged into or out of Sei over IBC. See the [SIP-03 Migration Guide](/learn/sip-03-migration) for the full explanation and the list of affected assets.
 
   For new smart contract development, use the EVM directly. See [Deploy a Smart Contract](/evm/evm-general).
 </Danger>
@@ -20,7 +20,7 @@

 <Info> **What is a precompile?** A precompile is a special smart contract deployed at a fixed address by the Sei protocol itself, that exposes custom native chain logic to EVM-based applications. It acts like a regular contract from the EVM's perspective, but executes privileged, low-level logic efficiently. </Info>

 ## How Does the CosmWasm Precompile Work?

 The CosmWasm precompile at address `0x0000000000000000000000000000000000001002` exposes functions like `execute()`, `execute_batch()`, and `query()`.

@@ -28,7 +28,7 @@
 - **Native Execution:** Operations are executed at the Cosmos SDK level for maximum efficiency and security.
 - **Seamless Bridge:** No need for separate wallet integrations or complex cross-chain interactions.

 ## What You'll Learn in This Guide

 By the end of this guide, you'll be able to:

@@ -41,7 +41,7 @@

 The CosmWasm precompile exposes the following functions:

 ### Transaction Functions

 <Warning>The `instantiate()` function has been disabled by [Prop 115](https://seistream.app/proposals/115) and will revert. It is omitted from this reference. The ABI in `@sei-js/precompiles` may still expose it for backwards compatibility, but calling it on-chain will fail.</Warning>

@@ -71,7 +71,7 @@
 ) payable external returns (bytes[] memory responses);
 ```

 ### Query Functions

 ```solidity
 /// Queries a CosmWasm contract.
@@ -84,7 +84,7 @@
 ) external view returns (bytes memory response);
 ```

 ## Using the Precompile

 ### Setup

@@ -97,7 +97,7 @@
 - **EVM-compatible wallet**
 - **SEI tokens** for gas and contract operations

 #### Install Dependencies

 Install the required packages for interacting with Sei precompiles:

@@ -109,7 +109,7 @@
 npm install @sei-js/precompiles@2.1.2
 ```

 #### Import Precompile Components

 ```typescript
 // Import CosmWasm precompile address and ABI
@@ -134,11 +134,11 @@
 const cosmwasm = new ethers.Contract(WASM_PRECOMPILE_ADDRESS, WASM_PRECOMPILE_ABI, signer);
 ```

 ## Critical: Understanding Message Formats

 One of the most important concepts to understand when working with the Sei CosmWasm precompile:

 ### CosmWasm Message Structure

 The CosmWasm precompile requires **JSON-encoded messages** that conform to each contract's specific schema:

@@ -148,7 +148,7 @@
 | `query()` | req parameter (input) | JSON bytes | `ethers.toUtf8Bytes(jsonString)` |
 | **All functions** | response (output) | JSON bytes | `JSON.parse(ethers.toUtf8String(response))` |

 ### How Message Encoding Works

 **All CosmWasm functions require JSON-encoded byte arrays:**

@@ -160,7 +160,7 @@
 - Use `msg.value` for SEI amounts
 - Use `coins` parameter for other denominations (encoded as JSON bytes)

 ### Best Practice: Message Encoding Helpers

 When working with CosmWasm messages, use proper JSON encoding:

@@ -203,7 +203,7 @@
 });
 ```

 ## Message Format Helpers

 Use these helper functions to handle CosmWasm message formatting:

@@ -251,9 +251,9 @@
 const coins = CosmWasmHelper.createCoins([{ denom: 'uusdc', amount: '1000000' }]);
 ```

 ## Step-by-Step Guide: Using the CosmWasm Precompile

 ### Execute a CosmWasm Contract

 <Tabs>
 <Tab title="JavaScript">
@@ -311,7 +311,7 @@
 </Tab>
 </Tabs>

 ### Execute Batch Operations

 <Tabs>
 <Tab title="JavaScript">
@@ -382,7 +382,7 @@
 </Tab>
 </Tabs>

 ### Query a CosmWasm Contract

 <Tabs>
 <Tab title="JavaScript">
@@ -451,9 +451,9 @@

 <Warning> **Query Limitations:** CosmWasm queries are read-only operations and don't consume gas, but parsing JSON responses in Solidity is complex. Consider handling response parsing off-chain. </Warning>

 ## Advanced Usage Examples

 ### Cross-Runtime DeFi Integration

 ```typescript
 async function crossRuntimeDeFiOperation(cosmwasmDexContract: string, evmTokenContract: string, amount: string) {
@@ -492,7 +492,7 @@
 }
 ```

 ### Complete Integration Example

 <Tabs>
 <Tab title="JavaScript">
@@ -730,9 +730,9 @@

 ## Troubleshooting

 ### Common Issues and Solutions

 #### Message Encoding Issues

 ```typescript
 // Ensure proper JSON encoding for messages
@@ -750,7 +750,7 @@
 const incorrectMsg = ethers.toUtf8Bytes('invalid json');
 ```

 ### Error Code Reference

 | Error | Cause | Solution |
 | --- | --- | --- |
@@ -761,23 +761,23 @@
 | `unauthorized` | Insufficient permissions | Check admin/owner permissions |
 | `query parsing failed` | Invalid query message format | Match contract's query schema |

 ## Important Notes

 <Info> Remember the key rule: All CosmWasm messages must be properly JSON-encoded as bytes, and contract schemas vary by implementation! </Info>

 ### Message Format Requirements

 - **JSON Encoding:** All messages must be valid JSON encoded as UTF-8 bytes, invalid JSON will cause transaction failures
 - **Schema Compliance:** Messages must match the contract's expected format
 - **Type Safety:** Use proper data types as expected by the contract

 ### Contract Address Format

 - Use valid Sei contract addresses with `sei1...` prefix
 - These are Cosmos-format addresses, not EVM addresses
 - **Contract Existence:** Verify contracts exist before calling

 ### Cross-Runtime Considerations

 - **State Isolation:** CosmWasm and EVM contracts have separate state
 - **Gas Estimation:** CosmWasm operations may require different gas calculations
@@ -785,7 +785,7 @@
 - **Native Token Handling:** Use `msg.value` for SEI, `coins` for other denominations
 - **Batch Limitations:** Large batches may hit gas limits

 ### Best Practices

 - Always validate JSON messages before sending
 - Handle response parsing carefully, especially for complex data structures

diff --git a/evm/precompiles/cosmwasm-precompiles/example-usage.mdx b/evm/precompiles/cosmwasm-precompiles/example-usage.mdx
@@ -6,7 +6,7 @@
 
 
 <Info>
-Per [Proposal 115](https://seistream.app/proposals/115), no new CosmWasm contracts can be deployed on Sei. The examples below apply to **pre-existing CosmWasm contracts** only — `instantiate()` will revert. Separately, [Proposal 116](https://seistream.app/proposals/116) disables inbound IBC transfers as part of the [SIP-03](/learn/sip-03-migration) migration.
+Per [Proposal 115](https://seistream.app/proposals/115), no new CosmWasm contracts can be deployed on Sei. The examples below apply to **pre-existing CosmWasm contracts** only — `instantiate()` will revert. Separately, IBC is disabled in both directions as part of the [SIP-03](/learn/sip-03-migration) migration — Proposals [116](https://seistream.app/proposals/116) and [120](https://seistream.app/proposals/120) disabled inbound IBC, and [Proposal 121](https://seistream.app/proposals/121) disabled outbound IBC.
 </Info>
 
 The Sei precompiles can be used like any standard smart contract on the EVM. For
@@ -47,7 +47,7 @@
 const contract = new ethers.Contract(WASM_PRECOMPILE_ADDRESS, WASM_PRECOMPILE_ABI, signer);
 ```

 #### Querying & Executing a CosmWasm Contract

 Once you have the contract, you can query and execute messages to any CosmWasm
 smart contract. In the below example we assume there is a counter contract with a `get_count` function

diff --git a/index.mdx b/index.mdx
@@ -9,16 +9,16 @@
 The first parallelized EVM blockchain delivering unmatched scalability and speed.
 
 <Danger>
-  **Action required: IBC assets on Sei will become inaccessible**
+  **IBC is disabled on Sei in both directions**
 
-  If you hold [USDC.n](https://seiscan.io/address/0x3894085Ef7Ff0f0aeDf52E2A2704928d1Ec074F1) (USDC via Noble), [USDT.kava](https://seiscan.io/address/0xb75d0b03c06a926e488e2659df1a861f860bd3d1) (Kava USDT), Wormhole-bridged tokens, or any other IBC asset on Sei, you **must** swap, migrate, or bridge out **before the governance proposal to disable inbound/outbound IBC transfers passes and is activated** to avoid permanent loss of access. After this, Sei will no longer support IBC bridging of assets from Cosmos-based chains to and from Sei Network.
+  [Proposal #121](https://seistream.app/proposals/121) passed on July 31, 2026 and disabled outbound IBC transfers. Inbound IBC was already disabled by [Proposal #116](https://seistream.app/proposals/116) and [Proposal #120](https://seistream.app/proposals/120). No asset can be bridged into or out of Sei over IBC.
 
-  Consult the [SIP-03 Migration Guide](/learn/sip-03-migration) for the full list of affected assets, required actions, and supported routes.
+  If you hold [USDC.n](https://seiscan.io/address/0x3894085Ef7Ff0f0aeDf52E2A2704928d1Ec074F1) (USDC via Noble), [USDT.kava](https://seiscan.io/address/0xb75d0b03c06a926e488e2659df1a861f860bd3d1) (Kava USDT), ATOM, WBTC, or any other IBC asset on Sei, it can no longer be redeemed on its origin chain. The balance still exists on Sei and can still be transferred within Sei.
 
-  For USDC.n specifically, see: [Holders of USDC.n Need to Swap or Migrate](https://blog.sei.io/announcements/holders-of-usdcn-need-to-swap-or-migrate/).
+  See the [SIP-03 Migration Guide](/learn/sip-03-migration) for what changed, the full list of affected assets, and what remains possible.
 </Danger>
 
 ## Quick Start

 <CardGroup cols={3}>
  <Card title="Deploy a Smart Contract" icon="code" horizontal href="/evm/evm-general">
@@ -38,7 +38,7 @@
  </Card>
 </CardGroup>

 ## Essential Resources

 <CardGroup cols={3}>
  <Card title="Chain Info" icon="globe" horizontal href="/learn/dev-chains">
@@ -127,7 +127,7 @@
  </Card>
 </CardGroup>

 ## Smart Contracts

 <Card title="Deploy & Debug on Sei" icon="code" horizontal href="/evm/evm-general">
  Write, deploy, and debug Solidity smart contracts with your favorite toolchain. Sei is fully EVM-compatible with 400 ms blocks and parallelized execution.
@@ -140,7 +140,7 @@
  <Card title="Best Practices" icon="gauge-high" horizontal href="/evm/best-practices/optimizing-for-parallelization" />
 </CardGroup>

 ## Infrastructure & Tools

 <CardGroup cols={2}>
  <Card title="Run a Node" icon="lock" horizontal href="/node">

diff --git a/learn/dev-interoperability.mdx b/learn/dev-interoperability.mdx
@@ -6,10 +6,10 @@
 ---
 
 <Info>
-  **CosmWasm deployments are frozen, and inbound IBC is being disabled.** Per [Proposal 115](https://seistream.app/proposals/115), no new CosmWasm contracts can be uploaded or instantiated on Sei. [Proposal 116](https://seistream.app/proposals/116) additionally disables inbound IBC transfers, so IBC assets bridged from Cosmos chains can no longer arrive on Sei. The interoperability features described on this page apply to **already-deployed** CosmWasm contracts, native Bank Module assets, and Cosmos-SDK modules accessed via precompiles. For new smart contract development, build directly on the EVM. See [SIP-3](https://github.com/sei-protocol/sips/blob/main/sips/sip-3.md) for the full migration context.
+  **CosmWasm deployments are frozen, and IBC is disabled in both directions.** Per [Proposal 115](https://seistream.app/proposals/115), no new CosmWasm contracts can be uploaded or instantiated on Sei. Proposals [116](https://seistream.app/proposals/116), [120](https://seistream.app/proposals/120), and [121](https://seistream.app/proposals/121) disabled inbound and then outbound IBC transfers, so no asset can be bridged into or out of Sei over IBC. The interoperability features described on this page apply to **already-deployed** CosmWasm contracts, native Bank Module assets, and Cosmos-SDK modules accessed via precompiles. For new smart contract development, build directly on the EVM. See [SIP-3](https://github.com/sei-protocol/sips/blob/main/sips/sip-3.md) and the [SIP-03 Migration Guide](/learn/sip-03-migration) for the full migration context.
 </Info>
 
 ## Dual Address Support

 Sei utilizes two distinct address types:

@@ -23,7 +23,7 @@
 For more details on interoperability, explore our article
 [here](https://blog.sei.io/sei-v2-interoperability/).

 ## Virtual Machine Interoperability

 EVM and existing CosmWasm-based smart contracts co-exist on Sei, but live in
 different execution environments. This creates a challenge for users, who use
@@ -35,7 +35,7 @@
 already-deployed CosmWasm contracts to the EVM via precompiled contracts. New
 smart contracts on Sei should be deployed on the EVM directly.

 ## Precompile Contracts

 Sei precompiles are smart contracts embedded directly within the Sei EVM
 environment. They provide a gateway for users and developers to access Cosmos-SDK functions through the EVM RPC interface.
@@ -43,7 +43,7 @@
 For instructions on utilizing EVM precompiles, refer to the
 [Example Usage](/evm/precompiles/example-usage) section.

 ## Example Diagram

 ![Interoperability](/assets/interoperability.png)
 *Enabling seamless access to all tokens and contracts on Sei*
diff --git a/learn/sip-03-exchange-migration.mdx b/learn/sip-03-exchange-migration.mdx
@@ -6,7 +6,13 @@
 
 This section is for exchanges, custodians, and other service providers that currently support SEI token deposits and withdrawals using native (`sei1...`) addresses. It explains what SIP-03 changes, the options available for migrating customer holdings to EVM (`0x...`) addresses, and the timeline by which migration must be complete.
 
+<Warning>
+**IBC is already disabled in both directions.** Proposals [#116](https://seistream.app/proposals/116) and [#120](https://seistream.app/proposals/120) disabled inbound IBC, and [#121](https://seistream.app/proposals/121) disabled outbound IBC on July 31, 2026. No asset can be bridged into or out of Sei over IBC, so IBC is not available as a route for moving customer funds off Sei, and IBC-bridged assets held on Sei can no longer be redeemed on their origin chain. See [IBC is disabled](/learn/sip-03-migration#ibc-is-disabled).
+
+The migration options below move funds between the native and EVM sides of Sei. They are intra-chain and are not affected by the IBC parameters.
+</Warning>
+
 ### What SIP-03 changes
 
 For exchanges, the practical implication of the SIP-03 migration is that any integration treating "Sei" (native) and "Sei EVM" as two separate chains needs to be reconciled into a single integration before the Cosmos shutdown. Every native address (`sei1...`) on Sei has a corresponding EVM address (`0x...`) on the same chain. This is not two distinct chains or wallets, it is one chain with two ways to interact with it.

@@ -24,19 +30,19 @@
 - Ensure the native and EVM addresses are associated on-chain (see [Address association](#address-association) below).
 - Update internal accounting and customer-facing UI to present the EVM address as the canonical Sei address.

 #### 2) Automated forwarding contract

 The exchange uses a `FundsForwarder` smart contract to programmatically move customer funds from the native side to the customer's EVM wallet on the exchange. The exchange handles deployment and triggering; the customer sees the funds arrive at the new address without taking any action themselves.

 This is appropriate when the exchange cannot or does not want to expose EVM addresses for existing native wallets directly, but is willing to operate the migration itself.

 #### 3) User-directed forwarding contract

 The exchange notifies customers of the change and directs them to the `FundsForwarder` contract address. Customers initiate the transfer themselves; this action triggers the contract to automatically forward funds to the appropriate EVM wallet on the exchange.

 This is functionally similar to option 2 but pushes the trigger action onto the customer. It is appropriate when the exchange cannot operate the contract directly but wants to provide an automated destination.

 #### 4) Fully manual transfer

 The exchange notifies customers of the change and asks them to manually withdraw funds to a self-custodial wallet and then redeposit them to the EVM address provided by the exchange.

@@ -50,7 +56,7 @@

 For details on how to query association status and the methods for associating addresses, see [Accounts](/learn/accounts).

 ### FundsForwarder contract

 The `FundsForwarder` is a one-way smart contract that accepts deposits at a native (`sei1...`) address and forwards the full balance to a pre-configured EVM (`0x...`) destination address. It is the underlying mechanism for options 2 and 3 above.

@@ -62,7 +68,7 @@
 
 ### Migration milestone
 
-Address association must be completed prior to deprecation of all Cosmos, CosmWasm and IBC related functionality, slated for **June 15, 2026**. After deprecation:
+IBC has already been disabled, in both directions, by Proposals [#116](https://seistream.app/proposals/116), [#120](https://seistream.app/proposals/120), and [#121](https://seistream.app/proposals/121). Address association must still be completed prior to deprecation of the remaining Cosmos and CosmWasm functionality, slated for **June 15, 2026**. After deprecation:
 
 - Exchanges and their users will not be able to access or transfer funds.
 - Cosmos-native transaction interfaces will no longer be available. Exchanges will not be able to broadcast Cosmos-format transactions, sign with Cosmos key derivations against the live chain, or interact with the chain through Cosmos RPC endpoints.