Remove IBC-disabled wording and adjust precompile docs

Remove outdated statements that IBC is disabled and simplify CosmWasm and bank precompile documentation. Update the deprecation notice to reference Proposal 115 only and remove mentions of Proposals 116/120/121 and IBC being disabled. Remove the TokenFactory native token creation row from the EVM compatibility table, simplify bank precompile denom wording, and clarify send vs sendNative usage. Minor copy edit to the SIP-3 card text for clarity.

Author: alexander-sei

evm/differences-with-ethereum.mdx

@@ -39,8 +39,6 @@ Cosmos SDK and CosmWasm functionality is being deprecated in favor of EVM-only.
 
 [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.
 
-**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>
 
 - **Sei is a dual-execution environment (EVM and Cosmos-SDK).** This means:

evm/evm-parity/evm-compatibility.mdx

@@ -103,7 +103,6 @@ These capabilities are Sei-specific and have no standard Ethereum equivalent. Th
 | Sei precompiles (staking, governance, distribution, oracle, P256, JSON, CosmWasm bridge) | EVM contracts at deterministic addresses. ABIs and contract addresses are exported from `@sei-js/precompiles` for use with any standard EVM library. |
 | Pointer contracts (CW20 ↔ ERC-20, CW721 ↔ ERC-721) | Bridge between CosmWasm and EVM token standards. Standard ERC interfaces work against pointer contracts. |
 | Native address association (EVM ↔ Cosmos address) | Links an EVM address and a Cosmos address for the same account. Required before some Sei-native flows. |
-| TokenFactory native token creation | Create native Sei tokens that are usable across EVM and CosmWasm without a wrapper contract. |
 
 ## Unsupported RPC Methods
 

evm/precompiles/cosmwasm-precompiles/bank.mdx

@@ -16,9 +16,9 @@ The bank precompile at address `0x0000000000000000000000000000000000001001` expo
 
 - **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.
-- **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.
+- **Any native denom:** Manage native SEI and other bank module denominations from EVM contracts.
 
-**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).
+**When to use `send` vs `sendNative`:** `send` moves an arbitrary `denom` 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
 

evm/precompiles/cosmwasm-precompiles/cosmwasm.mdx

@@ -7,12 +7,10 @@ keywords: ['cosmwasm precompile', 'ethers.js', 'wasm execution', 'cross-chain co
 **Address:** `0x0000000000000000000000000000000000001002`
 
 <Danger>
-  **Deprecation Notice — Prop 115 & Prop 116**
+  **Deprecation Notice — Prop 115**
 
   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, 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>
 

evm/precompiles/cosmwasm-precompiles/example-usage.mdx

@@ -6,7 +6,7 @@ keywords: ["precompile example", "ethers.js", "cosmwasm query", "evm integration
 
 
 <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, 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.
+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.
 </Info>
 
 The Sei precompiles can be used like any standard smart contract on the EVM. For

learn/sips.mdx

@@ -73,7 +73,7 @@ SIP-3 and SIP-4 both affect how you use and build on Sei. These pages cover what
 
 <CardGroup cols={2}>
   <Card title="SIP-3 migration guide" icon="arrow-right-arrow-left" href="/learn/sip-03-migration">
-    Move assets off Cosmos-native addresses and IBC tokens before Sei becomes EVM-only.
+    What SIP-3 changes for asset holders, and how to move off Cosmos-native addresses.
   </Card>
   <Card title="SIP-3 for exchanges" icon="building-columns" href="/learn/sip-03-exchange-migration">
     Integration changes for exchanges and custodians supporting Sei deposits and withdrawals.