Pi Network’s 421,000 Nodes Keep Marching Past Protocol 23

Pi Network’s 421,000 active mainnet nodes were the May headline. Protocol 23, sold as the smart-contract switch, actually flipped on May 22, 2026, after the Core Team moved a disconnect deadline from May 15 to May 19.

Four months later the same node army is being told to install Protocol 27. Pi’s own node page says the mainnet is under upgrade, desktop software sits at version 0.6.3, and the date the Core Team named is September 15, 2026.

When Did Protocol 23 Go Live on Pi?

The public ledger first carried protocol 23 on May 22, 2026, at 12:11:18 UTC, on ledger 26,805,815, after the node deadline moved from May 15 to May 19. That is the date that matters, not the original cutoff and not the press copy that treated the upgrade as already live a week earlier.

On May 8, the official Pi Network account told operators the clock was already running. “All Mainnet nodes are required to complete the Protocol 23 upgrade by May 15, 2026 to remain connected to the network,” @PiCoreTeam wrote, adding that the job takes longer than earlier updates, so operators should plan ahead.

THE PROTOCOL 23 CLOCK

1. May 8, 2026: Core Team warns every Mainnet node to finish Protocol 23 by May 15 or lose the connection.
2. May 15, 2026: Original deadline slips four days to May 19 after a revised 23.0 build aimed at database performance after migration.
3. May 19, 2026: Extended cutoff. Nodes still on older software risk being dropped from the network.
4. May 20, 2026: Core Team says most major nodes have moved to v23 and the protocol should follow soon.
5. May 22, 2026: First mainnet ledger on protocol 23 is 26,805,815 at 12:11:18 UTC.

The May 15 date was never a ceremonial launch. It was a threat to cut machines that had not installed the new stack. the 421,000-node count in May arrived in that same week, and later upgrade notices kept recycling it as if it were a fresh census.

Only SuperNodes Sit in Consensus

Calling all 421,000 machines validators collapses three jobs Pi itself keeps separate. The official node docs still describe a Computer App, a Node, and a SuperNode, and only the last of those writes the ledger.

THE THREE NODE ROLES

A Node, in Pi’s own words, verifies the chain and submits transactions after the Core Team selects it. It does not participate in consensus. SuperNodes are “the backbone,” initially chosen by the Core Team, expected to stay online around the clock, and tasked with pushing the latest state to everyone else.

That is why a six-figure node count can sit beside a much smaller group that actually closes ledgers. The white paper even treats reachability as a scarce resource: Pi Nodes use ports 31400 through 31409, and the network’s stated aim is to have at least one-eighth of nodes with those ports open, a prerequisite for SuperNode status.

The same official node page still carries a disclaimer that Mainnet nodes sit behind a firewall in an Enclosed Network period. A large home-PC fleet can be real and still not be an open validator set.

Seven Protocol Jumps and No Ledger Halt

Protocol 23 was not a one-off. Public interfaces dated on September 2, 2026 by Alexander Schmidt at cryptoticker.io put mainnet on protocol 26, running stellar-core 26.1.0, at ledger 28,512,793. Testnet 1 had been on protocol 27 since August 20. Testnet 2 was still on 26.

SEVEN MAINNET JUMPS, MARCH TO AUGUST

That is seven version jumps from mid-March to mid-August, 149 days, with gaps that swing from two weeks to 47 days. Around the July 22 and August 13 switches, the largest measured hole between ledgers was six seconds. Over 10,000 ledgers from September 1 at 19:19 UTC to September 2 at 9:51 UTC, the average close was 5.23 seconds. The chain did not pause for a maintenance window.

Protocol 26’s node deadline was August 11. The version number on the ledger moved two days later, on August 13 at 16:51:43 UTC. Operators who waited for a visible flip to start the install were already late. The cutoff is when software must be in place, not when the chain advertises the new number.

Ubuntu 24 and Postgres 16 Hit Home Machines

The May job was heavier than a binary bump. On May 20 the Core Team thanked operators for getting through v23 and called it one of the hardest upgrades yet, because it stacked three subsystem moves: Protocol 22 to 23, Ubuntu 20 to 24, and PostgreSQL 12 to 16, plus internal data reprocessing.

Big kudos to Mainnet Node operators for upgrading to v23. Most major Nodes have now been upgraded, and the protocol is expected to move to v23 soon.

Pi Network, @PiCoreTeam, May 20, 2026

Pi’s chain follows Stellar Core. Protocol 23 on that stack is Whisk, the release Stellar shipped for parallel transaction processing on Stellar Core and a single event format for classic payments and contracts. The matching engine build is in the Stellar Core v23.0.1 release notes.

That is the technical payload hiding under the “smart contracts are coming” line from May. Whisk lets a Stellar-class node apply contract work on more than one thread and emit one event stream. It does not, by itself, fill a chain with apps, pools, or trades. Later Core Team posts still talk about expanding contract authentication, which is a tell that May’s switch was a platform move, not a finished product launch.

How the Upgrade Cadence Uses Disconnects

Miss a deadline and the node is dropped from the network until it catches up. That rule, not a validator vote, is how Protocol 23, 25, and 26 moved through a claimed 421,000-machine fleet, and it is the same rule now attached to Protocol 27.

WHAT NODE OPERATORS HAD TO INSTALL

• Protocol 23 stack: Docker-era node software plus Ubuntu 24 and PostgreSQL 16, with a rewrite of existing chain data that the Core Team warned would take longer than earlier updates.
• Follow-on versions: Forced jumps through protocols 24, 25, and 26, each with its own cutoff and the same penalty for lagging machines.
• Desktop 0.6.2 and 0.6.3: SoloHost, connectivity, and app-hosting changes on the same computers, including a five-device distributed-compute trial the Core Team said completed end to end in August.
• Protocol 27 software: Version 27.1 on the node side, with the live download page now shipping Pi Node 0.6.3 for Windows, Mac, and Linux.

The pattern is operational, not parliamentary. Operators execute. The Core Team sets the date. A home computer that misses the window is not a dissenting validator. It is an offline client.

That is also why a protocol number can keep climbing while Pioneer complaints stay stuck on KYC and migration. Under the August 21 Protocol 27 post, some readers still called the project idle, and others asked how to finish a migration that had not moved in years. Those are not arguments about Ubuntu. They are a reminder that node compliance and user unblocking are different queues, and only one of them has a hard disconnect date.

September 15 Is the Next Disconnect Date

On August 21, after Protocol 26 on mainnet, @PiCoreTeam said testnet was moving to Protocol 27 and named the mainnet target in plain language.

Following the successful completion of the Protocol 26 upgrade on Pi Mainnet, Pi Testnet is upgrading to Protocol 27!

Protocol 27 introduces more flexible and secure smart contract authentication capabilities, enabling more advanced ways for accounts and applications to… pic.twitter.com/Qb5Id092Ln

— Pi Network (@PiCoreTeam) August 21, 2026

“Protocol 27 introduces more flexible and secure smart contract authentication capabilities, enabling more advanced ways for accounts and applications to authorize transactions,” the account wrote. “The target date for the Mainnet upgrade to 27 is September 15, 2026.”

The live every Mainnet node must upgrade to v27 banner now matches that post. Holders who only mine in the phone app do not have a balance action on that date. Node operators do.

WHAT WE KNOW

• Named target: The Core Team set September 15, 2026 for a mainnet move to Protocol 27 after calling Protocol 26 a milestone ahead of that “final planned upgrade.”
• Stated feature: The official post describes smarter contract authentication, not a list of new consumer apps.
• Software on the page: Pi Node 0.6.3 is the current advertised desktop build, with a Google doc linked for deadlines and steps.

WHAT IS UNCONFIRMED

• Mainnet DEX in the same switch: The August 21 post does not launch an AMM, order book, or public RPC rewrite. Those extras show up in other write-ups and should be treated as separate until the Core Team says they are on mainnet.
• Testnet 2 timing: As of the September 2 measurement, the second testnet had not yet moved to protocol 27, so the last rehearsal step was still open 13 days before the named target.
• A new node census: No fresh official recount replaced the 421,000 figure. Later notices kept using it.

Protocol 23 did what a platform upgrade does. It put a claimed 421,000 home machines on a newer Stellar Core, with a harsher OS and database underneath, and it did it without stopping the ledger. The bill that came due is the next cutoff. September 15 is the date on the calendar, and the node page is already collecting the installs.

Disclaimer: This article is news reporting and analysis of Pi Network’s node count and protocol upgrades, and it is for information only. It is not investment advice, trading advice, or a recommendation to buy, sell, hold, or mine PI, and it is not advice on running node software or storing passphrases. Readers should consult a qualified financial adviser and, if they operate a node, follow only official Pi Network instructions before changing software or moving tokens. Figures, protocol versions, deadlines, and software builds reflect the cited Core Team posts, the live Pi Node page, and the September 2 ledger measurements, and all of those can change.