Pi Network has successfully completed its Protocol 24 Mainnet upgrade, the Pi Core Team confirmed in an X post on Friday, describing it as one of the most challenging migrations the network has undertaken. The team has now set June 18 as the deadline for the next upgrade, Protocol 25.
- Pi Network has successfully completed its Protocol 24 Mainnet upgrade, the Pi Core Team confirmed in an X post on...
- The team has now set June 18 as the deadline for the next upgrade, Protocol 25.
- According to community reports, more than 100 nodes were upgraded, with operators noting that block-delay issues had been resolved and...
- The upgrade is expected to enhance node performance, improve scalability, and advance smart contract capabilities on the Mainnet.
Keep reading for the full breakdown on Blockchain — everything you need to know is covered below.
The Protocol 24 rollout required all Mainnet node operators to update their software by June 2 or risk disconnection from the network. Nodes that fail to upgrade will be cut off from Pi’s canonical chain, losing the ability to validate transactions and earn rewards during any period of downtime.
Techpression previously reported the completion of Protocol 23 in May as part of Pi Network’s sequential rollout of upgrades spanning Protocols 19 through 26.
What Protocol 24 delivered
Protocol 24 focused on improving core network performance, node synchronisation, and overall system stability. According to community reports, more than 100 nodes were upgraded, with operators noting that block-delay issues had been resolved and that synchronisation across the network had improved.
Unlike Protocol 23, which involved rewriting database files and carried a risk of data corruption, Protocol 24 was described by the Pi Core Team as a relatively clean migration. However, coordinating the upgrade across a globally distributed node infrastructure contributed to its reputation as one of the network’s most demanding upgrades.
Node operators on Windows and macOS received the update automatically through the Pi Desktop application. Linux users running the Pi Node CLI were required to either enable automatic updates or manually trigger the upgrade using the `pi-node update-protocol` command. Nodes confirmed readiness once their status field displayed “Synced.”
With Protocol 24 now complete, attention shifts to Protocol 25, which carries a June 18 deadline. The upgrade is expected to enhance node performance, improve scalability, and advance smart contract capabilities on the Mainnet. Protocol 26, the final phase of the current roadmap, is scheduled for June 22.
The Protocol 25 cycle is also linked to PiRC1 upgrades, which are expected to expand token standards and smart contract functionality across the network. Earlier this year, Pi Network introduced subscription-based smart contracts on Testnet under PiRC2. The ongoing protocol upgrades are intended to lay the technical foundation for a full Mainnet smart contract rollout.
What the Pi Network ecosystem looks like
Pi Network currently reports 18.1 million KYC-verified users and 16.72 million completed Mainnet migrations, with more than 119,000 second migrations processed. The network has also logged more than 526 million identity-verification tasks, positioning its validator ecosystem as human-powered infrastructure for AI applications.
The protocol upgrades are unfolding against a bearish market backdrop. PI is currently trading near $0.136, close to its all-time low, as daily token unlocks continue to weigh on price performance. Data indicates that approximately 163.6 million PI tokens are expected to enter circulation over the next 30 days, with a peak daily unlock of nearly 16 million tokens projected around June 11.
Despite the ongoing price pressure, the Pi Core Team appears focused on strengthening the network’s underlying infrastructure. The completion of Protocol 24 and the upcoming rollout of Protocol 25 suggest that the project’s immediate priorities remain centred on scalability, stability, and preparing the Mainnet for broader smart contract functionality.













