← Back to list
OrbitWatch Editorial★★★★▲

V27 Official Deadline Confirmed: September 15th, Node Files Updated, Testnet 1 Switched, but Official Schedule Not Yet Public

Published August 21, 2026 at 07:08 AM

The official node upgrade documentation has been updated, confirming the official deadline for V27 as September 15, 2026.

GitHub release：organization-mainnet-v1.0-p27.1.0  ✓ Released
Testnet 1 protocol_version：27                      ✓ Switched (OrbitWatch verified)
Your node (mainnet)：v26                             ⏳ Not yet pulled v27
Official node deadline：2026/09/15 (Node documentation updated)

This is the final step in the entire V19→V27 upgrade sequence. When the official announcement was made on July 29-30, V27 was characterized as the "final planned upgrade".

Technical Details in the GitHub Release

organization-mainnet-v1.0-p27.1.0 was released by pierre275, and the changes recorded in the release notes are as follows:

Component version updates:
  stellar-core: v26.1.0 → v27.1.0
  horizon:      v26.0.0 → v27.0.0
 
Expected downtime:
  Only swapping stellar-core and horizon executables,
  No database migration or schema changes required,
  Expected to complete within 5 minutes (may take longer in rare cases)
 
Changes:
  CORE_REF upgraded from v26.1.0 to v27.1.0
  HORIZON_REF upgraded from v26.0.0 to v27.0.0
  Build environment (ubuntu:24.04, clang-20 / libc++-20) remains unchanged,
  Official text states: "v27 has the same C++20 requirement as v26"

Notably, the amount of changes recorded in these release notes is less than for V26. The V26 upgrade included underlying adjustments like upgrading the build environment from Ubuntu 20.04 to 24.04 and the compiler toolchain from clang-12 to clang-20; V27, this time, is almost entirely a version number increment, with no changes to the toolchain or build environment.

Testnet 1 Confirmed Switched

OrbitWatch queried Testnet 1's Horizon API and confirmed that protocol_version is now 27. This is the first network in this upgrade sequence confirmed to have switched to v27.

Comparing with Previous Upgrade Rhythms

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 6/5 (3-day difference)
V25  Node Deadline 6/18   → Mainnet Switch 7/22 (34-day difference)
V26  Node Deadline 8/11   → Mainnet Switch 8/14 (3-day difference)
V27  Node Deadline 9/15   → Mainnet Switch ?

The V27 node deadline is currently confirmed as September 15th, but the GitHub release and Testnet 1 have already moved ahead of the official announcement—this aligns with the pattern seen in V25 and V26, where node-side actions preceded official announcements. Based on the release notes (only swapping executables, no database migration), this upgrade is of low complexity. If it follows the rhythm of V22-V24 and V26, the mainnet switch should occur within 3 days after the deadline.

This announcement contains significantly less information compared to V26. When the V26 deadline was announced, the official team posted a separate update on X, explicitly characterizing it as a "major milestone" and detailing the areas of improvement (contract security, state management, interoperability, encryption). For V27, as of this writing, OrbitWatch has not found any official statements accompanying the deadline announcement—no new qualitative descriptions, nor any content specifying what this upgrade addresses. All third-party reports currently available still cite the old official wording from July 29-30 ("final planned upgrade"), not new content specific to this deadline announcement.

OrbitWatch's Continued Tracking

We will continue to monitor the mainnet node-side activities around the September 15th deadline, as well as whether the mainnet protocol_version switches to 27.

Further Reading

Data sources: GitHub PiCoreTeam/pi-node-docker releases (direct observation), Pi Testnet 1 Horizon API (direct query). All analysis does not constitute investment advice.

Key Points

  • •The official deadline for Pi Network's V27 node upgrade is confirmed as September 15, 2026.
  • •The V27 GitHub release is live, and Testnet 1 has already switched to protocol version 27, preceding a formal announcement.
  • •This upgrade is a low-complexity version increment, marked as the "final planned upgrade" in the V19-V27 sequence, though official details on its specific improvements are scarce.