Pi Protocol 28 Is Live, and the Token Barely Moved

Pi Network’s block explorer listed Protocol Version 28 on Mainnet block 29,250,624 at 17:33 UTC on October 16. PI’s high on OKX that day was $0.08195, short of $0.09.

The Core Team had set October 16 as the switch date after an October 13 node deadline. Holders did not have to move coins, reopen the mining app, or change supply. Node operators did. Developers got maintenance tools borrowed from Stellar. Traders treated the same calendar square as a rally cue, and the tape did not follow.

Protocol 28 Is Already on the Ledger

On the morning of October 16, public Horizon reads still showed protocol 27. One check put the latest ledger at 29,238,648 at 04:24 UTC, with Core software already at 28.0.1 and protocol 28 listed only as supported. By 17:33 UTC the explorer had printed Protocol Version 28 on block 29,250,624, with zero failed transactions in that block.

The Node page still told every Mainnet operator to move to v28 and still described the chain as under upgrade. The Core Team did not post a separate “the switch is done” note that afternoon. It posted a November summit instead.

That gap is the whole event. Software on nodes can sit at 28.0.1 while the live protocol field still reads 27. The field that matters is current_protocol_version, and the explorer is the copy anyone can audit.

THE PATH TO PROTOCOL 28

1. May 22, 2026: Protocol 23 hits Mainnet and brings Soroban-style smart contracts onto Pi’s Stellar-based chain.
2. July 22, 2026: Protocol 25 finally switches, 34 days after its node deadline, the long outlier in this year’s rhythm.
3. September 15, 2026: Node deadline for Protocol 27; Mainnet follows around September 22 and is called complete on September 25.
4. September 25, 2026: Testnet is already on Protocol 28. The Core Team sets an October 13 node deadline and an October 16 Mainnet target.
5. October 13, 2026: Operators are told to be on v28 software or lose the connection until they catch up.
6. October 16, 2026: The explorer prints protocol 28 on block 29,250,624 at 17:33 UTC.

Most jumps this year used a three-day gap from node deadline to chain switch. Protocol 27 used about seven. Protocol 25 used 34. Protocol 28 went back to three days on the calendar, even if the protocol field lagged into the afternoon of the target date.

Nine Cents Was the Wrong Scoreboard

OKX has PI’s all-time high at $3.000 on February 27, 2025. At $0.08018, the token is 97.3% below that print, with 11.25 billion coins circulating against a 100 billion max. Market cap on that quote is $902.14 million. None of those figures move because a protocol integer ticked from 27 to 28.

The October 16 session on OKX opened at $0.07960, traded as high as $0.08195, and closed at $0.08066 on $1.37 million of volume. The next session ran between $0.07950 and $0.08119. There was no print at $0.09, and no run at $0.10.

OKX PI TAPE INTO THE SWITCH

October 15 was the messy day, with an OKX low at $0.07400 and the largest volume of the four. Futures open interest, per Blockworks, had already slumped to $8.23 million on October 15 from $49.03 million the week before, an 83.2% drop in notional bets. The upgrade week did not refill that book. It printed a two-cent range under a round number that never traded.

Who Had to Upgrade by October 13?

If PI sits in the mobile app, the protocol change does nothing to balances, mining, or circulating supply. The work sat with operators who keep Mainnet nodes online. The Core Team told them on September 25 to upgrade their nodes to Protocol 28 by October 13, three days before the Mainnet target. Linux operators can run pi-node update-protocol or let auto-update pull a new Docker image. Miss the cutoff and the box drops off consensus until it is patched.

The project has not published a compliance count for how many nodes actually made that date. It has published a size claim for the pool those operators sit in.

THE NETWORK PI CITES FOR BUILDERS

• Engaged users: More than 60 million Engaged Pioneers, the Core Team’s label for the installed base it wants apps to reach.
• KYC’d accounts: Over 18.1 million fully KYC’d users, the slice that can pass identity gates on Mainnet products.
• Nodes: More than 420,000 Nodes, the machines that had to be on v28 software before the chain could switch.
• Mainnet apps: Over 300 Mainnet apps, the catalogue the November summit is supposed to show rather than count.

Those figures come from the same summit post that treats distribution as the pitch to developers. They are not an audit of how many of the 300 apps take payments, how many of the 420,000 nodes vote in consensus, or how many of the 60 million open anything other than the miner. Protocol 28 does not answer those questions. It only changes what a current node is allowed to run.

Stellar’s Adapter, Relabeled for Pi

Pi’s chain is a Stellar fork. Protocol 28 on Stellar is branded Adapter, and the Stellar Development Foundation called it a builder-focused Protocol 28 release. Two of the three changes help people who already ship contracts. The third helps validators keep voting when transaction data is late. Pi’s own September 25 wording tracks that list almost line for line.

Protocol 28 improves how the network handles delays in transaction data and enables developers to upgrade groups of smart contracts at once and change stored data more safely as their applications develop.

Pi Network, official X account, September 25, 2026

The Stellar papers under those sentences are specific. They are not a new virtual machine, a DEX, or a consumer feature in the mining app.

WHAT ADAPTER ACTUALLY ADDS

• CAP-83: Validators can start voting before a full transaction set arrives, and they can drop a late or invalid set instead of stalling. Parallel download of those sets starts off and is meant to turn on later.
• CAP-85: Contracts can point at a shared, updatable code reference so an admin can push atomic upgrades of many contracts at once, the Stellar version of a beacon proxy, instead of patching each copy by hand.
• CAP-86: New “sparse” host functions let a live contract add or drop data fields without the old exact-shape checks rejecting the write, so schema changes stop breaking running apps.

CAP-85 exists because factory-style apps deploy fleets of clones that share one Wasm blob. Updating each clone in a separate transaction leaves a window where some copies run the fix and some still run the bug. The new executable type stores the Wasm hash in one owner contract, keyed by a tag that cannot be deleted and cannot point at missing code. One write moves the whole fleet. That is a gift to a team that already has a fleet. It is idle code for a chain whose public DEX is still a rumour.

Smart contracts on Pi did not arrive with 28. Protocol 23 on May 22 turned that layer on. Versions 26 and 27 hardened auth, state, and contract safety. 28 is the maintenance release after that sequence, which is why a holder who only watches the miner sees nothing.

A Live Protocol Is Not a Live DEX

A protocol integer can move while the product people actually want stays dark. After the October 16 switch, operators reading public APIs said the Soroban contract execution endpoint was still closed and that PiDEX deployment had not started. Those reads are not a Core Team notice. They match the shape of the release: Adapter makes fleets easier to patch once contracts are running. It does not, by itself, open an execution endpoint the Core Team has kept shut.

That is also why some posts treated Protocol 28 as the day Pi became a smart-contract chain. It was not. The engine has been on the ledger since Protocol 23. What 28 adds is a safer way to upgrade a fleet and a cleaner way to migrate stored fields, plus a consensus path that does not freeze when a transaction set is late. Calling that a consumer launch is how you get a $0.08195 high on a “catalyst” day.

Replies under the Core Team’s own summit post made the same point in plainer language. People did not ask for another three-day stream. They asked for a working DEX. A smaller set cheered the builder framing. The split is not mysterious. One camp is pricing listings and order books. The other is pricing SDKs, App Studio imports, and SoloHost. Protocol 28 feeds the second camp. It does not fill an order book.

What November 17 Has to Prove

On October 16 the Core Team announced the first Pi Ecosystem Summit, a three-day online event in November running November 17 to 19. Pi Day and Pi2Day stay as community dates. This one is aimed at developers, tools, and apps. Hackathon rules are due during the stream, not before it.

Pi Network is introducing the first-ever Pi Ecosystem Summit, a three-day online event on November 17–19, 2026!

While Pi Day and Pi2Day celebrate progress across the broader Pioneer community and network, the Pi Ecosystem Summit will focus on developers, the Pi platform, and… pic.twitter.com/UzdvYAxlxY

— Pi Network (@PiCoreTeam) October 16, 2026

The blog post attached to that notice is the pitch: AI makes it cheaper to write software, so the scarce thing is distribution, and Pi says it already has users, login, payments, and discovery. Recent 2026 tool work named in that post includes bringing outside AI apps into Pi App Studio, SoloHost for self-hosted AI apps, more SDK functions, and thicker docs. The summit is supposed to add platform releases, live tool demos, partner and community showcases, and a talk track with the Core Team.

WHAT THE SUMMIT SAYS IT WILL SHOW

• Platform releases: New features, capabilities, and resources for people building on Pi.
• Demos: Practical walks through specific tools, not slideware about a roadmap.
• App showcases: Work from companies and community developers, with some account of how they use Pi.
• Hackathon: An all-new contest whose structure, prizes, and rules are still unstated.

Thirty-two days separate the October 16 ledger print from the first summit session. That is the window in which CAP-85 and CAP-86 either show up in a real app’s upgrade path or sit as unused host functions. A demo that only restates App Studio and SoloHost will not settle whether grouped contract upgrades matter. A live app that rotates a fleet in one write would. So would an honest note that the contract execution endpoint is still closed.

Protocol 28 is now an integer on block 29,250,624. PI’s OKX high on the target date was $0.08195. The next dated event on the Core Team’s calendar is November 17, and the thing that still is not on that calendar is a DEX.

Disclaimer: This article is news reporting and analysis of a blockchain protocol change and a listed token. It is informational only and is not investment advice, trading advice, or a recommendation to buy, sell, or hold PI or any other digital asset. Cryptocurrency prices, protocol status, and app availability can change without notice, and past prints such as the $3.000 all-time high are not a guide to future results. Readers should consult a qualified financial adviser and, where node operation is involved, a technically competent operator before acting on any figure or date in this piece. Figures here reflect the cited exchange tape, explorer page, and project posts as dated in the article and may already have moved.