Key Highlights The Pi Core Team has officially confirmed the successful completion of the Protocol v24 upgrade — calling it one of the most challenging migrations in the network's history. Th
Key Highlights
Pi Network has reached another major infrastructure milestone. The Pi Core Team officially announced today that the Protocol v24 upgrade has been completed successfully — and immediately set the next challenge in motion: all nodes must now reach version 25.2 by June 18, 2026.
The official statement from @PiCoreTeam confirmed:
“Network Update: Upgrade to protocol 24 has been completed successfully. Great job to all Nodes! This was one of the most challenging migrations. Next up will be v25, deadline June 18.”
The acknowledgement that v24 was “one of the most challenging migrations” — following a similar description for v23 — reflects the genuine technical complexity of what Pi’s node operators have been delivering. As we covered in our Protocol 24.1 upgrade guide, the v24 step involved quick internal data migrations with expected downtime under 15 minutes — but coordinating that across a distributed global node network still required significant operational discipline from the operator community.
Pi Node 24 Completed/Source: @PiCoreTeam (X)
Pi Network is upgrading its protocol sequentially from v19 to v26 — with every node required to follow each step in order and wait for network-wide completion before the next step begins. The images above from Pi’s official documentation show the full upgrade path and current status clearly.
Source: Pi Network official upgrade documentation
Completed steps (7 of 9):
Starting from the February 15 completion of the 19.1 → 19.6 migration — through the progressively more complex 22.1 → 23.0 in-place internal database upgrade on May 19 — through today’s confirmed completion of 23.0 → 24.1 on June 2 — the network has now successfully navigated every upgrade step in sequence without a single reversal.
The 22.1 → 23.0 step deserves particular mention in this context. As we detailed in our Protocol 23.0 upgrade article, that migration involved simultaneous upgrades across Protocol 23, Ubuntu 20→24, and PostgreSQL 12→16 — the most complex single upgrade in Pi’s history — and the network completed it successfully before moving into the v24 sequence.
Current active step:
The 23.0 → 24.1 upgrade is now marked as completed as of June 2, 2026 — with the network immediately transitioning to the next phase.
Upcoming steps (2 remaining — locked):
The 24.1 → 25.2 upgrade is now the active target — with a deadline of June 18, 2026. The 25.2 → 26.0 step that follows remains locked with a TBD deadline — and must not be started until officially activated.
Source: Pi Network official upgrade documentation
With v24 complete and the network transitioning to v25, node operators need to act promptly. The June 18 deadline gives approximately 15 days from today — sufficient time for a well-prepared operator but not a timeline that accommodates delays.
Key operational guidance:
Do not upgrade ahead of schedule — The sequential upgrade requirement means starting a step before the Pi Core Team activates it can cause network synchronisation issues. The 25.2 and 26.0 steps are explicitly marked “Do NOT start” until officially enabled.
Do not upgrade all nodes simultaneously — Stagger upgrades across infrastructure and divert traffic away from nodes currently undergoing migration — pointing to other nodes or to https://api.mainnet.minepi.com during the process.
Back up your data before upgrading — Particularly important for steps involving internal data migrations. The v23.0 experience demonstrated the value of having recoverable backups before beginning any complex migration.
Expected downtime for v25 — Based on the pattern of recent quick upgrade steps — expected downtime should be under 15 minutes for most operators. Monitor the official release notes when the v25.2 Docker image is published for confirmed specifications.
Verify completion using the ledger endpoint — Compare ingest_latest_ledger from your node (curl http://localhost:31401) against https://api.mainnet.minepi.com to confirm migration is fully complete rather than relying on node restart alone.
Each completed upgrade step in Pi’s v19-to-v26 sequence is not just a technical checkbox — it is a building block for the ecosystem capabilities that Pioneers and developers are waiting for.
As we covered in our Pi Network OKX US market expansion — where OKX opened Pi access to millions of American users — the network’s infrastructure readiness directly enables the exchange and partnership relationships that expand Pi’s real-world accessibility. As we detailed in our CiDi Games 1.2M sessions launch — the Pi Browser application ecosystem that attracted 81,000 Pioneers in its first week runs on the same Mainnet infrastructure that these protocol upgrades are building and strengthening.
The closer Pi gets to v26 — the fully upgraded production infrastructure state — the more stable and capable the foundation becomes for the dApps, utility tools, and ecosystem partnerships that Pi Network Ventures and the Pi Core Team are building toward.
With 7 of 9 upgrade steps completed and just v25.2 and v26.0 remaining — Pi Network is in the final stretch of its most significant infrastructure transformation since the Mainnet launch.
Protocol v24 is complete. The network has thanked its operators — and immediately handed them the next assignment: version 25.2 by June 18. With 7 consecutive upgrade steps completed successfully — many of them described as among the most challenging in Pi’s history — the node operator community has demonstrated the reliability that a production-grade blockchain requires.
Two steps remain. The finish line for Pi’s v19-to-v26 upgrade journey is visible. Get to v25.2 before June 18 — and wait for the official signal before touching v26.0.
Disclaimer: The views and analysis presented in this article are for informational purposes only and reflect the author’s perspective, not financial advice. Technical patterns and indicators discussed are subject to market volatility and may or may not yield the anticipated results. Investors are advised to exercise caution, conduct independent research, and make decisions aligned with their individual risk tolerance.
