Pi Network has scheduled the mainnet node upgrade for June 2, 2026. The core team requires all mainnet node operators to complete the Protocol 24.1 update by the deadline; otherwise, they will be unable to continue connecting to the Pi Mainnet.
This update follows Protocol 23. Unlike the new features that have garnered more attention, Protocol 24.1 primarily focuses on underlying operational efficiency, with an emphasis on preparing for future smart contracts and broader ecosystem expansion.
The focus of the update has shifted to underlying optimization.
According to the Pi Core Team, Protocol 24.1 mainly involves four aspects: improving ledger processing efficiency, improving node synchronization, preparing backend infrastructure for future smart contracts, and making subsequent network upgrades smoother.
Based on the disclosed information, this update does not primarily focus on changes to front-end functionality, but rather on further improving the mainnet's operational requirements. For node operators, the most direct impact is the necessity to complete upgrades on time to maintain online status.
The upgrade process is simpler than last time.
The Pi team stated that this migration was less difficult than that of Protocol 23. Previous version upgrades involved large-scale database adjustments, while the migration to Protocol 24.1 is expected to be faster.
- Most migrations are expected to be completed within 5 minutes.
- Windows nodes can be automatically updated via Pi Desktop.
- Linux operators can use the new Pi Linux Node CLI tool.
For Docker users, the team states that simply deploying the updated container version is sufficient. Meanwhile, the official recommendation is that operators avoid upgrading all nodes simultaneously, instead distributing traffic through backup nodes or the official Pi API to minimize the risk of interruptions during the upgrade process.
The community is paying attention to the next phase of progress.
Although Protocol 24.1 is primarily an infrastructure update, community discussions have already shifted to the more recent Protocol 26. Some users believe that subsequent versions may be more related to smart contract capabilities and the pace of ecosystem expansion.
However, the Pi team has made it clear that blockchain protocol upgrades and ecosystem product launches are not on the same timeline. The delays surrounding PiDex and smart contracts do not mean they will be released alongside Protocol 24.1. The current focus remains on improving network stability before paving the way for larger-scale product expansion.
With June 2nd approaching, this upgrade will become a new juncture for observing the Pi mainnet's readiness for operation.
