-
Sei Labs proposes SIP-3 to transition the Sei network to an EVM-only model, removing CosmWasm and native Cosmos support.
-
The transition will simplify Sei’s ecosystem, enhance user and developer experience, and reduce infrastructure overhead.
-
The shift will require users and developers to migrate to EVM-native wallets and adapt to new systems for EVM-only compatibility.
Sei Labs gears up for a monumental shift to an EVM-only architecture, promising enhanced performance and user experience.
Sei Labs Pushes for EVM-Only Network
SIP-3 suggests that only EVM addresses can initiate transactions, and all future transactions should be EVM-exclusive. It seeks to phase out CosmWasm contracts and native Cosmos messaging.
However, essential features like staking and governance will remain available through precompiles.
“Moving to an EVM-only architecture will significantly simplify the Sei developer and user experience, reduce infrastructure overhead, and position Sei more strongly within the broader EVM ecosystem,” the proposal read.
Importantly, SIP-3 includes a three-phase approach to the EVM-only transition. The first phase focuses on creating EVM pointers. This ensures that all Cosmos and CosmWasm assets are accessible from the EVM side.
In the second phase, new CosmWasm deployments will be deprecated. Additionally, Cosmos-based inbound IBC transfers will be blocked. The final phase will involve disabling legacy interactions, removing support for CosmWasm contract execution, and transactions involving non-EVM addresses.
Phillip Su, Engineering Manager and Lead at Sei Labs, noted that a significant portion of the network activity is already EVM-based, justifying the decision to focus fully on this. The usage has surged since the launch of Sei v2.
Sei Network introduced EVM support with Sei v2 in Q2 2024. The network’s performance has been impressive since then.
Su highlighted that it has reached over $500 million in Total Value Locked (TVL). Sei v2 has over 19.3 million total wallets, and a daily transaction volume surpassing 4.1 million. Additionally, the network boasts over 300,000 daily active addresses and hosts more than 200 projects on its mainnet.
While Sei has achieved notable growth, the dual architecture has introduced several challenges. It requires users to manage EVM and native addresses.
Additionally, the infrastructure requires custom logic for compatibility between the two ecosystems, placing extra burdens on node providers and developers. Maintaining cross-compatibility also increases codebase overhead. Therefore, this complicates debugging and testing. By focusing solely on EVM, Sei aims to eliminate these challenges.
“The proposed transition will lead to greater adoption, improved developer experience, and a more cohesive community. What excites me most is how this positions Sei to solve the EVM’s biggest limitation: performance at scale,” Su wrote.
However, the proposal outlined that users, developers, and infrastructure teams would need to make some changes to adapt. Teams that provide core services like RPC (Remote Procedure Call) and indexing must ensure their systems interact only with EVM APIs.
Users will need to migrate assets to EVM-native wallets or use bridging mechanisms. Lastly, application developers must port CosmWasm applications to EVM and ensure compatibility with EVM frontends. This shift will require significant effort, but it will also unlock the full potential of Sei’s EVM ecosystem.
While SIP-3 promises enhanced performance and adoption, its success will depend on the community’s ability to navigate migration challenges and the active participation and feedback of the Sei community.
Conclusion
The transition to an EVM-only model represents a strategic evolution for Sei, poised to streamline operations and attract a broader developer base. Continued community engagement will be vital to ensure a smooth migration.
