Pi Network announced that all mainnet node operators must complete the upgrade to Protocol 25 by June 18 or risk losing connection to the network. The Pi Core Team issued the directive as part of the project's ongoing mainnet development roadmap, which is gradually transitioning nodes from Protocol 19 through Protocol 26. The upgrade requirement follows the successful rollout of Protocol 24 and continues Pi Network's sequential migration process, where nodes must upgrade in order and cannot skip versions. The announcement on X reminded operators to plan ahead for the migration, sparking immediate discussion across the Pi community as operators prepare for the network-wide transition.
Protocol 25 Marks Next Step in Upgrade Path
The current upgrade path moves from version 24.1 to 25.2, with Protocol 26 expected to follow at a later date. According to the roadmap, nodes must upgrade sequentially and cannot skip versions. Unlike some previous migrations, the Protocol 25 upgrade is designed to be relatively quick. Pi Network said most nodes should experience less than five minutes of downtime during the process. The team advised operators not to upgrade all nodes simultaneously. Instead, they should redirect traffic to other nodes or use Pi's mainnet API infrastructure while the migration is underway.
Node Operators Prepare for June 18 Deadline
Pi advocate PiNetwork DEX said he plans to notify node operators to complete upgrades in batches before June 18 to help ensure a smooth transition across the network. Questions surfaced about node participation and network growth. Some community members asked whether the total node count has approached 400,000 and where updated testnet statistics can be viewed. While the Core Team has not commented on those figures, the discussion highlights growing interest in the health and scale of the Pi Network ecosystem.
Upgrade Process Differs by Node Type
For users running Pi Desktop on Windows or macOS, the process is largely automatic. The protocol update will trigger when the node software starts. Linux users operating through the newer Pi Linux Node CLI may not need to take action if auto-updates are enabled. Those without automatic updates must manually run the upgrade command. Operators using legacy self-managed Docker containers will need to update their Docker image and restart services using the latest Protocol 25 release. Pi Network stressed that operators should monitor synchronization status after upgrading to confirm the migration has completed successfully.
Implications for Developers and Community
For developers, Protocol 25 is another sign that Pi Network continues to strengthen its infrastructure ahead of future upgrades. Consistent node participation is critical for network stability, scalability and future ecosystem growth. For community members, the upgrade demonstrates that the project is continuing to execute its technical roadmap. The progress comes at a time when Pi Network remains under pressure from large token unlocks and weak market sentiment. Many holders are closely watching whether ecosystem development can eventually offset the additional supply entering circulation. As June 18 approaches, the focus now shifts to node operators and their ability to complete the Protocol 25 migration on time.
FAQ
What is the deadline for Pi Network's Protocol 25 upgrade?
All mainnet node operators must complete the upgrade to Protocol 25 by June 18 or risk losing connection to the network.
How long will the Protocol 25 upgrade take?
Pi Network said most nodes should experience less than five minutes of downtime during the Protocol 25 upgrade process.
Do all Pi Network node types upgrade the same way?
No. Windows and macOS users running Pi Desktop will see automatic updates. Linux users with auto-updates enabled may not need to take action. Docker container operators must manually update their Docker image and restart services.
