Sei has started deploying its Eidos storage upgrade on mainnet through the network’s v6.6 release, beginning a staged overhaul of how the layer-1 stores and verifies on-chain data. The work is part of Sei’s broader Giga roadmap, which is aimed at supporting throughput of 200,000 transactions per second.

The rollout is designed to happen without taking the network offline. During the transition, Sei is running the current and new storage systems in parallel, while governance retains the ability to pause or roll back the process if necessary.

Storage architecture rebuilt in phases

According to the announcement, Eidos changes the underlying storage design used by the network, with the first phase starting on mainnet in version 6.6. The upgrade focuses on improving how state data is handled as Sei works toward much higher transaction throughput.

A central change is the separation of EVM state into a dedicated database. Sei says this is intended to stop historical queries from competing with live transaction processing, which can become a bottleneck as network activity grows.

FlatKV and LtHash planned for later stages

Later stages of Eidos are expected to replace Merkle-tree-based storage for EVM state with FlatKV, a flat key-value storage model, and to use LtHash, or lattice hashing, for verification. Sei says this approach would allow constant-time updates as state changes.

The network is also introducing LittDB as a separate storage engine for blocks and receipts. The stated goal is to support high write throughput while still handling large reads, two demands that can conflict in more traditional designs.

Active and historical data handled differently

Sei’s plan also changes where different kinds of data are kept. Historical data is expected to be moved into archival systems, while more recent data stays on faster storage so it can be accessed quickly by active nodes and applications.

That split is meant to reduce the storage burden on active nodes without removing access to older chain records. In practical terms, it is part of the broader effort to keep the network responsive while scaling up capacity.

Network stays online during migration

The migration is being carried out while Sei remains online, rather than through a one-time shutdown and cutover. Existing and new storage systems are operating at the same time during the rollout, allowing the network to keep serving balances, smart contracts and RPC endpoints throughout the process.

Sei said node operators and users do not need to take action as the upgrade proceeds. The next confirmed steps are the later Eidos phases, including the planned addition of FlatKV and LtHash, with governance mechanisms in place if the rollout needs to be paused or reversed.

Source: crypto.news