TLDR
- Pi Mainnet operators must complete Protocol 25 upgrades before June 18 to maintain node connectivity.
- The upgrade applies to all Mainnet nodes, including systems operated from laptops and desktops worldwide.
- Pi Nodes use Stellar Consensus Protocol principles rather than proof-of-work validation models used elsewhere globally.
- Node operators may need extra preparation time because the Protocol 25 upgrade takes longer overall.
- Pi’s desktop node software supports app access, blockchain setup, and different participation levels for users.
Pi Mainnet has set June 18 as the deadline for all Mainnet node operators to complete the Protocol 25 upgrade, with the network notice stating that nodes must finish the required step before the cutoff to remain connected to the blockchain.
The update applies across the active node layer, which is operated on laptops and desktop computers, and operators have been advised to plan ahead because the upgrade process takes longer than routine maintenance. The requirement comes as Pi Network continues to position nodes as a core role in its blockchain structure, separate from mobile mining and app-based participation.
In the Pi ecosystem, nodes are intended to support transaction validation, ledger verification, and network availability by helping the distributed system maintain an agreed order of records, while the broader design continues to rely on user participation through devices that are more accessible than specialized mining hardware.
Protocol 25 Upgrade Requirement
Unlike Bitcoin-style proof-of-work systems, Pi’s node framework is based on the Stellar Consensus Protocol model, in which agreement is formed through trusted groups known as quorum slices. Under that model, nodes do not compete through energy-intensive mining, but instead work toward consensus by relying on trusted relationships that shape how transactions are accepted and recorded on the shared ledger.
Pi’s broader trust model also draws from security circles created by mobile users, which are designed to contribute to a global trust graph used by the network to support quorum formation.
The project has described this structure as part of its approach to building a distributed currency system around user networks, although node availability, software readiness, and operator reliability remain practical requirements for maintaining connection during upgrade periods.
Node Roles And Consensus Design
The Pi Node software includes a desktop Pi App interface and a node interface, giving Pioneers different levels of participation based on technical readiness and selection status. The desktop app interface allows users to access functions similar to the mobile application, including balance checks, media content, and Pi chats, while the node interface supports installation and operation of the blockchain component for users who apply to run nodes.
Within the participation structure, the Computer App level is intended for users who want desktop access without operating the blockchain component, while the Node level allows selected users to make their computer available for ledger verification and transaction submission.
SuperNodes carry broader responsibilities, including helping reach consensus, keeping other nodes updated with the blockchain state, and maintaining reliable network availability for extended periods.
Operator Readiness Before June 18
The June 18 Protocol 25 deadline places immediate operational focus on Mainnet node operators, because failure to complete the required upgrade before the cutoff could leave a node disconnected from the network.
The notice says all Mainnet nodes are required to complete the step, meaning operators need to account for installation time, device availability, connectivity, and any local setup issues before the deadline arrives.
The upgrade also reflects Pi Network’s movement from earlier testing stages toward a complete Mainnet environment, where node software, consensus participation, and user-operated infrastructure must remain aligned with protocol requirements.
While the network has previously described progressive decentralization as part of its development method, the Protocol 25 requirement is a practical reminder that node operators must keep software current when protocol changes are introduced.





