V24 Node Upgrade Completed, Testnet 2 Switched – Mainnet Still on v23, Is This Normal?
June 3, 2026 at 06:27 AM
The June 2nd deadline has passed.
According to OrbitWatch's observations, the current status is:
Node software version: v24 ✓ Completed (deadline 6/2)
Testnet 2 protocol: v24 ✓ Switched
Mainnet protocol: v23 ⏳ Not yet switched
If this looks familiar, you're not mistaken—this is exactly the same situation as with V22 and V23.
This is Normal, and There's a Pattern
Looking back at the pattern of the past two upgrades:
V22 Node deadline 4/27 → Mainnet switch 4/30 (3-day difference)
V23 Node deadline 5/19 → Mainnet switch 5/22 (3-day difference)
V24 Node deadline 6/2 → Mainnet switch ? (in progress)
Each time, the Mainnet officially switches a few days after the node deadline. This is by design of the Stellar Consensus Protocol (SCP)—after nodes are upgraded, a sufficient proportion of nodes need to run the new software before the protocol version can be switched together via the consensus mechanism.
Testnet 2 has already switched to v24, which is consistent with the situation during V23. The testnet switching first is a signal of successful technical validation; the Mainnet switch is only a matter of time and is expected to happen within the next few days.
What Does V24 Bring?
V24 is positioned as an infrastructure enhancement, not a new feature.
Specifically, it includes: updated Docker images, an optimized automatic migration system, and improved restart capabilities, aiming for more stable nodes and shorter downtime. It also includes performance enhancements and security hardening, preparing for a more decentralized node architecture.
For ordinary miners, V24 brings almost no directly noticeable changes. It serves as the foundation for V25 and V26 to proceed smoothly.
Upcoming Upgrade Schedule
V24 Target completion: 6/2 ✓ Completed
Mainnet switch: In progress
V25 Target completion: 6/15
Mainnet switch: To be confirmed
V26 Target completion: Not yet confirmed
Status: Testnet 1 is already running V26
V25's target completion is June 15th, which is 12 days from now. If you are running a node, you can observe whether it will auto-upgrade or if any action is required soon.
OrbitWatch's Monitoring Commitment
Our Horizon API monitoring checks the Mainnet's protocol_version every 15 minutes.
Once the Mainnet switches from v23 to v24, we will publish a confirmation article immediately, just as we did for V22 and V23. You won't need to constantly refresh Block Explorer or community groups.
Further Reading
- V23 Mainnet Protocol Switch Confirmed
- Upgrade Schedule Update: V24 Deadline Changed to June 2nd
- V23 Testnet Switched, Mainnet Still on v22—Is This Normal?
Data sources: Pi Network Horizon API (api.mainnet.minepi.com), Pi Network Block Explorer, 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.
Key Points
- •The V24 node upgrade and Testnet 2 switch are complete, but the Mainnet remains on v23, following a pattern seen in previous upgrades.
- •This delay is normal, as the Mainnet typically switches a few days after the node deadline to allow a sufficient proportion of nodes to adopt the new protocol.
- •V24 is an infrastructure enhancement focused on node stability, performance, and security, preparing for future decentralized architecture, with no direct changes for ordinary miners.