Confirmation: Pi Network Mainnet Protocol Switched to v28

OrbitWatch's Horizon API monitoring detected:

The Mainnet protocol_version has officially switched to 28.

You can verify this directly on the Block Explorer: 👉 blockexplorer.minepi.com

When Did the Switch Occur?

Last ledger confirmed as v27    29242078
                            closed_at: 2026-10-16 09:22:07 UTC
Earliest ledger confirmed as v28    29252197
                            (OrbitWatch's last record for 10/16)

The switch occurred between these two ledgers, specifically on October 16 (UTC), aligning with the official target date for the Mainnet on October 16. OrbitWatch's monitoring detected the change during its next check on October 17.

Full Timeline of This Upgrade

9/25    Official announcement of V27 completion, Testnet upgraded to V28, and V28 schedule released
10/13   Official Node deadline
10/16   Mainnet protocol_version officially switched to v28 ✓

Compared to previous upgrades:

V22  Node deadline 4/27   → Mainnet switch 4/30 (3 days difference)
V23  Node deadline 5/19   → Mainnet switch 5/22 (3 days difference)
V24  Node deadline 6/2    → Mainnet switch 6/5 (3 days difference)
V25  Node deadline 6/18   → Mainnet switch 7/22 (34 days difference)
V26  Node deadline 8/11   → Mainnet switch 8/14 (3 days difference)
V27  Node deadline 9/15   → Mainnet switch 9/22 (7 days difference)
V28  Node deadline 10/13  → Mainnet switch 10/16 (3 days difference)

V28 was completed on time on the officially scheduled date of October 16, with only 3 days between the Node deadline and the Mainnet switch, returning to the rhythm of V22–V24 and V26.

What Does v28 Bring?

The official announcement on September 25 explained that Protocol 28 improves how the network handles transaction data latency and allows developers to upgrade an entire set of smart contracts at once, enabling safer changes to stored data during application evolution.

OrbitWatch's Observations

Since V23, official explanations for all upgrades (V23, V26, V27, V28) have revolved around smart contract capabilities. However, during OrbitWatch's most recent compilation, the official response on Developer Discord stated that smart contract functionality is not yet finalized and is currently for internal use only (see Smart Contract Status Analysis for details). The continuous expansion of protocol-level capabilities and when third-party developers can actually use them remain two separate matters.

The official preview for the Pi Ecosystem Summit on November 17–19 announced new platform and feature announcements, which will be the next opportunity to observe if there's any progress on this matter.

OrbitWatch's Follow-up

We will continue to monitor whether the official team provides further technical details on V28, as well as the actual agenda and announcements from the Ecosystem Summit.

Further Reading

Data sources: Pi Network Horizon API (api.mainnet.minepi.com), Pi Network Block Explorer, @PiCoreTeam official X account (9/25 announcement). All analyses do not constitute investment advice. OrbitWatch is an independent Pi Network ecosystem observatory and is not affiliated with the official Pi Network team.