Pi Network Protocol Upgrade Mechanism: From Node Deadline to Mainnet Switch
July 28, 2026
Pi Network's mainnet protocol version does not update automatically, nor is it a one-time operation. Each upgrade follows a fixed process: first, a deadline for node software updates, followed by the actual switch of the mainnet's on-chain protocol version. There is usually a gap of several days to several weeks between these two events.
This page compiles the upgrade patterns and mechanisms observed by OrbitWatch during its tracking from V21 to V25.
Two Phases of the Upgrade Process
Each Pi Network protocol upgrade is divided into two independent phases:
Phase One: Node Software Update The official announcement sets a node deadline, requiring all node operators to complete software updates within the specified period. For nodes using Pi Desktop (Windows/macOS), this process is automatic—the software automatically pulls the new Docker image and switches to running the new container. The completion of the node software update does not mean the mainnet protocol version has switched.
Phase Two: Mainnet Protocol Version Switch
The mainnet's protocol_version officially switches only after a sufficient proportion of nodes have completed their software updates. Pi Network uses the Stellar Consensus Protocol (SCP), where nodes reach consensus through mutually trusted quorum slices—this mechanism dictates that the protocol version cannot be forcibly switched by a single node; the entire network needs to be ready.
The usual observed sequence is:
Node Deadline
↓ (several days later)
Testnet 2 switches to the new version first
↓ (several more days later)
Mainnet protocol_version officially switches
Testnet 2 switching first is a signal of successful technical validation, with the mainnet following shortly after.
Complete Timeline of Past Upgrades
OrbitWatch has tracked the complete record of each upgrade starting from V21:
Version Node Deadline Mainnet Switch Date Gap Key Content
V21 — 2026/4/29 — Infrastructure (before OrbitWatch launch)
V22 2026/4/27 2026/4/30 3 days PiRC1 framework effective
V23 2026/5/19 2026/5/22 3 days Full Soroban smart contract support
V24 2026/6/2 2026/6/5 3 days Automated migration system optimization, node stability
V25 2026/6/18 2026/7/22 34 days BN254 encryption, Poseidon hash
V26 TBD — — To be determined
The three upgrades from V22 to V24 followed a very consistent pattern: the mainnet completed its switch within 3 days of the node deadline.
V25 was a clear exception. Nearly two weeks after the deadline, the node software automatically pulled the v25 container (around 6/27-6/28); the actual switch of the mainnet protocol version was completed on the officially announced date (7/22), a full 34 days after the deadline. The official blog on 7/15 explained that v25 introduced BN254 encryption and Poseidon hash, making it a technically more complex upgrade than previous ones.
It's also worth noting that the V24 node deadline was postponed twice: originally scheduled for 5/25 → 5/31 → finally set for 6/2. Deadline adjustments are not uncommon in Pi's upgrade process, and OrbitWatch observed these changes directly from official node upgrade documents each time, rather than through formal announcements.
Why Do Upgrades Sometimes Take Longer?
According to OrbitWatch's observations, at least two factors influence the length of the time gap:
Technical Complexity. V23 introduced full Soroban smart contract support, and V25 introduced BN254 encryption and Poseidon hash—upgrades involving new protocol-level capabilities like these require more validation time than simple infrastructure enhancements (e.g., V24).
Node Readiness Rate. The official team issues reminders after the deadline, indicating that not all nodes complete updates by the deadline. The mainnet switch requires waiting for a sufficient proportion of nodes to be ready, though this proportion has not been officially disclosed.
Important Premise: The above are possible reasons inferred from observations; the official team has not provided specific technical explanations for any delays. OrbitWatch refrains from further speculation on uncertain aspects.
What Do Node Operators Need to Do?
For node operators using Pi Desktop (Windows/macOS): Software updates are usually automatic and do not require manual intervention. You can use the docker images command to check the currently running container version and confirm if the new image has been pulled.
Updates to the Pi Node software itself (e.g., 0.6.0, 0.6.1) are separate from protocol version upgrades. The former are functional updates to the node application, while the latter are switches of the on-chain protocol version; they do not interfere with each other.
How to Confirm the Current Mainnet Protocol Version?
The most direct way is to query the Horizon API:
https://api.mainnet.minepi.com/ledgers?order=desc&limit=1
The protocol_version field in the returned result indicates the current protocol version running on the mainnet.
You can also check directly on the Pi Network Block Explorer: 👉 blockexplorer.minepi.com
OrbitWatch's Horizon API monitor automatically checks every 15 minutes and publishes an update article immediately after a protocol version switch.
Upgrade Tracking Record for Each Version
| Version | Key Content | Status | OrbitWatch Tracking Articles |
|---|---|---|---|
| V21→V22 | PiRC1 framework effective | ✓ Completed | Nodes running v22, but chain still v21 · V22 Confirmed Switch |
| V22→V23 | Full Soroban smart contract support | ✓ Completed | V23 Deadline Update · Testnet 2 Switched · V23 Confirmed Switch |
| V23→V24 | Automated migration system optimization, node stability | ✓ Completed | V24 Deadline Update · Testnet 2 Switched · V24 Confirmed Switch |
| V24→V25 | BN254 encryption, Poseidon hash (basis for zero-knowledge applications) | ✓ Completed | V25 Upgrade Announcement · Deadline Observation · Nodes Ready · Official Announcement 7/22 · V25 Confirmed Switch |
| V25→V26 | To be determined | Deadline TBD | — |
Data sources: Pi Network Horizon API (api.mainnet.minepi.com), Pi Network Block Explorer, direct observation of Pi Network node interface, Pi Network official announcements. All analyses do not constitute investment advice. OrbitWatch is an independent Pi Network ecosystem observatory and is not affiliated with the official Pi Network team.
Key Points
- •Pi Network protocol upgrades occur in two distinct phases: a node software update deadline, followed by the mainnet protocol version switch, often with a gap of days to weeks.
- •The duration of this gap can vary due to technical complexity (e.g., V25's BN254 encryption) and the overall node readiness rate across the network.
- •Node operators using Pi Desktop typically experience automatic software updates, and the current mainnet protocol version can be verified via the Horizon API or Pi Network Block Explorer.