Deep Dive
1. Tokenomics Revision (9 June 2026)
Overview: This is a financial and governance update, not a codebase change. The Eclipse Foundation announced it had "decentralized the ownership of the ES token" through an OTC sale and revised tokenomics.
The update focuses on reallocating the token supply, with 47% going to early investors and contributors and 53% to ecosystem development and liquidity. The foundation confirmed selling some treasury assets to fund operations but did not disclose details. This move appears aimed at addressing exchange delisting reviews and improving long-term project sustainability.
What this means: This is neutral for Eclipse because it addresses financial structure and exchange compliance rather than improving the network's technology, speed, or security. The lack of transparency around the asset sale could concern users focused on project health.
(Eclipse)
Overview: These updates highlight the capabilities of the underlying GigaScale Virtual Machine (GSVM) but are not recent code commits. They were shared as research achievements in a July 2025 newsletter.
The team introduced AlDBaran, a system that sustained 48 million state updates per second on a 96-core server, breaking a potential bottleneck. They also released an in-house ed25519 signature-verification library, achieving nearly 9 million verifications per second on server-grade hardware.
What this means: This was bullish for Eclipse because it demonstrated the raw performance potential of its core technology, suggesting the chain could handle massive transaction loads efficiently. However, these are not recent live-network upgrades.
(Eclipse Labs)
3. Mainnet Architecture Documentation (21 February 2025)
Overview: This documentation commit formalizes Eclipse's shift to a fixed architecture. It explains that Eclipse Mainnet is a single, shared optimistic rollup using the Solana VM for execution, Ethereum for settlement, and Celestia for data availability.
The docs detail technical choices like using RISC Zero for succinct fraud proofs to shorten dispute times. This provides a clear reference for developers but does not constitute a new feature or patch.
What this means: This is neutral for Eclipse as it simply documents the established technical design. It aids developer understanding but doesn't change network functionality or user experience.
(GitHub)
Conclusion
The available information shows a focus on financial restructuring and dated technical research, with no evidence of recent code commits, security patches, or protocol upgrades. How will the project's new focus on in-house application development translate into tangible network improvements?