Pi Network Ecosystem Tracker
Real-time tracking of protocol updates, on-chain data, and community activity
View LatestProtocol Version
Daily Transactions
Large Transfers
Fee Pool Daily Growth
Upgrade Countdown
Date TBD
Latest Events
View All →Pi Launchpad Completes SLICE Test Token Distribution and Introduces Liquidity Pool Price Tracking
Pi Launchpad has completed the distribution of its second testnet token, SLICE. According to the official blog (published on 7/24), from June 11 to June 28, over 240,000 Pi miners participated in this test, contributing a total of 15.92 million Test-Pi in exchange for 10 million SLICE test tokens. What's Different This Time Compared to the First Test Token The official statement explains that the main difference between SLICE and the first test token is that SLICE is linked to a real, operational third-party game, 'Slice of Pi,' rather than a mock application used for testing. The official team states that this helps align with the Pi ecosystem token's 'product-first' goal—where the token's purpose is to support application utility, user acquisition, and engagement, rather than primarily for fundraising. The participation process has also been simplified. This time, focusing on the amount of Test-Pi contributed by miners, the Launchpad automatically calculates the corresponding fair access lock-up amount and presents participation benefits as percentage rewards. This aligns with the direction previously mentioned by the official team in Improved Participation Flow and Updated Model. What the Interface Now Offers After Distribution The official team explains that after the SLICE distribution is complete, the Pi Launchpad interface currently provides: Personal allocation details and token acquisition price SLICE liquidity pool access Price chart: tracking SLICE's price changes relative to Test-Pi How the Liquidity Pool Works (Official Explanation) The official team dedicated considerable space in this blog post to explain the AMM mechanism, which is one of the key highlights of this update. Under the Pi Launchpad model, the Pi received from token issuance does not belong to the issuer but enters a liquidity pool, paired with ecosystem tokens. The purpose of this design is to establish a healthy liquidity foundation from the outset. SLICE's liquidity pool utilizes an Automated Market Maker (AMM) algorithm, calculated using the constant product formula: SLICE Reserve × Test-Pi Reserve = Constant Product This means that each time a miner exchanges Test-Pi for SLICE, Test-Pi increases, SLICE decreases, and the displayed price of the remaining SLICE will rise; the reverse is true for the opposite exchange. The official team emphasizes that this pricing is automatically calculated based on the quantity changes of the two assets in the pool, not manually set. The official team also reminds: SLICE only exists on the testnet and will not be transferred to the mainnet. Purpose of This Test The official team clearly stated two purposes: first, to allow miners to gain practical exposure to DeFi mechanisms (liquidity pools, token swaps, automated pricing); second, to collect data and community feedback to further improve the Launchpad's design and mechanisms before the mainnet version goes live. Related Reading → Pi Launchpad Releases Improved Participation Flow and Updated Model Data source: Pi Network official blog (minepi.com/blog/launchpad-liquidity-pool/, published on 2026/7/24). All analyses do not constitute investment advice. OrbitWatch is an independent Pi Network ecosystem observatory and is not affiliated with the official Pi Network.
- •Pi Launchpad has completed the distribution of its second testnet token, SLICE, with over 240,000 miners participating and contributing 15.92 million Test-Pi.
- •Unlike the first test token, SLICE is integrated with a real third-party game, 'Slice of Pi,' reinforcing the 'product-first' approach for token utility and engagement.
Jul 24, 04:00 PM
Read Full Analysis →Confirmation: Pi Network Mainnet Protocol Officially Switched to v25
OrbitWatch's Horizon API monitoring detected today: The Mainnet protocol_version has officially switched to 25. You can verify this directly on the Block Explorer: 👉 blockexplorer.minepi.com Full Timeline of This Upgrade Compared to previous upgrades: 34 days. This time span is significantly different from previous upgrades. The reason, as we explained in a previous post, is that v25 introduces BN254 encryption and Poseidon hashing, which are new cryptographic capabilities at the protocol layer, making the technical complexity higher than previous versions. What Does v25 Bring? According to the official blog (published 7/15): Key Updates: BN254 Encryption + Poseidon Hashing These two technical components enable developers to build zero-knowledge applications on Pi — allowing for the verification of identity or conditions without revealing all personal information. The official examples given are identity verification and proof-of-qualification applications. For general node operators, v25 does not introduce any directly noticeable interface changes. This is a protocol-level capability expansion, significant for opening up new application directions for developers. OrbitWatch's Follow-up The deadline for the V26 upgrade is currently TBD, with no confirmed date from the official team yet. We will continue to track this and publish updates as soon as the switch occurs. Further Reading → Official Confirmation: v25 Mainnet Upgrade Expected 7/22, Clues Emerge for the Delay → Nodes are Already Running v25, But Mainnet is Still v24 — This Discrepancy is Different This Time → V25 Node Deadline Passed, Our Nodes Are Still on v24 — Is This Normal? Data sources: Pi Network Horizon API (api.mainnet.minepi.com), Pi Network Block Explorer, Pi Network Official Blog (minepi.com/blog/v25-menu-redesign/). All analysis does not constitute investment advice. OrbitWatch is an independent Pi Network ecosystem observatory and is not affiliated with the official Pi Network team.
- •Pi Network's Mainnet protocol has officially upgraded to v25 on July 22nd, as confirmed by OrbitWatch's Horizon API monitoring.
- •This v25 upgrade, which took 34 days from the node deadline (significantly longer than previous 3-day transitions), introduces advanced cryptographic capabilities: BN254 encryption and Poseidon hashing.
Jul 22, 01:00 PM
Read Full Analysis →Official Confirmation: v25 Mainnet Upgrade Expected 7/22, Finally a Clue Why It Took So Long This Time
From the June 18th deadline until now, we've had a lingering question in our previous two articles tracking v25: Why is this mainnet switch taking so much longer than the previous three? On July 15th, the official blog provided part of the answer. Official Confirmation: Mainnet Switch on 7/22 Looking back at previous instances: 34 days. This isn't a "slight delay"; it's a significantly different timeframe compared to before. Why the Long Delay This Time? The Official Explanation In the past three instances (V22, V23, V24), the official team never published a separate article explaining the switch beforehand. This time, a dedicated blog post was written, stating that v25 introduces two technical components: BN254 encryption and Poseidon hashing According to the official statement, these two are the technical foundation for building zero-knowledge applications – allowing apps to verify whether an identity or condition is met without revealing all personal information. The examples given are identity verification and proof of qualification. This is considerably more complex than V24's "infrastructure reinforcement." V24's goal was to make the network more stable, while V25 adds new cryptographic capabilities at the protocol layer. The technical complexity of the two is not on the same level, which might be the reason for the extended duration – however, the official blog itself didn't directly explain why there was a 34-day gap, and we won't speculate without basis. Other Updates Announced by the Official Team This blog post also includes two updates unrelated to the protocol upgrade, which are noted here: Redesign of Pi Mining App's Side Menu and Profile Page The official team stated this is "the first step in a comprehensive app update," introducing dark mode and adjusting information layout. They explicitly mentioned that this will be rolled out gradually, not all at once. This part is unrelated to the protocol upgrade and concerns changes to the app's interface layer. Removal of Banxa as an In-App Option Since the app now offers Fast Track KYC for direct mainnet wallet creation, the official team has removed Banxa from the app interface. The official statement clarifies that Banxa can still be used as an external third-party option, it just won't appear within the app's interface anymore. OrbitWatch's Next Tracking Focus July 22nd is the scheduled date provided by the official team. Around that time, we will verify whether the Horizon API's protocol_version has indeed switched. As in the past – just because the official team says it will happen doesn't mean it will happen on that exact day. We await on-chain data to confirm. Further Reading Nodes are already running v25, but mainnet is still v24 – this discrepancy is different this time V25 Node Deadline Passed, Our Nodes Are Still on v24 – Is This Normal? Data sources: Pi Network official blog (minepi.com/blog/v25-menu-redesign/, published 2026/7/15), Pi Network Horizon API (api.mainnet.minepi.com). All analyses do not constitute investment advice. OrbitWatch is an independent Pi Network ecosystem observatory and is not affiliated with the official Pi Network team.
- •Pi Network's v25 mainnet upgrade is officially scheduled for July 22nd, marking a significant 34-day delay compared to previous upgrades which typically took only 3 days.
- •The extended delay is attributed to the introduction of complex new cryptographic capabilities (BN254 encryption and Poseidon hashing) in v25, which are crucial for building zero-knowledge applications.
Jul 15, 04:00 PM
Read Full Analysis →Pi Node 0.6.1 Live: What Do SoloHost, Hermes AI Agent, and Soroban RPC Actually Look Like?
On Pi2Day 2026 (6/28), the official team announced new features like SoloHost. We summarized what the official team said would be available in our Pi2Day report. Now that the node software has been updated to 0.6.1, these features have actually appeared in the interface—this article documents what we've seen firsthand. Pi Node 0.6.1: Automatic Update This version is automatically pushed; the node software will update itself to 0.6.1 without manual intervention. The old node software itself could automatically pull the v25 container to run (we documented this in our previous article). 0.6.1 is a separate update, and the two events are not causally related. New: Optional Soroban RPC service switch A new switch has been added to the node settings page: Both are optional, not mandatory to enable. Soroban is the execution environment for Pi smart contracts (running since V23 went live). This new switch allows node operators to choose whether to simultaneously provide a local Soroban RPC endpoint externally—this is meaningful for developers who want to directly interact with their own nodes, but for general miners, not enabling it has no impact. Currently, this switch is enabled on our node, but the actual RPC behavior has not yet been further tested. SoloHost: A Platform for Running Apps on the Node (Early Beta) SoloHost is the most noteworthy part this time. A banner at the top of the interface clearly states: SoloHost is in early beta. The experience and functionality may change significantly as the product is being improved. It's important to remember this positioning—everything seen currently is still subject to significant adjustments. Operational Architecture (Official Interface Description) Each SoloHost app runs as an independent sandboxed Docker container. Pi Desktop manages separate compose projects for each app. Ports are by default bound to 127.0.0.1 (local, not externally exposed). Upon uninstallation, the container and volumes are removed together, leaving no data on the computer. Remote Access SoloHost includes a Remote Access feature, which runs a container in the background, allowing node operators to connect and manage their nodes via the Pi Browser. Users first need to link their Pi Network account in Remote Access, then open https://solohost.pinet.com in the Pi Browser and log in to operate. However, during actual testing, logging into SoloHost within the Pi Browser consistently got stuck on login verification, so it's not yet confirmed what settings can actually be operated. Hermes: The Official AI Agent Placed in the SoloHost Directory This is the most interesting observation this time. In SoloHost's Discover directory, the official team has placed an app called Hermes: Several notable details: Published officially by the Pi Core Team. Not a third-party developer; it's directly placed in the directory by the official team. Runs locally, not externally exposed. Port bound to 127.0.0.1, not a public endpoint. No wallet or key access. The official interface explicitly states this limitation, which is part of SoloHost's sandbox mechanism. We have not installed it yet. However, the interface shows an 'Install' button next to this App, meaning we have only confirmed that 'this app exists in the SoloHost directory and can be installed.' Its actual behavior after installation and running has not yet been verified. What's Confirmed vs. What's Still Unconfirmed Confirmed: Pi Node 0.6.1 is live, requiring manual download and installation from the official website. An optional Soroban RPC service switch has been added to node settings. The SoloHost interface has appeared, marked as Early Beta. The official Hermes (AI Agent, running locally) is in the SoloHost directory. The Remote Access feature exists within SoloHost. Unconfirmed: Actual behavior and performance of Soroban RPC. Actual experience of the Remote Access connection process. Actual functionality and behavior of Hermes after installation. Actual functionality of other apps (official and third-party) in the SoloHost directory. Further Reading → Pi2Day 2026: Introducing SoloHost, Pi Sign-in, and PiVerify → Node is already running v25, but mainnet is still v24 Data sources: Direct observation of Pi Node 0.6.1 interface, SoloHost Hermes page (2026/7/13). All analyses do not constitute investment advice. OrbitWatch is an independent Pi Network ecosystem observatory and is not affiliated with the official Pi Network.
- •Pi Node 0.6.1 has been released, introducing an optional Soroban RPC service and the SoloHost platform.
- •SoloHost, currently in early beta, allows running sandboxed Docker apps locally on the node, with the official Hermes AI agent already listed in its directory.
Jul 13, 02:55 AM
Read Full Analysis →Pi App Studio Adds Backend Support and AI Planning for New Apps
Pi App Studio just got some pretty big upgrades, honestly. They've added backend infrastructure support, starting with persistent storage. What this means for us is that apps built through the App Studio can now actually remember things across sessions – like your high score in a game or your to-do list in a productivity app. Before, if you left an app, all your data was gone, which was a bit of a bummer for anything beyond a simple, one-off experience. They also introduced an AI-assisted app planning phase. So, before the AI even starts building your app, it helps you refine your idea, asking for more details about the goal, category, and user experience. This should lead to much better, more thought-out apps from the get-go. This really builds on what we've seen recently with initiatives like Pioneers, Help Bring More AI-Created Apps to Pi and Enter Raffle to Win Pi Merchandise! and Vibe Coding Meets Pi App Studio: Build AI-Created Apps for 60M+ People, showing a clear push to make AI-generated apps more robust and useful. For everyday Pi miners, here's the thing: these updates are a big deal because they enable a whole new class of useful applications within the Pi ecosystem. Imagine apps that actually save your progress, remember your settings, or keep your data safe. This makes the apps more engaging and functional, which in turn makes the Pi ecosystem more valuable and sticky for everyone. It's all about making the apps we use daily more practical and less like fleeting demos.
- •Pi App Studio apps can now save user data across sessions, making them much more useful.
- •An AI-assisted planning phase helps creators build higher-quality apps from the start.
Jul 7, 04:25 PM
Read Full Analysis →Nodes are already running v25, but Mainnet is still v24—this time the discrepancy is different
12 days have passed since the V25 node deadline (6/18), and we've observed a new situation, different from the previous 'complete inactivity'. The nodes themselves have automatically pulled and are running the v25 container. This is inferred from the container creation time found via docker images, which was approximately two to three days ago (around 6/27–6/28) – a 9–10 day discrepancy from the official 6/18 deadline. However, both Testnet 2 and Mainnet protocol_versions are currently still v24. This Differs from Last Week's Observations In our previous post, we noted 'complete inactivity.' Now, it appears that the node side is actually active: the v25 image has been pulled, and the container is running. However, this 'node software layer readiness' and the 'official on-chain protocol version switch' are two distinct stages – a pattern consistent with previous upgrades. It's just that the gap between node-side readiness and the on-chain switch appears to be longer this time compared to previous instances. Comparing Time Lags with the Past The past three switches were completed within 3 days. This time, the node side is ready (v25 container started running around 6/27–6/28), but as of this publication, 12 days have passed since the deadline, and no on-chain change has been observed – this discrepancy is significantly longer than the previous three. We are unsure of the reason. It could be that there are more conditions to consider for this switch, or it might simply not be time yet – we have no official documentation to confirm the specific reason and will not invent explanations here. Also Noted: New Pi Node Software Version 0.6.0 This is separate from the container pull mentioned above, but the timing coincides within the last few days, so we're noting it together. Version 0.6.0 of the Pi Node software is currently available for download on the official node page. This update is not automatically pushed and requires manual download and installation from the official website. We have not yet upgraded to this version, so we are currently unaware of the specific features added or adjusted in 0.6.0. This is not causally related to the automatic v25 container pull mentioned earlier – we are currently running an older version of the Pi Node software, and the v25 container was automatically pulled and is running on this older version. In other words, you don't need to upgrade to 0.6.0 to get v25. What 0.6.0 brings remains to be investigated. Current Knowns and Unknowns Knowns: Node software (older version) has automatically pulled and is running the v25 container, around the deadline. Testnet 2 and Mainnet protocol_versions are still v24. A new version of Pi Node software, 0.6.0, is available for manual download; its content awaits verification. Unknowns: Why the on-chain switch is slower than the previous three times. What specific features 0.6.0 adds. OrbitWatch Monitoring Continues Our Horizon API monitoring continues to track the Mainnet protocol_version. We will publish an update once the on-chain version switches or when specific update details for 0.6.0 are found. Further Reading V25 Node Deadline Passed, Our Nodes Still on v24 – Is This Normal? Confirmed: Pi Network Mainnet Protocol Officially Switched to v24 Data sources: Direct observation of node docker images, Pi Network Horizon API (api.mainnet.minepi.com), Pi Network Block Explorer, minepi.com/pi-node official website. All analyses do not constitute investment advice. OrbitWatch is an independent Pi Network ecosystem observatory and is not affiliated with the official Pi Network.
- •Pi Network nodes have automatically pulled and are running the v25 container, but Mainnet and Testnet 2 protocols remain at v24.
- •The delay between node readiness and on-chain protocol switch for v25 is significantly longer (12+ days) compared to previous upgrades (typically 3 days).
Jun 30, 07:32 AM
Read Full Analysis →PiRC1
Read the PiRC1 Spec
PiRC1 is the core technical document for Pi Network's Open Mainnet upgrade, defining protocol version standards and node requirements.
Read Full SpecPiRC2
Explore the PiRC2 Spec
PiRC2 defines Pi Network's first smart contract capability — the Subscription Contract API for recurring on-chain payments.
Read PiRC2 SpecV23
Smart Contracts Guide
A deep dive into Pi Network V23 smart contracts — from PiRC2 subscription contracts to on-chain dApp integration.
Read Smart Contracts Guide