Protocol upgrade
Track the complete record of all Pi Network protocol upgrades.
Pi Network's Mainnet protocol version does not update automatically, nor is it a single 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 actually observed by OrbitWatch during its tracking from V21 to V27.
Two Phases of the Upgrade Process
Each Pi Network protocol upgrade is divided into two independent phases:
Phase One: Node Software Update The official team announces 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. Completion of the node software update does not mean the Mainnet protocol version has already switched.
Phase Two: Mainnet Protocol Version Switch The Mainnet's protocol_version will only officially switch after a sufficient proportion of nodes have completed their software updates. Pi Network adopts 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 verification, with the Mainnet following closely.
Full Timeline of Past Upgrades
OrbitWatch has tracked the full record of each upgrade since 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 hashing
V26 2026/8/11 2026/8/14 3 days Contract security, state management, interoperability enhancements
V27 2026/9/15 — — Improved Smart Contract Authentication
The three upgrades from V22 to V24 followed a very consistent pattern: the Mainnet switch was completed within 3 days of the node deadline. V26 also continued this rhythm.
V25 is currently the only clear exception. Nearly two weeks after the deadline, node software automatically pulled the v25 container (around 6/27-6/28); the actual switch of the Mainnet protocol version was only completed on the officially announced target date (7/22), a full 34 days after the deadline. The official team explained in a blog post on 7/15 that v25 introduced BN254 encryption and Poseidon hashing, making it a more technically complex upgrade than previous ones.
When the V26 deadline (8/11) was announced, the official team unusually published a separate announcement on X, characterizing V26 as a 'major milestone' and explaining that improvements included contract security, state management, interoperability, and encryption-related capabilities, while also referring to V27 as the 'final planned upgrade'. V26 ultimately completed its Mainnet switch within 3 days of the deadline, returning to the previous normal rhythm.
Before the V27 deadline (9/15) was confirmed, the node side had already taken action: a corresponding release (organization-mainnet-v1.0-p27.1.0) had been published on GitHub, and Testnet 1 had also confirmed its switch to v27. Node documentation initially only provided the deadline without technical details; it wasn't until 8/21 that the official team formally posted within the Pi App, adding specific content: Protocol 27 brings more flexible and secure mechanisms for smart contract authentication, allowing accounts and applications to authorize transactions in more advanced ways, continuing Pi's work to expand smart contract capabilities. The official team also confirmed that the target date for Mainnet upgrade to Protocol 27 is September 15, 2026.
It is 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 documentation each time, rather than through formal announcements.
Planning continues to extend. The node upgrade path currently shows a step from 27.1 → 28.x (i.e., V28), but without any deadline or technical details—this indicates that although V27 was once referred to as the 'final planned upgrade,' the official protocol planning has not stopped there; the specific content of the next round has simply not yet been announced.
Why Do Delays Sometimes Occur?
According to OrbitWatch's observations, there are at least two factors influencing the length of the time gap:
Technical Complexity. V23 introduced full Soroban smart contract support, and V25 introduced BN254 encryption and Poseidon hashing—upgrades involving new protocol-layer capabilities like these require longer verification times than simple infrastructure enhancements (e.g., V24, V26).
Node Readiness Rate. The official team issues reminders after deadlines, indicating that not all nodes complete updates by the deadline. The Mainnet switch requires waiting for a sufficient proportion of nodes to be ready, a proportion that 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 parts.
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 version of the currently running container and confirm if the new image has been pulled.
Updates to the Pi Node software itself (e.g., 0.6.0, 0.6.1, 0.6.2) and protocol version upgrades are two independent matters. The former is a functional update to the node application, while the latter is a switch 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 is 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 will publish an update article immediately after a protocol version switch.
Upgrade Tracking Records for Each Version
| Version | Key Content | Status | OrbitWatch Tracking Article |
|---|---|---|---|
| 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 hashing (foundation for zero-knowledge applications) | ✓ Completed | V25 Upgrade Preview · Deadline Observation · Nodes Ready · Official Announcement 7/22 · V25 Confirmed Switch |
| V25→V26 | Contract security, state management, interoperability enhancements | ✓ Completed | Official Confirms V26: major milestone · Nodes and Testnet2 Ready, Mainnet still v25 · V26 Confirmed Switch |
| V26→V27 | Improved Smart Contract Authentication | Testnet 1 switched, Mainnet target 9/15 | GitHub release and Testnet 1 switch, deadline confirmed 9/15 |
| V27→V28 | To be determined | In planning, no deadline yet | — |
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, Pi Network node upgrade documentation. All analysis does 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 involve two distinct phases: a node software update deadline followed by the actual Mainnet protocol version switch, typically with a gap of several days to weeks.
- •The Mainnet protocol version only officially switches after a sufficient proportion of nodes have completed their software updates, adhering to the Stellar Consensus Protocol (SCP), often signaled by Testnet 2 switching first.
- •Delays in the upgrade process can be attributed to factors like the technical complexity of new protocol-layer capabilities (e.g., V25's advanced cryptography) and the overall node readiness rate across the network.