2026-04-29

Nodes are running v22, but the chain is still v21—is this normal?

Recently, a common confusion in the Pi community has been: "The official team said V22 is already being rolled out, so why do I still see protocol 21 on the Block Explorer?" Honestly, I've been observing this issue for a long time myself. The answer isn't complicated, but it involves a distinction many people overlook—**node software version** and **on-chain protocol version** are fundamentally two different things. --- ## First, the Data Currently Observed by OrbitWatch From our Horizon API monitoring, conducted every 15 minutes: - **On-chain `protocol_version`**: Currently still shows **21** - **Block Explorer** (blockexplorer.minepi.com): Also confirmed as v21 - **Node Docker container**: Official requirement is v22.1, deadline April 27 The simultaneous existence of these three numbers is not a bug, nor is anything wrong. This is the normal state of Pi Network's upgrade mechanism. --- ## Node Version vs. On-chain Protocol Version: What's the Difference? To use an easier-to-understand analogy: Imagine a city changing its traffic rules. "Node software upgrade" is like every car getting a new version of its navigation system, while "on-chain protocol version switch" is the moment the new traffic laws officially take effect. Just because cars have new navigation systems doesn't mean new laws take effect immediately—it still requires enough cars in the city to be ready, and then a unified announcement to switch. Pi Network's upgrade process is as follows: ``` Step 1: Official release of new Docker container (v22.1) ↓ Step 2: Node operators complete updates before the deadline (April 27 deadline passed) ↓ Step 3: Enough nodes on the network run the new software ↓ Step 4: Nodes "vote" to switch protocol versions via the Stellar Consensus Protocol ↓ Step 5: On-chain protocol_version switches from 21 to 22 ``` We are currently stuck between Step 3 and Step 4. Almost all nodes have updated, but the consensus switch has not yet been triggered. --- ## Why Does the Switch Take Time? This is related to the **Stellar Consensus Protocol (SCP)** adopted by Pi Network. SCP is designed for nodes to confirm with each other, rather than relying on a central server for commands. This means the protocol version switch must wait until a "sufficient proportion" of nodes are ready before they all switch together—this process cannot be forcibly accelerated, nor can the exact switch time be predicted. The advantage of this design is security: it prevents network forks due to a few nodes not updating. The trade-off is uncertain switch times, which could be hours or days. --- ## So, Is PiRC1 Considered Active Now? This is the most frequently asked question. Strictly speaking: **The PiRC1 specification document has been published, and the official team has announced it as part of V22, but it will only be considered fully active on a technical level once the on-chain `protocol_version` truly switches to 22.** However, for most ordinary Pioneers, this distinction does not affect any of your operations—your Pi balance, migration progress, or KYC status are not impacted by this switch. --- ## What to Observe Next? OrbitWatch's Horizon API monitoring checks the latest ledger every 15 minutes, which includes the `protocol_version` field. As soon as the on-chain version switches from 21 to 22, we will update our website immediately. Beyond this, what's more noteworthy next is **V23**: The deadline for V23 has been moved up from the original May 18 to May 11. This version is expected to bring full smart contract functionality and is a direct prerequisite for Pi DEX and Pi Launchpad to launch. Furthermore, the official team simultaneously announced a longer roadmap: the upgrade sequence extends from V23.0 all the way to V26.0, expected to be completed by June 22, 2026, covering five major upgrade milestones. This pace is faster than many expected, but it also means the next few months will be the most intensive period for Pi ecosystem development. --- ## Advice for Ordinary Pioneers **Pioneers not running a node:** You don't need to do anything. The on-chain protocol version switch has no direct impact on you; just continue to wait for V23. **Pioneers running a node:** If you completed the v22.1 Docker update before April 27, your node should now be online and operating normally. If you missed the deadline, your node has been disconnected, and reconnecting to the network will require a full resync, a process much more cumbersome than a direct upgrade. --- ## OrbitWatch's Monitoring Commitment We know that 'waiting' is what the Pi community is least accustomed to. Therefore, OrbitWatch promises: as soon as the on-chain `protocol_version` switches to 22, you will see an update on this page, eliminating the need to constantly refresh community groups for news. This is why we built this website. The countdown to V23 has already begun. May 11 is the day that will truly change the game. --- *Data sources: Pi Network Horizon API (api.mainnet.minepi.com), Pi Network Block Explorer, Bitget News, crypto.news. This analysis does not constitute investment advice.* *OrbitWatch is an independent Pi Network ecosystem observatory and is not affiliated with the official Pi Network team.*

• •Despite nodes running v22.1, the on-chain protocol version remains 21 because node software upgrades and on-chain protocol switches are distinct processes.
• •The on-chain protocol switch from v21 to v22 requires a consensus 'vote' by a sufficient proportion of updated nodes via the Stellar Consensus Protocol, a process that cannot be forcibly accelerated or precisely predicted.