Action required: IBC assets on Sei will become inaccessibleIf you hold USDC.n (USDC via Noble), USDT.kava (Kava USDT), Wormhole-bridged tokens, or any other IBC asset on Sei, you must swap, migrate, or bridge out before Proposal #116 (disables inbound 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 IBC Asset Migration Table below 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.
For the full proposal text, see:
- The official SIP-03
- Governance Proposal #99 — initiated the migration
- Governance Proposal #115 — disables CosmWasm code uploads and contract instantiations. After this passes, no new CosmWasm contracts can be deployed on Sei.
- Governance Proposal #116 — disables inbound IBC transfers. After this passes and is activated, IBC assets bridged from Cosmos chains can no longer arrive on Sei.
What most users need to do
- If you use Keplr or Leap (Cosmos-style wallets) and hold assets on the native address (sei1…), you should move assets to an EVM-compatible address (0x…). Use the Asset Transfer tool linked below.
- If you use Compass or another EVM wallet already, you’re good — continue as normal.
IBC Asset Migration Table
If you hold any of the following IBC assets on Sei, take action before Proposal #116 (disables inbound IBC transfers) passes and is activated. [We’ll update this table as more resources are made available]| Asset | Token contract | Action(s) | Possible route(s) | Support |
|---|---|---|---|---|
| USDC.n (USDC via Noble) | seiscan mintscan | Swap to native USDC or migrate via CCTP | Sapyhre, Symphony, or Stargate | Sei blog Sei Tech Chat Discord |
| USDT.kava (USDT via Kava) | seiscan mintscan | Swap via Symphony or bridge out to Kava | Symphony, Stargate | Sei Tech Chat Discord |
| USDCso (Wormhole, Solana) | mintscan | Bridge out to Solana via Wormhole | Portal Bridge (legacy) | Sei Tech Chat Discord |
| Wormhole-bridged WETH | mintscan | Bridge out to Ethereum via Wormhole | Portal Bridge (legacy) | Sei Tech Chat Discord |
| USDCet (Wormhole, Ethereum) | mintscan | Bridge out to Ethereum via Wormhole | Portal Bridge (legacy) | Sei Tech Chat Discord |
| USDCop (Wormhole, Optimism) | mintscan | Bridge out to Optimism via Wormhole | Portal Bridge (legacy) | Sei Tech Chat Discord |
| USDTbs (Wormhole, BSC Chain) | mintscan | Bridge out to BSC Chain via Wormhole | Portal Bridge (legacy) | Sei Tech Chat Discord |
| ATOM | mintscan | Bridge out to Cosmos Hub | Skip:Go | Sei Tech Chat Discord |
| WBTC | mintscan | Bridge out to origin chain | Skip:Go | Sei Tech Chat Discord |
Key tools and resources
1) Asset Transfer (Native ↔ EVM)
- Use the official Sei Dashboard to move assets between native (Keplr/Leap/Fin) and EVM (MetaMask/Compass etc.) addresses: Sei Dashboard Transfer or the Bridge tab at Sei Dashboard Bridge.
- You used Keplr or Leap before and want assets available via an EVM wallet going forward.
- You need to access tokens on apps that now expect an EVM (0x) address.
2) USDC on Sei
Native USDC and Circle’s CCTP V2 are now supported on Sei. USDC from Noble (USDC.n) is deprecated.- QuickStart: USDC on Sei
- Background: USDC & CCTP v2 announcement
How to swap or migrate USDC.n
Swap (smaller amounts):- DragonSwap or Symphony — slippage may vary depending on market conditions and liquidity.
- Manual migration: Bridge USDC.n via Stargate to an intermediary chain with CCTP v1 and v2 (e.g., Base), then use CCTP to burn/mint native USDC back to Sei.
- Other useful bridging frontends: CCTP Exchange
- Wind down and withdraw your positions before migrating to native USDC. Failure to do so before the SIP-03 upgrade may result in inability to access your supplied assets.
Migrating a hardware or mnemonic-only wallet
If your wallet can export a raw private key, the simplest path is to import that key into an EVM wallet. A private key is independent of coin type, so it reproduces the same0x... and sei1... addresses in any wallet, and no funds need to move.
If your wallet cannot export a private key, you can still migrate by moving your funds to a new EVM-native account, as described below.
When private-key export isn’t an option
A raw private key always works, but two common setups do not provide one:- Mnemonic-only wallets. Some wallets back up only a recovery phrase, not a raw private key. Sei’s Cosmos (
sei1...) accounts use coin type 118 (m/44'/118'/0'/0/0). Importing the same phrase into an EVM wallet such as MetaMask derives it on coin type 60 (m/44'/60'/0'/0/0), producing a different account with no access to the original funds. The underlying private key would import correctly if the wallet exposed it, but a mnemonic-only wallet does not. - Hardware wallets (such as Ledger). A Ledger does not export the private key or seed under any circumstances. It only allows switching between the Cosmos app (coin type 118) and the Ethereum app (coin type 60), which control separate accounts with different addresses. The Cosmos-app account cannot be used from an EVM wallet.
Migration steps
This works because every account has exactly one EVM (0x...) address and one Cosmos (sei1...) address, both derived from the same key. Funds sent to the new account’s sei1... address are therefore spendable from the EVM wallet that holds its 0x... address.
Create a new account in an EVM wallet you control
Use MetaMask, Compass, Rabby, or a Ledger running its Ethereum app. This produces a new
0x... address.Fund the new address with a small amount of SEI
Roughly 0.1 SEI is sufficient. Association is an on-chain transaction, so the account requires SEI for gas. Fund it from an exchange withdrawal or from any EVM wallet that already holds SEI.
Associate the new account on the Sei Dashboard
Connect the new EVM account to the Sei Dashboard and complete address association. This records the public key on-chain and links the
0x... address to its sei1... counterpart. The dashboard then displays the linked sei1... address, which is the destination for the next step. See Account Linking for details on association.Send a test transfer of 1 SEI
From the original Cosmos wallet (Keplr, Leap, the Ledger Cosmos app, and so on), send 1 SEI to the
sei1... address from step 3. This is a standard Cosmos-to-Cosmos transfer.Confirm receipt
Because the addresses are associated, the test amount should appear under the new account on the dashboard and as a spendable balance in the EVM wallet.
Notes and limitations
- Complete this before the SIP-03 upgrade. After the Cosmos interface is deprecated, addresses can no longer be associated and
sei1...transfers can no longer be broadcast. Steps 3 and 4 must be completed beforehand. - This procedure moves liquid balances only. Staked SEI must be unbonded first, and the unbonding period is 21 days. See the staking question in the FAQ.
- Associate before sending. Associating the new account before transferring ensures the funds arrive at the correct, immediately spendable address rather than a temporary holding address.
- Optional verification. To confirm the paired
sei1...address independently, callgetSeiAddr(0x...)on theaddrprecompile. See Query Linked Addresses.
FAQ
I am a Keplr / Leap wallet user; do I need to do anything?
Yes. Use the Asset Transfer tool to ensure your assets are available via an EVM wallet. See Asset Transfer above.I use Compass wallet; do I need to do anything?
No action needed. Compass ensures your assets are available via EVM. Continue connecting to Sei like any EVM chain.My wallet only shows a recovery phrase, or I use a Ledger — how do I migrate?
If you can export a raw private key, import it into an EVM wallet. This always works, because the key reproduces the same addresses in any wallet. If you cannot (a wallet that exports only a recovery phrase, or a Ledger that only switches between apps), create a new account in an EVM wallet you control, fund it with a small amount of SEI, associate it to reveal its pairedsei1... address, and send your existing Cosmos funds to that address. Send a 1 SEI test transfer first. See Migrating a hardware or mnemonic-only wallet for the full procedure.
I stake SEI — do I need to do anything?
It depends on whether your Cosmos (sei1...) and EVM (0x...) addresses are associated (linked). Staking on Sei is handled by the Cosmos staking module. After SIP-03, Cosmos-native transaction interfaces will no longer be available — but the underlying staking state is preserved and accessible via EVM for associated addresses.
If your addresses are associated: No action is needed. After the upgrade, your existing delegations, rewards, and unbonding state will be fully accessible via EVM. You can continue managing your stake through an EVM wallet using the Staking Precompile, the Sei Dashboard, or the Sei Dashboard.
If your addresses are NOT associated: You must act before the upgrade. After SIP-03, you will not be able to associate addresses or manage delegations through a Cosmos wallet.
Your options:
- Associate your addresses before the upgrade. You can do this by connecting your Cosmos wallet on the Sei Dashboard or by using any of the methods described in Accounts. Once associated, your staking state becomes accessible via EVM — no need to unbond.
- Unbond your stake and migrate assets to an EVM wallet using the Asset Transfer tool. The unbonding period is 21 days, so you must begin this process at least 21 days before the Cosmos shutdown to ensure your tokens are liquid in time.