Key Takeaways:
Pi Network mandated that all Mainnet node operators complete the Protocol 25 upgrade by June 18, 2026, or risk losing connection to the network, the Pi Core Team announced on June 9.
"The Pi Mainnet is upgrading to Protocol 25. All Mainnet nodes are required to complete this step before the deadline to remain connected to the network," the Pi Core Team said in a post on X. "This upgrade takes longer to complete. Plan accordingly."
The upgrade moves nodes from Protocol 24.1 to version 25.2, continuing Pi Network's sequential migration path that began with Protocol 19.6 in February. Protocol 24, which the team described as "among the most complex" upgrades to date, faced delays beyond its initial May 15 target due to subsystem enhancements and internal data reprocessing requirements. It went live in early June.
Protocol 25 is designed for minimal disruption — most nodes should experience less than five minutes of downtime during the migration, according to the team. Operators were advised against upgrading all nodes simultaneously and instead to redirect traffic to other nodes or use Pi's mainnet API infrastructure during the transition. The upgrade process varies by setup: Pi Desktop users on Windows or macOS will see the update trigger automatically on startup, while Linux Node CLI users with auto-updates enabled may not need to take action. Operators using self-managed Docker containers must pull the updated stellar-core image and restart services manually.
The mandatory upgrade arrives as Pi Network expands its ecosystem beyond infrastructure. The Pi App Studio has onboarded roughly 470 decentralized applications, driving stronger network traffic that triggered temporary access queues for Pioneers. The native token faces pressure from upcoming unlocks and weak market sentiment, with holders watching whether ecosystem development can offset additional supply entering circulation.
For node operators, the June 18 deadline represents the next critical checkpoint in Pi's progressive decentralization roadmap. The Core Team has signaled that Protocol 26 will follow at a later date, maintaining the phased approach toward improved scalability, stability, and broader network participation. Failure to complete the migration on time means disconnection from the mainnet — a risk that could reduce node count and temporarily affect network resilience.
This article is for informational purposes only and does not constitute investment advice.
