Sei v6.7 Goes Live With Mandatory Mainnet Upgrade Ahead of Major EVM Migration
Sei has activated v6.7 on its Pacific-1 mainnet, marking a major protocol upgrade ahead of a separate migration to the network’s new EVM storage layer. Sei described the upcoming storage migration as its biggest migration since January 2024 and said the changes move the network another step toward its longer-term Giga roadmap.
The v6.7 release is a mandatory upgrade for all Pacific-1 node operators and validators. According to Sei’s upgrade instructions, nodes that fail to upgrade will halt at the designated upgrade height and fall out of consensus, making the release an important operational change for infrastructure providers across the network.
Sei v6.7 Brings Major Network Changes
The upgrade was scheduled around block height 236,450,000, with the target upgrade time set for October 8 at approximately 16:30 UTC. Sei expected the network to experience only a few minutes of downtime while validators switched to the new version.
The on-chain upgrade name is v6.7, while the corresponding binary and Git tag are identified as v6.7.0. Sei specifically warned Cosmovisor users that the upgrade directory must use the on-chain name, v6.7, rather than the v6.7.0 Git tag.
The release introduces several changes that node operators and infrastructure providers need to account for. Among them is a reduction in the WebSocket frame limit from 10 MiB to 5 MiB, although operators can configure a higher request-body limit under the EVM settings when their applications require larger requests.
ABCI and gRPC pagination limits have also been tightened for untrusted callers. The new restrictions cap pagination parameters and iteration counts, while indexers can use next_key, trusted CIDR configurations or private nodes with disabled limits depending on their infrastructure requirements.
Another significant change is the removal of IBC, capability and feegrant functionality. Sei said IBC and transfer queries, as well as decoding historical IBC transactions, will require a v6.6 node operating in freeze mode, while transactions using a fee granter other than the payer will be rejected.
The upgrade also removes several legacy JSON-RPC methods beginning with sei_ and sei2_. Developers are being directed toward standard Ethereum-compatible eth_* methods instead, with only sei_getSeiAddress, sei_getEVMAddress and sei_getCosmosTx remaining among the legacy Sei-specific methods.
Storage Migration Sets Stage for Sei Giga
Beyond the immediate v6.7 release, Sei’s next major step is a separate migration to its new EVM storage layer. The network has characterized this as its largest migration since January 2024, making the transition important for developers, validators and applications that depend on Sei’s EVM infrastructure.
The v6.7 codebase includes extensive work around the new storage architecture. The release contains improvements involving LittDB, including block storage, indexing, receipt storage, compression, state management and database performance, alongside changes designed to improve the handling of EVM workloads.
Several EVM RPC improvements are also included. These cover request-size controls, limits on gas estimation calls, restrictions around block-receipt fan-out, concurrent log subscriptions and memory bounds for debugging and tracing operations.
Sei has also continued work on Autobahn, its consensus and performance infrastructure, with changes covering hash storage, committee and stake management, block production checks, metrics and full-node functionality. The collection of updates shows that v6.7 extends beyond a simple version change and touches multiple layers of the network.
For developers, the migration means that compatibility needs to be considered before applications move onto the new storage layer. The removal of legacy APIs and tighter request limits make it particularly important for infrastructure providers and indexers to review their configurations and RPC usage.
Sei’s stated objective is to move closer to Giga, its next-generation architecture focused on scaling the network for high-performance applications, particularly trading. The v6.7 upgrade and subsequent EVM storage migration are therefore being positioned as steps in a much larger technical roadmap.
With v6.7 now live, attention shifts toward the separate EVM storage migration and how the new infrastructure performs under production workloads. The mandatory upgrade introduces meaningful changes for node operators, while the underlying storage and EVM work provides part of the technical foundation Sei says it needs as it moves toward Giga.
About The Author
