Pi Network confirms Protocol 28 mainnet upgrade after delayed status update

Pi Network confirmed that its mainnet completed an upgrade to Protocol 28 on October 16, resolving uncertainty left by the absence of a completion notice on the scheduled transition date. The network disclosed the completed change on October 22 as part of its Pi Desktop 0.6.4 release, two days before this article’s October 24 publication.

The timing matters because Pi’s official node page continued to describe the protocol transition as being in progress. An independent report published October 24 also noted that the page had retained rollout language after the scheduled event. The newer, dated announcement is the clearest available project record that the mainnet crossed the upgrade boundary, but it is not an independent audit of every node.

What Protocol 28 changes

Pi says Protocol 28 improves how the network handles delays in transaction data. It also introduces tools intended to make smart-contract maintenance easier, including the ability to coordinate updates across groups of contracts and make safer changes to stored application data.

Those capabilities address two distinct operational problems. Delayed transaction information can impede the process by which distributed nodes agree on the next ledger state. Contract fleets present a different maintenance challenge: when many applications share related code, updating each instance separately can leave part of the group running an older implementation during the transition.

The upgrade announcement does not establish how frequently either problem affected Pi before October 16. It also supplies no before-and-after measurements for ledger completion time, transaction throughput, failed transactions, node participation or application reliability. The changes should therefore be treated as new protocol capabilities, not proof of faster or more dependable production performance.

Confirmation came after the event

Pi had required mainnet node operators to install compatible software before the planned October 16 transition. The company’s October 22 post states that the upgrade was successfully completed on October 16, while the separately maintained node page still carried language saying the upgrade was underway when checked for this report.

That inconsistency does not by itself show that the mainnet remained on the earlier protocol. It does show why the event date and disclosure date must remain separate: the network attributes completion to October 16, but the public confirmation available for this article was issued six days later.

The secondary report corroborates that sequence, including the earlier node deadline, the October 16 event date and the October 22 confirmation. It relies on the same project disclosure for completion, however, and does not contribute independent validator telemetry or a reproducible network-version measurement.

What remains unproven

No reviewed source identifies how many nodes had upgraded when Protocol 28 became active, whether any incompatible nodes disconnected, or whether applications have begun using the new contract-maintenance features. Pi also did not disclose an incident, asset loss, token-supply change or application launch tied to the transition.

The next useful evidence would be attributable mainnet version data, post-upgrade operating measurements, or documentation of production applications using the new contract tools. Until then, the defensible conclusion is narrow: Pi Network has declared Protocol 28 complete on mainnet, while the upgrade’s practical effects and network-wide deployment remain unmeasured.