Pi Network’s deadline for Mainnet node operators to install Protocol 28 has passed, but the planned network activation is still ahead on 16 October, 2026.
Operators were told to upgrade by 13 October. Pi says Protocol 28 is intended to improve the handling of delayed transaction data and give developers safer ways to upgrade groups of smart contracts and stored application data.
However, Pi has not published an auditable figure showing how many active Mainnet nodes are running version 28. A software download count would not demonstrate that a machine is participating in consensus, and the deadline itself does not confirm that the new protocol has been activated successfully.
Protocol 27 is already live on Mainnet, while Protocol 28 was tested on Testnet before the operator deadline. The planned Mainnet switch will involve the live ledger, transactions and nodes required to maintain consensus. Confirmation should therefore come from a dated Pi announcement, independent ledger observations and evidence that the network continues producing blocks after the change.
What Protocol 28 is expected to change
Pi’s stated improvements concern infrastructure rather than a confirmed new application or immediate increase in usage.
Better management of delayed transaction data could reduce failures when servers have different views of information required to process operations. Grouped contract upgrades could help applications with several connected contracts avoid a period in which different components run incompatible versions. Changes to stored contract data are also intended to make application migrations safer.
Those features do not, by themselves, prove that a Mainnet app is using them. Pi has not published a throughput benchmark, fee reduction percentage or list of production contracts using the new functions. Developers would need to show named applications, contract addresses and reproducible transactions demonstrating successful upgrades and preserved data.
The protocol change also does not automatically launch a stablecoin. Pi’s 8 October statement described work with Open Standard, the group behind OUSD, and said the project would explore rewards and other ecosystem uses. It did not confirm an OUSD launch on Pi or link one to the 16 October activation.
Pi says PI remains the network’s native cryptocurrency. Whether stablecoin-based payments create demand for PI will depend on the eventual design, including fees, incentives, liquidity and any requirement to hold PI.
What happens after activation
A successful switch would show that the scheduled software transition took place and that compatible nodes continued operating. It would not, on its own, establish higher token demand, more merchants, sustained app usage or increased decentralised finance activity.
KYC and migration remain separate access requirements for Pioneers seeking to use Mainnet balances. App discovery, merchant acceptance and useful consumer services are additional factors that Protocol 28 cannot resolve alone.
As of 14 October, the activation remained scheduled rather than completed. No public compliance percentage or identified Mainnet application had shown a before-and-after improvement attributable to Protocol 28.
The key evidence on 16 October will be the live Mainnet protocol version, the distribution of active node versions, uninterrupted ledger production, any failed transactions or emergency patches, and reproducible demonstrations of the new contract tools. A protocol upgrade may improve the network’s foundations, but its effect on users and the PI market will require separate evidence after deployment.
