Sei v6.4 Is Live on Mainnet: What It Means for IBC
Sei Network is now running on release v6.4, which includes the ability to (eventually) disable the inbound transfer of IBC assets. Here's what you need to know.
The latest release, v6.4, is the next step in the Sei protocol's migration an EVM-only architecture. Importantly, it includes the ability to (eventually) disable the inbound transfer of IBC assets. Here's what you need to know.
What v6.4 does
v6.4 adds the protocol-level ability to disable inbound IBC transfers. IBC is Cosmos' native interoperability protocol. Once this capability is activated, users will no longer be able to bridge Cosmos-native assets (such as ATOM, USDC.n, Kava USDT, or Wormhole-wrapped tokens) into Sei Network.
What v6.4 does not do
v6.4 does not disable inbound IBC transfers on its own. The technical capability ships with v6.4, but the actual change will only take effect after a follow-on governance proposal is passed. Sei Labs will publish that proposal separately, and the community will have advance notice before the change goes live.
Why this matters
Last May, the Sei community accepted SIP-3, a proposal to deprecate CosmWasm and native Cosmos transactions in order to make Sei a streamlined, EVM-only chain. Version 6.4 is part of that broader transition. This is the release that makes it possible to begin winding down Cosmos-native asset flows into Sei.
What you should do now
If you hold any non-SEI IBC assets on Sei, you should take action before the governance proposal activates the change. Specifically:
- Swap your IBC assets for EVM-native equivalents where possible. For smaller volume conversions, you may be able to swap using Saphyre or Symphony. Slippage may vary depending on market conditions and liquidity. The mention of these platforms does not constitute an endorsement, and users should do their own research before using any third-party service.
- Bridge your IBC assets to their origin chain using a frontend like Skip:Go. The mention of this platform does not constitute an endorsement, and users should do their own research before using any third-party service.
- Unwind DeFi positions that rely on IBC assets before the deadline.
For a full list of affected assets, recommended actions, and migration routes, visit the SIP-3 Migration Guide.
What's next
After the governance proposal to disable inbound IBC transfers passes, additional network releases will add the ability to disable outbound IBC transfers and remove Sei's native oracle solution. These upgrades are expected in the coming months, and will formally complete the SIP-3 migration to Sei’s EVM-only architecture.
