Pi Network Awaits Oct. 16 Protocol 28 Activation After Node Upgrade Deadline

Deadline passed, activation still pending

Pi’s schedule separates the operator upgrade window from the actual rule change on Mainnet. Oct. 13 was the date for participating node operators to install compatible software, while Oct. 16 is the planned date for the Mainnet protocol change itself.

That distinction matters because a missed operator deadline is not the same thing as a failed network upgrade. The final outcome depends on validator participation and on how the network handles servers that remain on incompatible versions. Pi previously said Protocol 27 had been upgraded successfully on Mainnet before Protocol 28 moved through Testnet, but a Testnet run does not confirm live deployment on the production ledger.

No public compliance figure for active Mainnet validators

At the time the source report was prepared, Pi’s public node page did not provide a dated, auditable breakdown showing what share of active Mainnet validators were running v28. Without that data, there is no solid basis for claiming a specific level of compliance ahead of activation.

A download count would not answer the question, because operators can obtain software without actually running it in consensus. More useful evidence would include version distribution among active nodes, any upgrade vote or activation status, and confirmation that ledger production continues normally after the switch.

This also matters for ordinary participants, not only developers. Nodes that stay on an older protocol can lose sync once new transaction rules take effect, though the scale of any disruption would have to be observed after activation rather than assumed in advance.

What Protocol 28 is supposed to add

Pi says Protocol 28 is designed to improve handling of delayed transaction data, support grouped smart contract upgrades and make contract state changes safer as applications evolve. Those are technical capabilities, not proof of immediate increases in usage or performance.

The announcement did not include a throughput benchmark, a quantified fee reduction or a list of production contracts already using the new functions. For that reason, treating the release as an automatic boost to transactions per second or app activity would go beyond the available evidence.

The claimed contract features are also limited in scope. Coordinated upgrades can help applications built from several dependent contracts avoid version mismatches during updates, while safer state changes can help preserve balances, permissions and other stored records when code changes. Even so, developers still need to test their logic and migration paths, and protocol support does not amount to a security audit of any individual app.

Technical progress is separate from adoption

The source article notes that Protocol 28 continues an existing development path rather than introducing smart contracts for the first time. Its impact therefore needs to be judged against Protocol 27 and other earlier tooling, not against a hypothetical network with no developer capabilities at all.

A stronger case for adoption would require visible Mainnet evidence such as named apps, reproducible contract addresses, transactions invoking the new features, and some indication of real usage. Even then, raw wallet counts or transfer values would need careful interpretation, since a single actor can control many wallets and activity can be concentrated in one application or among related accounts.

The broader 2026 roadmap also includes other constraints that a protocol upgrade alone does not solve. KYC and migration affect who can use Mainnet balances, app discovery affects whether users can find services, and merchant or consumer utility affects whether people have a reason to spend.

What to watch on and after Oct. 16

Pi’s separate Oct. 8 statement about working with Open Standard, the group behind OUSD, should not be treated as part of the Oct. 16 protocol switch. The company said it would explore rewards and ecosystem uses, but it did not provide a confirmed OUSD launch date on Pi or say that Protocol 28 activation would make such a product available immediately.

The next confirmed step is the planned Mainnet activation on Oct. 16. After that, the most meaningful signs of success would be independent confirmation that the new protocol is live, evidence of version uptake among active validators, uninterrupted ledger production and developer transactions that demonstrate the new contract upgrade and state-handling features in practice.