2026-06-22

V25 Node Deadline Has Passed, Our Nodes Are Still on v24—Is This Normal?

The June 18th deadline has passed. According to OrbitWatch observations, the current status is: There have been no upgrade prompts, nor any screens requiring manual intervention, which is a significant difference from previous versions. Previously, running nodes would typically automatically fetch the new protocol's Docker Image and switch to the new protocol version a few days before the deadline. However, so far, no v25 Docker Image has been observed, and nodes are still running on v24. Official Current Statement Let's look at a few timelines together: The deadline has passed, but the official's latest wording is still "in progress," not "completed." This is not inconsistent with our nodes still showing v24. Comparison with Past Upgrades The past three times, the mainnet completed its switch within 3 days after the node deadline. If this time follows the same pattern, we should see results soon—but as of this publication, nothing has been observed yet. What We Are Currently Unsure Of To be honest: We don't know why the nodes haven't switched yet. In previous delays (V23, V24), there were official node upgrade documents for direct verification. This time, no corresponding explanation has been found yet. We are unsure if this is an isolated or widespread phenomenon. The results observed on both testnet2 and mainnet nodes are consistent, but the sample size is limited. We will not invent explanations without sources—this part is currently unknown, and we will supplement it once clearer evidence is found. Background Knowledge: Pi's Consensus Mechanism Pi Network adopts the Stellar Consensus Protocol (SCP), where nodes reach consensus through mutually trusted quorum slices. The protocol version truly changes only after a sufficient proportion of trusted nodes have switched to the new version. This is the technical background for previous upgrades where "nodes moved first, and the mainnet followed a few days later." However, this is just a general explanation of the mechanism, not the specific reason for the V25 delay this time—currently, there are no official documents directly linking the two. OrbitWatch Monitoring Continues Our Horizon API monitoring continues to track the mainnet protocol_version. As soon as an on-chain version switch is observed, or a specific official explanation for this delay is found, an update will be published immediately. Further Reading Confirmation: Pi Network Mainnet Protocol Officially Switched to v24 V24 Node Upgrade Complete, Testnet 2 Switched—Mainnet Still on v23 Data sources: Pi Network Horizon API (api.mainnet.minepi.com), Pi Network Block Explorer, minepi.com/pi-node announcement page, direct observation of Pi Network node screens. All analysis does not constitute investment advice. OrbitWatch is an independent Pi Network ecosystem observatory and is not affiliated with the official Pi Network.

• •The June 18th deadline for the Pi Network v25 node upgrade has passed, but nodes are still observed running on v24, with no upgrade prompts or v25 Docker images.
• •Official communications from the Pi Core Team still state the "protocol upgrade is in progress," which is consistent with nodes remaining on v24 despite the passed deadline.