简化SEI的体系结构，仅关注EVM

支持EVM和COSMWASM有助于吸引广泛的用户和开发人员。但是，这种双重结构的方法也引起了严重的头痛。

As Web3 technology rapidly advances, new protocols are continually being developed to improve the user experience and drive adoption. Among the innovations that have emerged in recent years is the integration of various programming models for smart contracts.

随着Web3技术的迅速发展，不断开发新协议以改善用户体验并推动采用。近年来出现的创新是智能合约的各种编程模型的整合。

One protocol that has been at the forefront of this integration is Sei. In its v2 version, released in 2024, Sei introduced support for both the Ethereum Virtual Machine (EVM) and CosmWasm, a WebAssembly-based system used by Cosmos chains. The aim was to provide maximal flexibility for users and developers in deploying and interacting with diverse applications.

该集成最前沿的一种协议是SEI。 SEI在2024年发布的V2版本中引入了对以太坊虚拟机（EVM）和Cosmwasm的支持，这是Cosmos链使用的基于WebAssembly的系统。目的是为用户和开发人员提供最大的灵活性，以与不同的应用程序进行部署和互动。

However, a new proposal submitted through the Sei Improvement Proposal (SIP) process suggests streamlining Sei into a fully EVM-based chain. This proposal, which is being put forth by @Sei_Labs, aims to reduce the complexity of developer experience, infrastructure maintenance, and user interaction with the network.

但是，通过SEI改进建议（SIP）过程提交的一项新提案建议将SEI简化为完全基于EVM的链条。 @SEI_LABS提出的这一建议旨在降低开发人员体验，基础架构维护和用户与网络的互动的复杂性。

Why Dual Support Became a Double-Edged Sword

为什么双重支撑成为双刃剑

In theory, letting users interact with both Cosmos-native and EVM-based apps was a win for flexibility. Sei’s architecture allowed interoperability between Ethereum’s EVM and Cosmos’s WasmVM, a WebAssembly-based system that powers smart contracts. But in practice, the setup created several sticking points.

从理论上讲，让用户与宇宙本地和基于EVM的应用程序进行交互是灵活性的胜利。 SEI的体系结构允许以太坊的EVM和Cosmos的WASMVM之间的互操作性，这是一个基于WebAssembly的系统，可以为智能合约提供动力。但是实际上，设置创造了几个粘点。

Users have to manage two separate wallets—EVM and Cosmos—and manually link them to access the network’s full features. For developers and infrastructure providers, the situation is even more tangled. Indexers, explorers, and node operators must write custom logic to sync data between two incompatible systems. This overhead increases code complexity, introduces bugs, and slows development.

用户必须管理两个单独的钱包 - EVM和Cosmos，并手动将它们链接起来以访问网络的完整功能。对于开发人员和基础设施提供商，情况更加纠结。索引器，探险家和节点运算符必须编写自定义逻辑以在两个不兼容的系统之间同步数据。该开销增加了代码复杂性，引入错误并减慢开发。

SIP-3: A proposal from @Sei_Labs to streamline Sei’s architecture to an EVM-only model has been submitted through the Sei Improvement Proposal process.

SIP-3：通过SEI改进提案过程提交了@Sei_Labs对简化SEI架构到仅EVM模型的建议。

This proposal aims to enhance developer experience, simplify infrastructure, and fully leverage Sei’s parallelized EVM… pic.twitter.com/nxQ9cGYXj2

该建议旨在增强开发人员的体验，简化基础架构并完全利用SEI并行的EVM…pic.twitter.com/nxq9cgyxj2

— Sei 밝은 빨간색 (@SeiNetwork) 5월 7, 2025

- SEI鲜红色（@Seinetwork）2025年5月7日

The numbers speak volumes. Since the release of Sei v2, EVM-based usage has skyrocketed. According to on-chain analytics from SeiScan, over 85% of transaction volume on the network is now being generated by EVM addresses. Popular apps like Astroport, which recently migrated from Terra to EVM-compatible chains, are also contributing to this trend. The market is speaking—and it’s leaning heavily toward EVM.

数字说的数量。自SEI V2发行以来，基于EVM的用法飙升。根据Seiscan的链分析，现在由EVM地址生成了网络交易量的85％以上。最近从Terra迁移到EVM兼容链的Astroport之类的流行应用也促进了这一趋势。市场在说话 - 它倾向于EVM。

The Proposal: Moving to an EVM-Only Architecture

提案：移至仅EVM架构

The new governance proposal recommends sunsetting CosmWasm support and concentrating fully on EVM. Under this plan:

新的治理建议建议日落宇宙支持并完全专注于EVM。根据此计划：

Only EVM addresses will be able to initiate transactions on the network.

只有EVM地址才能在网络上启动交易。

New CosmWasm deployments and IBC transfers will be disabled.

新的宇宙部署和IBC转移将被禁用。

Execution of CosmWasm contracts and native Cosmos transactions will be phased out.

执行宇宙合同和本地宇宙交易将被淘汰。

Internal protocol features like staking and governance will still function via precompiles, meaning core functionality of the protocol will be maintained even as external code is sunsetted.

内部协议功能（如桩和治理）仍将通过预编译来运行，这意味着即使外部代码被日落，协议的核心功能也将得到维护。

Technically, the transition will depend on a few key milestones. One is the creation of “EVM pointers,” which will allow seamless access to existing Cosmos assets from the EVM side. The next steps will involve the complete shutdown of CosmWasm contract deployment and, finally, the termination of legacy interactions with the CosmWasm runtime.

从技术上讲，过渡将取决于一些关键里程碑。其中之一是创建“ EVM指针”，它将允许从EVM一侧无缝访问现有的Cosmos资产。接下来的步骤将涉及宇宙合同部署的完全关闭，最后，与宇宙运行时的遗产互动终止。