Sei, the blockchain built on the Cosmos SDK, is floating a future centered on the Ethereum Virtual Machine. The chain's team has signaled that it may trade Cosmos-native flexibility for the network effects of the EVM — potentially cutting support for CosmWasm smart contracts and narrowing the role of the Inter-Blockchain Communication protocol. The move would chase a bigger addressable market among Ethereum developers, but risks alienating part of the original Cosmos base.
What Sei is proposing
Under the plan, Sei would run EVM contracts in parallel to reduce contention and raise throughput, while keeping low-latency confirmation. The 'EVM-only' label can mean different things: prioritizing the EVM runtime and possibly sunsetting CosmWasm; keeping IBC in a narrower role; or adopting EVM-native RPCs and wallets while reducing Cosmos tooling. The exact scope is still being defined — official docs and upgrade notes at docs.sei.io are supposed to be the final source of truth.
CosmWasm could become second-class or phased out entirely. Developers who built on Cosmos' Rust-based smart contract framework face an uncertain path. Validators, indexers, bridge providers, market makers — anyone relying on IBC-linked liquidity — would have to reconfigure if Sei cuts its IBC connection.
Why now
L2s have raised the bar on speed and user experience. Builders increasingly expect EVM tooling out of the box. Across crypto, gravity pulls toward the EVM because of its mature tooling, liquidity, and developer mindshare. Cosmos brought modularity and sovereignty, but many sovereign chains now face a strategic fork: interoperate with EVM natively or risk a thinner pipeline of developers and users.
Sei launched as a trading-first chain with fast finality. Over time the team introduced performance features and signaled a stronger EVM roadmap. This month's announcement crystallizes that direction.
The developer calculus
For teams, the trade-off is clear. The EVM gives immediate access to Hardhat, Foundry, standard RPCs, and established indexers. CosmWasm offers safety features and Rust ergonomics, but its learning curve and smaller talent pool slow hiring and audits. An EVM-only approach also simplifies gas economics for Solidity dApps and enables standard MEV tooling and protections — but it imports Ethereum's MEV dynamics: bundle markets, searchers, and the risk of toxic flow if order flow isn't protected.
Cosmos-native routes sometimes insulated apps via custom modules. EVM uniformity trades that insulation for familiarity.
The question now is whether Sei keeps IBC as a central bridge to Cosmos liquidity or isolates itself from the appchain ecosystem. Without IBC, Sei risks being a standalone EVM chain competing against L2s and L1s that already dominate that space. The next upgrade notes should reveal how far the team is willing to go.
