Linux Node Release and Upcoming Protocol Upgrades
Linux Node Release
The Pi ecosystem has released a Linux Node version! Nodes are the backbone of Pi’s decentralized infrastructure, and expanding node support beyond Mac and Windows strengthens the network’s resilience and adaptability.
For partners and services including exchanges, the Linux Node release is immediately relevant. Many of these entities already run custom Linux-based nodes to connect to Pi. With an official Linux Node release, partners and services can transition to a standardized node software. This unlocks a key benefit: Linux node operators can self-manage protocol updates or enable auto-updates from Pi Network, staying more effortlessly up-to-date with future versions. This replaces the current reliance on custom builds, creating a more stable and consistent ecosystem.
For Pioneers, the Linux Node is a feature that has been frequently requested by the community over the past few years. While it is not directly tied to Node rewards, and therefore may not impact everyday participation immediately, the update allows for greater accessibility and ecosystem participation. The significance lies in infrastructure: supporting Linux makes the network more inclusive for developers, technically capable Pioneers, and those interested in contributing through open-source environments.
Installation instructions can be found here.
Upcoming Protocol Upgrade to Version 23
Parallel to the Linux Node release, Pi Network is preparing an important upgrade: the move from protocol version 19 to version 23. The Pi protocol is adapted from Stellar protocol. This version is a custom Pi protocol built on a base pulling upgrades from Stellar protocol version 23 that enables new layers of functionality and control. The upcoming protocol upgrades will phase in through consecutive versions and may potentially require planned outages of the blockchain services. Announcing such upgrades in advance is to help partners, third-party services and the community to get prepared ahead of time.
The rollout is staged for careful testing:
Testnet1 upgrades will start this week and continue into the next few weeks.Note: During Testnet1 protocol upgrades, there might be a small outage of the Testnet1 blockchain. Pi will be pushing out the new community Node container for Testnet1, and no action is needed from users.Testnet2 and Mainnet will be phased in over the following weeks after Testnet 1 upgrades are completed, bringing the full ecosystem to version 23.Note: Specific outages may occur during the upgrades, which will be announced ahead of time to partners and Pioneers. There may also be brief outages of Pi availability on third-party service sites, such as Centralized Exchanges (CEXs), as they process this upgrade.
KYC Authority Embedded in Protocol
KYC’d blockchains open additional utility in compliant interactions among users. Pi Network will continue to operate as one of the premier KYC-verified blockchain, with tens of millions of KYC’d accounts, but the way that verification is enforced is evolving. With the protocol upgrade, this enforcement will be done directly by the blockchain protocol itself. Importantly, the upgrade allows the decentralization of KYC authority.
While the native Pi KYC solution continues to verify Pioneers, the protocol will allow KYC authority to be assigned to other trusted entities in the future. This offers a more distributed, community-driven KYC process while maintaining compliance at the protocol level.
As a reminder, identity verification via KYC is important for the integrity of the network, compliance, and readiness for integrations by services that require identity verification. Pi’s leading vision of building a KYC-verified blockchain network years earlier—and its realization of over 14.82 million migrated, KYC-verified people on the Pi Mainnet blockchain—is now echoed by the industry’s recent developments toward verified, permissioned standards such as ERC-3643, which embed identity and compliance logic directly into tokens on public networks.
$KAITO #PiNetwork @Pi-Network