iExec Schedules V9 Mainnet Launch for August 12
The decentralized computing platform iExec has set a firm date for its next major protocol upgrade, announcing that the V9 mainnet will launch on August 12, 2025 [1, 2]. The announcement, a key milestone in the project’s 2025 roadmap, was made through its official social media channels [1].
Facts, in 30 seconds
- Decentralized computing platform iExec has scheduled its V9 mainnet upgrade for August 12, 2025 [1, 2].
- The launch date was confirmed through announcements on the project’s official social media and blog [1, 2].
- The V9 upgrade represents a significant milestone in the protocol’s 2025 roadmap [2].
- iExec specializes in providing a marketplace for trustless and confidential computing resources [2].
The team first shared the news on X (formerly Twitter) before publishing a detailed blog post that framed the V9 launch as a significant step toward “the future of decentralized computing” [1, 2].
iExec operates as a marketplace for cloud computing resources, falling under the growing category of Decentralized Physical Infrastructure Networks (DePIN). The platform enables users to monetize their spare computing power or rent resources like CPUs and GPUs on-demand. Its core value proposition is providing trustless and confidential computing, which ensures data remains secure and private during processing.
While the full technical details of the V9 upgrade have not been disclosed, major version releases typically introduce substantial improvements to a protocol’s performance, security, and feature set [2]. The positioning of V9 as a cornerstone of the 2025 roadmap suggests it will bring new capabilities to the iExec ecosystem [2]. More specific information is expected as the launch date approaches.
The platform’s native token, RLC, reacted modestly to the news. At the time of the announcement, RLC was trading at approximately $2.45, reflecting a 3.1% increase over the previous 24 hours, with a total market capitalization of around $196 million [3].
Sources
Original Source: Link
