Upgrade Schedule Updated Again: V24 Deadline Changed to June 2, Full Roadmap at a Glance

This isn't the first time.

Following the V23 deadline extension from May 15 to May 19, the official node upgrade documentation has been quietly updated again—the V24 node deadline has been changed from the original May 25 to June 2, with V25 also shifting accordingly.

As with the last time, there was no official announcement; OrbitWatch observed this change directly from the official node upgrade documentation.

Latest Full Upgrade Schedule

According to the latest information available:

V23   Node Deadline: 5/19  ✓ Completed
      Mainnet Switch: 5/22  ✓ Confirmed (OrbitWatch monitoring)

V24   Node Deadline: 6/2   ← Delayed from 5/25
      Mainnet Switch: To be confirmed

V25   Node Deadline: 6/15  ← Adjusted accordingly
      Mainnet Switch: To be confirmed

V26   Target Completion: 6/22
      Status: Testnet 1 is already running V26

What Does V24 Bring?

Unlike V23's major feature like "smart contracts," V24 is positioned as infrastructure enhancement.

Specifically, it includes: updated Docker images, optimized automatic migration systems, and improved restart capabilities, aiming to minimize downtime and make nodes more stable. It also includes performance enhancements and security strengthening, preparing for a more decentralized node architecture.

Honestly, V24 brings almost no directly noticeable changes for ordinary miners. The significance of this version is to 'make the network's underlying layer more stable,' rather than 'adding new features.'

A Notable Rumor

Recently, rumors have started circulating in the community that "V26 has been canceled."

This is false. Testnet 1 is already running Protocol V26, and the official team has clarified this. V26 has not been canceled and is still progressing as planned.

What Does an 8-Day V24 Delay Mean?

Let's review the historical pattern:

V22: Originally scheduled 4/27, completed on time
V23: Originally scheduled 5/15 → Delayed to 5/19 (Delayed 4 days)
V24: Originally scheduled 5/25 → Delayed to 6/2 (Delayed 8 days)

The number of delayed days is increasing, but this isn't necessarily a bad thing.

The V23 upgrade involved a complete database rewrite, requiring the official team to give node operators more time to complete this complex migration. The V24 delay likely means that the ripple effects of V23 are still being processed, and the official team is choosing to proceed cautiously rather than rush.

This aligns with Dr. Fan's statement at Consensus 2026: Pi Network prioritizes infrastructure stability over short-term speed.

Reminder for Node Operators

V24 Deadline: June 2

If you are running a node, you need to complete the upgrade to v24.1 before June 2.

This upgrade includes optimizations to the automatic migration system, which should theoretically be simpler than V23's database rewrite. However, as always, it's recommended to start a few days in advance and not wait until the last day.

For ordinary miners not running a node: No action is required; continue to await the gradual launch of ecosystem applications.

OrbitWatch's Continuous Monitoring

OrbitWatch's Horizon API monitoring checks the mainnet's protocol_version every 15 minutes.

After the V24 mainnet protocol switch, we will publish a confirmation article immediately, just as we did for V22 and V23.

Currently, the V24 node deadline is June 2, and the mainnet protocol switch is expected to occur within a few days after the deadline.

Further Reading

Data sources: Pi Network official node upgrade documentation (directly tracked by OrbitWatch), MEXC News, coinfomania, hokanews. All analysis does not constitute investment advice. OrbitWatch is an independent Pi Network ecosystem observer and is not affiliated with the official Pi Network team.