Nodes are at the heart of decentralization for the Pi blockchain—accessible to any Pioneer with a computer connected to the internet—and their progress is vital for achieving Pi Network’s vision as we edge closer to Open Network.
Pi Nodes also have tremendous potential in computing on a large scale. Pi’s current Testnet already has over 200,000 computer Nodes waiting for transition to the Mainnet during the Open Network period. These decentralized computers are collectively estimated to possess over 1 million CPUs, making Pi Nodes one of the largest distributed systems in the world. This means that large scale computing tasks like training a massive open-source AI model become feasible, with potential utility opportunities for Node operators to get more Pi in the future. This opens up new, unprecedented opportunities in the world of decentralized computing, and another platform-level utility for Pi.
Excited? Us too. We’re committed to update and prepare Nodes for the Open Network and beyond so that the network can realize this incredible potential utility in the future.
Recently, we’ve made a lot of progress in planning strategies and updating features to this end! First, we’ll explain the initial strategies regarding setting up the ideal testing environment for testing Nodes on the Testnet and Mainnet blockchains. Then, we’ll dive deeper into the three most recent Node updates (versions 0.4.9, 0.4.10, and 0.4.11).
How to install the Pi Node today
You can download the latest Pi Node Version from the official website Node page.
Nodes are automatically updating to the latest version, so there is no need to manually upgrade if you installed the Node before. It should already be on the latest version or will auto-update the next time you start it. The current latest version is 0.4.11.
Looking ahead: Preparing Nodes for Open Network
To prepare Nodes for the Open Network, we need to enable switching between the Testnet and Mainnet blockchains. This will allow Node runners to transition smoothly to the Mainnet once the network opens. Upcoming versions of the Node application and servers will support both blockchains, ensuring this transition.
To facilitate the testing of this functionality before the Mainnet blockchain opens up, we are introducing a new clean Testnet blockchain—Testnet2—where we can emulate switching between Networks. Initially a subset of Nodes will be allocated to this new Testnet2. The blockchain each Node is connected to will be displayed in the Node application UI. This functionality will be introduced in the next version of the Node.
Reminder: Testnet is for testing and may be reset occasionally
As a gentle reminder to developers and users, please do not store production data on Testnet or make your apps dependent on it. Testnet is for testing purposes, and it’s crucial to maintain a small, nimble blockchain by resetting its state periodically.
The Testnet blockchain is intended to be reset periodically, as communicated in the first introduction of Testnet, especially as we approach Open Network. As such, a reset may occur in the coming weeks or months, as part of the preparation and testing work moving towards Open Network. Resetting means all user Testnet wallets and Test-Pi balances on Testnet will disappear after the reset.
While it’s great for developers to try their apps on Testnet, ensure your testing apps can recover from a Testnet reset. For example, an app design that would break after a reset might depend on a specific block number; after the reset, such a block may no longer exist, breaking the app on the Testnet.
Recent Node Version Updates
In critical preparation for the upcoming Open Network launch, we’ve released important Node version updates that enhance Node analytics, standardize the Node application across geographic regions, and further lays the groundwork for future developments in Node selection and decentralization—all of which are also essential towards accomplishing Condition 1 of the Open Network goals.
Pi Network launched 3 updated versions since Pi Day 2024. Below, we’ll detail the updates from each respective version. Discover the latest enhancements and how they will transform your Pi Node experience.
Version 0.4.11 (May 9, 2024)
This version was automatically pushed to all Node runners.
User Interface Updates and New Features:
- Added a new UI feature to display detailed information about the Pi Node’s catch-up process, informing the Pioneer about the current state and ongoing actions of the Pi Node.
- Introduced a warning relating to interrupting the catch-up process.
- Improved the method for nodes to determine the latest block.
- Improved the log feature with ability to send up to 40 lines of log information during issues, providing the Pi Core Team with essential details for troubleshooting.
- Implemented a mechanism to determine the appropriate running container, aiding in accurate reporting of Nodes supporting the network.
Fixes:
- Enhanced the Pi Node’s ability to recognize when it is unable to sync to the blockchain and prevent loops that waste resources.
- Fixed an issue with displaying the version number, ensuring all Pi Node Apps show the correct version currently running.
Version 0.4.10 (April 9, 2024)
Fix:
- Resolved an issue where Docker Containers did not start automatically when the Node was initiated within the Pi Node App. Pioneers should now be able to start the Pi Node from within the app, and the corresponding Docker Container will start as expected, provided there are sufficient system resources, such as available disk space.
Version 0.4.9 (March 14, 2024)
User Interface Updates and New Features:
- A new page is available for Pioneers to view their Node’s known peer list, showing the list of other Nodes currently connected.
- If Core Team Nodes are unreachable, Pioneers can now add their own known Nodes (a.k.a. peers) to keep Nodes connected to the Testnet.
- When the Node is in disconnected mode (unable to access the sync server), Pioneers can customize the history URL, allowing the Pi Node App to download the blockchain history and resume operation to the latest block.
Fixes:
- Resolved the infinite loading screen issue experienced by some Pioneers when setting up newly downloaded Nodes. All Pioneers should now be able to download, install, and set up a Node without this problem.
- Fixed the Port Checking feature, enabling Pioneers to check that all required ports are open and ready for securing the network.
- Set the default container for all Nodes to Pi-Consensus, which supports the Pi Testnet. Previously, some Nodes were blocked from accessing the Pi-Consensus Testnet Container.
- The Pi Node Installation date is fixed to display the date of installation instead of “N/A”. All Pioneers updating to version 0.4.9 will see the installation date set to the date they updated. This value is only stored locally and should not affect their node analytics.
- Pi Node uptime, when previously reported as “N/A”, will now correctly display the uptime percentage recorded over the past 90 days.
- Updated default fallbacks and redundancies to direct the Pi Node Application on handling errors, helping to limit downtime and preventing scenarios such as a Node getting stuck switching between “Synced!” and “Joining SCP”.
While the above enhancements are important in preparation for the upcoming Open Network, they are not the final steps for the Pi Node application. Stay tuned for further updates and information on the Pi Node.
