TLDR:
- Sei Labs requires all exchanges to complete SEI EVM migration by June 15, 2026, or face fund loss.
- Every native sei1… address already has a paired EVM 0x… address on the same Sei blockchain.
- Four migration paths exist, ranging from automated smart contracts to fully manual fund transfers.
- After deprecation, Cosmos RPC endpoints and address associations will be permanently unavailable.
Sei Labs has announced a firm deadline for exchanges and custodians holding SEI tokens. The protocol is completing its transition to a unified, EVM-only architecture.
All platforms must migrate customer holdings from native Cosmos addresses to EVM addresses before June 15, 2026.
After that date, Cosmos and IBC-related functionality will be deprecated permanently. This move affects any service provider currently supporting SEI token deposits and withdrawals using native sei1… addresses.
What the Sei EVM Migration Means for Exchanges
Sei EVM is not a separate blockchain from the Sei network. It is the same chain with a second method of interaction.
Any integration currently treating both as distinct chains must be consolidated before the Cosmos shutdown. Exchanges operating under a split integration model need to act quickly.
Every native sei1… address has a corresponding EVM 0x… address on the same chain. The pairing exists at the keypair level and does not require any funds to move.
Exchanges need to derive or look up the EVM address for each native wallet under management. They must also ensure addresses are associated on-chain before the deprecation date.
Sei Labs stated on X: “The core thing exchanges and custodians need to know: Sei EVM is not a separate chain. It’s the same chain with a second way to interact with it.”
After June 15, 2026, Cosmos-native transaction interfaces will no longer be available. Exchanges will not be able to broadcast Cosmos-format transactions or interact via Cosmos RPC endpoints.
Address associations will also no longer be creatable through a Cosmos wallet. The FundsForwarder pattern will stop functioning for new deposits as well.
Four Migration Paths Available to Custodians
Sei Labs has outlined four upgrade paths for exchanges and custodians to follow. The first involves combining native and EVM access points, which is the cleanest option available.
The exchange surfaces the EVM address corresponding to each existing native wallet directly to customers. No funds need to move, and no customer action is required.
The second option involves an automated forwarding contract deployed by the exchange. The FundsForwarder smart contract moves customer funds from the native side to the EVM wallet automatically.
The contract was audited by OtterSec and has a fixed destination address. That destination cannot be changed after deployment.
The third path is a user-directed forwarding contract, where customers initiate the transfer themselves. This triggers the contract to forward funds to the appropriate EVM wallet on the exchange.
It suits exchanges that cannot operate the contract directly. However, it still provides customers with an automated destination.
The fourth option is a fully manual transfer, requiring customers to withdraw and redeposit funds. Exchanges notify customers to move holdings to a self-custodial wallet first.
Customers then redeposit to the new EVM address provided by the exchange. Sei Labs confirmed the June 15 deadline is firm, and address association must be completed before deprecation.
