Official Node Document Update: V26 Deadline Set for August 11, V27 Appears for the First Time in Upgrade Path

OrbitWatch today observed two updates directly from the official node upgrade document: the V26 node deadline has been set for August 11, and V27 has appeared for the first time in the upgrade path, with its deadline currently TBD.

There was no formal announcement; this was a direct update to the document content.

Current Status of Official Node Document

25.2 → 26.1   ➡️ Upgrade in progress   Deadline: 8/11/2026
26.1 → 27.0   🚫 Not yet started    Deadline: TBD

The document also added a clear reminder:

⚠️ Do not begin any upgrade before it is officially announced as active.

Full Upgrade Path and History

The full upgrade path currently listed in the official document:

19.1 → 19.6 → 19.9 → 20.2 → 21.2 → 22.1 → 23.0 → 24.1 → 25.2 → 26.1 → 27.0

Overview of each version's deadline:

Version          Deadline       Status
19.1 → 19.6  2026/2/15   ✅ Completed
19.6 → 19.9  2026/3/1    ✅ Completed
19.9 → 20.2  2026/3/12   ✅ Completed
20.2 → 21.2  2026/4/6    ✅ Completed
21.2 → 22.1  2026/4/27   ✅ Completed
22.1 → 23.0  2026/5/19   ✅ Completed
23.0 → 24.1  2026/6/2    ✅ Completed
24.1 → 25.2  2026/6/18   ✅ Completed
25.2 → 26.1  2026/8/11   ➡️ In progress
26.1 → 27.0  TBD         🚫 Not yet started

Several Noteworthy Details

V26 upgrade difficulty is the same as V25. The document states this is "a very quick upgrade, with fast internal data migration, and expected downtime of no more than 5 minutes" — identical to the V25 description, unlike the V23 upgrade which required a full database rewrite.
V27 appears for the first time, but with no details. The document only shows "26.1 → 27.0, TBD, TBD," without any functional description or estimated timeline. This is the first appearance of V27 in the upgrade path, indicating that the core team has included it in their plans, but no specific details are available yet.

Comparison with V25 Time Lag

V25  Node deadline 6/18 → Mainnet switch 7/22 (34-day difference)
V26  Node deadline 8/11 → Mainnet switch ?

V25 had the largest time lag to date. The V26 document indicates low upgrade difficulty, so if all goes as expected, the mainnet switch should be faster than V25 — but this is merely an inference based on past patterns, not a certainty.

OrbitWatch Monitoring Continues

We will continue to track changes in the official node document, as well as the actual status of nodes and mainnet around the August 11 deadline. We will also monitor whether the core team addresses the version number inconsistency observed in the V26.1 document description.

Further Reading

Data Source: Pi Network Official Node Upgrade Document (docs.google.com, directly observed by OrbitWatch on 2026/7/29). 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.