Sei proposes shift to EVM-only model to resolve complexity and boost adoption
The post Sei proposes shift to EVM-only model to resolve complexity and boost adoption appeared on BitcoinEthereumNews.com.
Layer-1 network Sei has initiated a proposal to streamline its architecture and focus solely on the Ethereum Virtual Machine (EVM) model. The developer firm Sei Labs has submitted a Sei Improvement Proposal (SIP) for the community to vote on. According to the SIP-3, the project will deprecate support for CosmWasm and native Cosmos accounts while it turns its attention to supporting EVM. This will mark a complete shift for the layer-1 blockchain. Sei network was originally built using the Cosmos software development kit (SDK). However, it upgraded to include EVM support with the Sei v2, a move calculated to attract more DeFi developers, given that over 70% of all smart contracts were initially deployed on Ethereum. The move has paid off, with the network offering flexibility through EVM and Cosmos accounts. However, the proposal noted that the dual architecture has also increased complexity for users and developers. Users have to manage both EVM and native addresses and link the two to fully enjoy network functionality, while infrastructure providers and developers also have to deal with more overhead costs due to the complexities. The network now seeks to address this problem and has chosen to focus on EVM because EVM has dominated network activity on Sei. According to the proposal, EVM addresses account for over 80% of transactions since August. EVM addresses dominate activity on Sei network (Source: Dune Analytics) With the proposal, only EVM addresses can initiate transactions, and all Cosmos-based contracts will be deprecated and subsequently removed. It said: “The proposal recommends that Only EVM addresses be allowed to initiate transactions on Sei. The network will support EVM-only transactions going forward. CosmWasm contracts and native Cosmos message handling will be deprecated and removed.” However, Sei native addresses will remain functional for internal protocol processes such as validator addresses. Core…
Filed under: News - @ May 8, 2025 1:26 pm