Pi Network has confirmed that its Mainnet completed the Protocol 23 upgrade and is now requiring all Mainnet node operators to move to Protocol 24.1 by June 2, 2026. Nodes that do not complete the update by that date will be disconnected from the network, and no extension has been announced.
Upgrade path must be followed in order
The new release is part of a broader protocol migration across the Pi blockchain. According to the schedule shared by the project, the version path runs through 19.1, 19.6, 19.9, 20.2, 21.2, 22.1, 23.0, 24.1, 25.1, and 26.0. Versions 19 through 23 have already been completed, while 24.1 is now live. Version 25.1 is scheduled for June 15, 2026, with 26.0 set to follow later.
Pi said node operators cannot skip steps in the sequence. The current task is the move from 23.0 to 24.1. The network also warned users not to start upgrading to 25.1 or 26.0 before official notice, saying that jumping ahead could break a node.
Protocol 24.1 is described as a faster update
Compared with the earlier Protocol 23 migration, which involved rewriting database files and carried a risk of data corruption, this round is being presented as a lighter process. Pi said expected downtime is under 15 minutes, there is no major database migration, and no backup is required, though keeping one is still considered prudent.
That makes Protocol 24.1 closer to a routine protocol step than a heavy backend rebuild. For most operators, the time offline should be limited.
Instructions vary by node setup
For users running Pi Desktop on Windows or macOS, no manual action is required. The desktop app updates automatically when opened, and operators only need to launch Pi Node and let it run.
Linux users now have access to the new Pi Linux Node CLI, introduced in 2026. If auto-update is enabled, nothing needs to be done. If it is disabled, users are instructed to run pi-node update-protocol and then monitor the node status. A node is considered ready only when the status reads “Synced” rather than “Syncing.”
Operators still managing nodes manually with Docker on Linux can continue to use that setup, but they must handle the upgrade themselves. Pi also recommends moving to the newer CLI tool.
Missing the deadline may trigger manual recovery work
Pi said a node that misses the June 2 cutoff will drop off the network. Recovery then requires the operator to apply each missed upgrade step in sequence. In the worst case, the node may need to be fully resynced from scratch, which takes more time and effort.
For users operating multiple nodes, the project advised against updating all of them at once. The process may be short, but the deadline is fixed.
Community response remains mixed
Reaction from the community has not been uniform. Some users welcomed the continued protocol work and infrastructure upgrades, viewing them as necessary for the network’s long-term decentralization. Others pointed to unresolved issues, including delays in KYC approvals, limited real-world utility for the token, and weak Pi Coin price performance.
What the project has made clear is narrower and immediate: Protocol 24.1 is live, and Mainnet node operators are expected to complete the upgrade before June 2.