Skip to main content
IBC is now disabled on Sei in both directions. IBC assets can no longer be bridged off Sei.Proposal #121 passed on July 31, 2026 and set the ibc module’s OutboundEnabled parameter to false. Inbound IBC was already disabled by Proposal #116 and Proposal #120. Both directions are now closed.If you hold any IBC asset on Sei, there is no longer a route to redeem or bridge it back to its origin chain. This includes USDC.n (USDC via Noble), USDT.kava (Kava USDT), ATOM, and WBTC. The bridge-out and IBC-based migration routes that were available before no longer work.These balances still exist on Sei and can still be transferred between Sei addresses. However, they can no longer be redeemed for the underlying asset. For the current state, see IBC is disabled. For the status of each asset, see Affected IBC assets.
This page lists the most important practical actions for the SIP-03 migration, with links to the official resources.
For the full proposal text, see:
  • The official SIP-03
  • Governance Proposal #99: started the migration.
  • Governance Proposal #115: disabled CosmWasm code uploads and contract instantiations. No new CosmWasm contracts can be deployed on Sei.
  • Governance Proposal #116: disabled inbound IBC transfers by setting the ibc module’s InboundEnabled parameter to false. IBC assets bridged from Cosmos chains can no longer arrive on Sei.
  • Governance Proposal #120: set InboundEnabled to false again, as a follow-up to Proposal #116. Outbound IBC was unchanged at the time.
  • Governance Proposal #121: disabled outbound IBC transfers by setting the ibc module’s OutboundEnabled parameter to false. IBC assets can no longer leave Sei. It passed on July 31, 2026.

​
What most users need to do

  • If you use Keplr or Leap (Cosmos-style wallets), move any assets on the native address (sei1…) to an EVM-compatible address (0x…). Use the Asset Transfer tool linked below.
  • If you already use Compass or another EVM wallet, you do not need to do anything. Continue as normal.

​
IBC is disabled

IBC (Inter-Blockchain Communication) is the Cosmos protocol that moved tokens between Sei and other Cosmos-SDK chains such as Noble, Kava, and Cosmos Hub. Assets that arrived this way exist on Sei as vouchers. A voucher is an ibc/... denom in the bank module, backed by the real asset escrowed on the origin chain. The only way to redeem a voucher is to send it back over the same channel that it came in on. Both directions are now closed. Two parameters on Sei’s ibc module control this, and both are false: Each parameter was set by a governance parameter change, which takes effect when the proposal executes. There is no separate upgrade or activation step. Inbound IBC was closed first, by Proposals #116 and #120. Outbound IBC closed on July 31, 2026, with Proposal #121.

​
What this means in practice

No longer possible:
  • Bridging any asset onto Sei over IBC.
  • Bridging any asset off Sei over IBC, including sending a voucher back to its origin chain to redeem the underlying asset.
  • IBC-based migration routes, such as sending USDC.n back to Noble to convert it to native USDC, or routing ATOM and WBTC out through Skip:Go.
  • The IBC precompile at 0x0000000000000000000000000000000000001009. Its transfer methods cannot succeed, and there is no replacement. Do not build against it.
Unaffected:
  • Native SEI transfers, staking, delegations, and rewards.
  • The Sei EVM, ERC-20 tokens, and native and CW pointer contracts.
  • Existing ibc/... balances in the bank module. They remain queryable and transferable between Sei addresses, including through their ERC-20 pointers. Only the redemption path off Sei is gone.
  • Already-deployed CosmWasm contracts, which can still be executed and queried. Proposal #115 blocked only uploads and instantiations. It is a separate change from the IBC parameters.
If you have an IBC transfer that was submitted but never completed, contact Sei Tech Chat or Discord. Both directions are closed, so do not assume that a pending transfer will settle or refund on its own.

​
Affected IBC assets

The assets below reached Sei over a bridge that is now closed. None of them has a route back to its origin chain. The Wormhole-bridged assets are not IBC vouchers and were not affected by Proposals #116, #120, or #121. They are listed here because Portal Bridge (legacy) is no longer available as a route off Sei.

​
What you can still do

  • Transfer within Sei. These balances move normally between Sei addresses and through their ERC-20 pointer contracts.
  • Swap on a Sei DEX. Swaps do not use IBC and still execute. These tokens can no longer be redeemed for the underlying asset, so the liquidity available for them is limited and may decline further. Check the quote before you trade.
  • Contact support. For anything else, including incomplete transfers and assets not listed above, ask for help in Sei Tech Chat or Discord.
The mention of third-party platforms does not constitute an endorsement. You should do your own research before you use any third-party service.

​
Key tools and resources

​
1) Asset Transfer (native ↔ EVM)

  • Use the official Sei Dashboard to move assets between native addresses (Keplr, Leap, Fin) and EVM addresses (MetaMask, Compass, and others). Go to Sei Dashboard Transfer or to the Bridge tab at Sei Dashboard Bridge.
When to use this:
  • You used Keplr or Leap before, and you want your assets to be available in an EVM wallet from now on.
  • You need to access tokens in dApps that now expect an EVM (0x) address.

​
2) USDC on Sei

Sei now supports native USDC and Circle’s CCTP V2. USDC from Noble (USDC.n) is deprecated.

​
If you still hold USDC.n

The route that sent USDC.n back to Noble to be reissued as native USDC required outbound IBC. As of Proposal #121, this route no longer works. USDC.n can no longer be redeemed through Noble or through Circle’s CCTP.
The only remaining option on Sei is an on-chain swap, which does not use IBC: For DeFi suppliers of USDC.n (Yei, Takara Lend, and other protocols):
  • If you have not already done so, wind down and withdraw your positions. Supplied USDC.n cannot be redeemed off Sei.
If you hold a balance that you cannot resolve this way, contact Sei Tech Chat or Discord.

​
3) Address association (Seistream)

Seistream’s SIP-03 migration page links your EVM (0x...) and Cosmos (sei1...) addresses for the native SEI token in three guided steps. It is a community-built tool that simplifies the standard association flow. Address association is the one-time, on-chain step that links your 0x... and sei1... addresses, so that a single key controls both. You must complete it before the SIP-03 upgrade. After the upgrade, Cosmos (sei1...) interfaces stop working, and addresses can no longer be associated. To learn how association works, see Account Linking. What the tool does:
  1. Connect wallet: Connect any EVM wallet with an injected provider (MetaMask, Keplr, Rabby, Compass, Tangem, Trust Wallet, OKX, and most others).
  2. Gas + association: Cover the small amount of SEI needed for gas. Seistream has a faucet for Sei Mainnet to help with this. Then submit the transaction that associates your 0x... and sei1... addresses on-chain. Any outgoing EVM transaction registers the link automatically.
  3. Transfer from Cosmos: Send your existing native SEI from the old Cosmos wallet to the linked sei1... address. The SEI then becomes spendable from your EVM wallet.
This tool is a simpler alternative to the manual association flow in Migrating a hardware or mnemonic-only wallet.
Seistream handles association for the native SEI token only. It does nothing for USDC.n, USDT.kava, ATOM, WBTC, or other IBC-bridged assets. For their status, see Affected IBC assets. Seistream is a third-party tool, and its inclusion here is not an endorsement. You should do your own research before you connect a wallet.

​
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 does not depend on the coin type. It gives the same 0x... and sei1... addresses in any wallet, so you do not need to move any funds. If your wallet cannot export a private key, you can still migrate: move 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 give you 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). If you import the same phrase into an EVM wallet such as MetaMask, the wallet derives it on coin type 60 (m/44'/60'/0'/0/0). The result is 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 lets you switch between the Cosmos app (coin type 118) and the Ethereum app (coin type 60). These apps control separate accounts with different addresses. The Cosmos-app account cannot be used from an EVM wallet.
For background, see HD paths and coin types.

​
Migration steps

This procedure 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.
If you prefer a guided flow, use Seistream’s SIP-03 migration tool. It walks through the same steps: connect an EVM wallet, cover gas, associate addresses, and then transfer native SEI from the Cosmos side. See Address association (Seistream). The tool covers native SEI only. The manual steps below work for any wallet that you control.
1

Create a new account in an EVM wallet you control

Use MetaMask, Compass, Rabby, or a Ledger with its Ethereum app. This creates a new 0x... address.
2

Fund the new address with a small amount of SEI

Approximately 0.1 SEI is enough. Association is an on-chain transaction, so the account needs SEI for gas. Fund the address from an exchange withdrawal or from any EVM wallet that already holds SEI.
3

Associate the new account on the Sei Dashboard

Connect the new EVM account to the Sei Dashboard. Then complete address association. This records the public key on-chain and links the 0x... address to its sei1... counterpart. The dashboard then shows the linked sei1... address, which is the destination for the next step. For details on association, see Account Linking.
4

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.
5

Confirm receipt

Because the addresses are associated, the test amount should appear under the new account on the dashboard. It should also appear as a spendable balance in the EVM wallet.
6

Transfer the remaining balance

After you confirm the test transfer, send the rest of the funds the same way. The assets are then held by an account whose key you control from an EVM wallet.
Send the 1 SEI test transfer and confirm receipt before you move the full balance. Verify that the destination matches the exact sei1... address shown after association in step 3.

​
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. You must complete steps 3 and 4 before then.
  • 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. If you associate the new account before you transfer, the funds arrive at the correct, immediately spendable address instead of a temporary holding address.
  • Optional verification. To confirm the paired sei1... address independently, call getSeiAddr(0x...) on the addr precompile. 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 make your assets available in an EVM wallet. See the Asset Transfer section above.

​
I use Compass wallet; do I need to do anything?

No, you do not need to do anything. Compass makes sure that your assets are available through EVM. Continue to connect to Sei as you would to 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 gives the same addresses in any wallet. Some setups cannot export a private key, such as a wallet that exports only a recovery phrase, or a Ledger that only switches between apps. In that case, follow these steps:
  1. Create a new account in an EVM wallet that you control.
  2. Fund the new account with a small amount of SEI.
  3. Associate the new account to reveal its paired sei1... address.
  4. Send a 1 SEI test transfer to that address. Then send your existing Cosmos funds to the same address.
For the full procedure, see Migrating a hardware or mnemonic-only wallet.

​
I stake SEI — do I need to do anything?

It depends on whether your Cosmos (sei1...) and EVM (0x...) addresses are associated (linked). The Cosmos staking module handles staking on Sei. After SIP-03, Cosmos-native transaction interfaces will no longer be available. However, the underlying staking state is preserved, and associated addresses can access it through EVM. If your addresses are associated: You do not need to do anything. After the upgrade, your existing delegations, rewards, and unbonding state will be fully accessible through EVM. You can continue to manage your stake from an EVM wallet with the Staking Precompile 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:
  1. Associate your addresses before the upgrade. To do this, connect your Cosmos wallet on the Sei Dashboard, or use any of the methods described in Accounts. After association, your staking state is accessible through EVM, and you do not need to unbond.
  2. Unbond your stake, and then migrate the assets to an EVM wallet with the Asset Transfer tool. The unbonding period is 21 days. For your tokens to be liquid in time, you must start this process at least 21 days before the Cosmos shutdown.
To check whether your addresses are linked, see Query linked addresses.
Do not confuse address linking with staking migration. The sei1... and 0x... addresses point to the same underlying account only after explicit association. Before that, the chain cannot recognize the link. Without association, your staked SEI will not be accessible through EVM after the upgrade. You will also have no way to unbond or claim rewards.

​
Can I still bridge assets into or out of Sei over IBC?

No. Proposal #116 and Proposal #120 disabled inbound IBC. Proposal #121 disabled outbound IBC on July 31, 2026. The InboundEnabled and OutboundEnabled parameters on the ibc module are now both false, so the chain does not accept IBC transfers in either direction. See IBC is disabled.

​
I hold an IBC asset on Sei — is it gone?

The balance is not gone. It still exists in the bank module, and it is still visible in explorers and wallets. You can still transfer it between Sei addresses and through its ERC-20 pointer. However, you can no longer send it back over IBC to redeem the underlying asset on its origin chain. See What you can still do.

​
I hold USDC.n (USDC via Noble) — what should I do?

USDC.n can no longer be redeemed. The migration route sent USDC.n back to Noble over IBC and reissued it as native USDC through Circle’s CCTP. That route required outbound IBC, which Proposal #121 disabled on July 31, 2026. An on-chain swap to native USDC on a Sei DEX does not use IBC and still executes, subject to whatever liquidity remains. See If you still hold USDC.n above. For background, read the original announcement: Holders of USDC.n Need to Swap or Migrate.