Sei has completed the v6.6 mainnet upgrade and described it as the biggest version release in the roughly two years since EVM support was added in May 2024. Two of the three major upgrades under the Giga plan are now officially live. The Ares upgrade is running, with the v2 executor being gradually retired. The Eidos upgrade is also active, separating two years of on-chain state by moving EVM historical data into an independent database, so it no longer shares Cosmos state. The upgrade fixes more than 30 issues and optimizes node synchronization efficiency, consensus timeout parameters, error-prone configuration items, and data pruning. Developer-facing improvements include better receipt generation, JSON-RPC error handling, and historical call tracing.
Sei has completed the v6.6 upgrade on mainnet. The team says it is the largest version upgrade in the roughly two years since EVM support was added in May 2024, and two of the three major upgrades planned under the Giga initiative have officially gone live.
The Ares upgrade is now active, retiring the v2 executor in stages. The Eidos upgrade has also launched, separating two years of on-chain state by migrating EVM historical data into a dedicated database rather than sharing Cosmos state. The release fixes more than 30 issues, alongside optimizations to node synchronization efficiency, consensus timeout parameters, error-prone configuration items, and data pruning. Developer-facing features also improved, including receipt generation, JSON-RPC error handling, and historical call tracing.
This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan. Disclaimer:
The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.
Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.
