Sei Network Disables IBC Asset Transfers, Migrating to EVM-Only Architecture

iconKuCoinFlash
Share
Share IconShare IconShare IconShare IconShare IconShare IconCopy
AI summary iconSummary

expand icon
On May 13, 2026, the Sei Network announced it has disabled IBC asset transfers following a community proposal. Users are urged to bridge their IBC assets out before withdrawals are suspended. The April network upgrade enabled this transition, with some users already receiving airdrop reminders. This move aligns with the broader trend in digital asset news toward EVM-focused blockchain development.

BlockBeats report: On May 13, Sei Labs announced that, following a community proposal, the Sei Network has officially disabled the function for importing IBC assets. The official notice warns wallet holders still holding IBC assets on the Sei Network to promptly bridge and withdraw their assets, as Sei will further disable the function for exporting IBC assets in the future.


Sei Labs stated that the Sei v6.4 upgrade released in April introduced a mechanism to disable IBC asset transfers. Some wallet holders with related assets previously received airdrop notifications urging users to complete bridging or exchange operations before Sei fully transitions to an EVM-only architecture.


This means Sei is gradually reducing its compatibility with the original Cosmos IBC ecosystem and moving further toward becoming an EVM chain.

Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.