SIP-3 Update: Sei Moves Toward EVM-Only Architecture

The first feedback period for SIP-3 (EVM-Only) has concluded, and the response has been significant. The engagement from developers, infrastructure providers, and users demonstrates the community's commitment to the Sei protocol's evolution toward continual performance improvements as the fastest and most streamlined EVM chain.

Following a community feedback period and discussion, SIP-3 passed its initial governance vote.

This marks the beginning of a multi-phase transition that will require several additional checkpoints in the implementation process.

What Implementing SIP-3 Means for the Sei Network

Implementing the SIP-3 proposal will transition the Sei network to an EVM-only architecture by deprecating CosmWasm and native Cosmos transactions. This streamlining aims to reduce complexity, improve developer experience, and position Sei more competitively within the broader EVM ecosystem while maintaining its performance advantages.

Key Focus Areas Based on Feedback

Several themes emerged from community discussions that will guide the refinement of SIP-3 and its implementation:

• Migration support for CosmWasm projects currently deployed on Sei
  • Asset transfer mechanisms to ensure users can seamlessly move between environments.
  • Technical specifications for EVM precompiles that will replace core Cosmos functionality.
  • Infrastructure guidance for RPC providers and indexers.
• Further education on what assets would be affected
  • Some community members expressed concerns about potential impacts to their EVM assets even though these assets would remain unaffected by SIP-3's implementation. 
  • Only CosmWasm assets will need to be migrated by ecosystem stakeholders.

Expected Timeline

A comprehensive update with the revised proposal and implementation schedule will be shared within the coming months. This will include concrete dates for each phase of the transition to ensure all ecosystem participants have adequate time to prepare.

No immediate action is required from users or developers at this time. 

Subscribe to the github discussion to be notified of updates.

What Happens Next

The SIP author (Philip Su) will now:

• Review all feedback received through forums, GitHub, and community channels.
• Continue to revise the SIP-3 github repo as more resources are added.