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
Latest Events
View All →Pi Desktop 0.6.4: SoloHost Remote Access Router-Free Setup, Application Adds Access Scope Check
On October 22, the official team published a blog post announcing Pi Desktop version 0.6.4. This update includes improvements to SoloHost remote connections, enhanced protection for SoloHost applications, and minor interface refinements. The team also confirmed at the end of the post that the Pi Mainnet has completed its Protocol 28 upgrade. Remote Access: No More Home Router Configuration The official team explained that since its launch, SoloHost has allowed Pioneers' computers to act as their own servers, enabling Pioneers to remotely access applications running on their desktops, such as AI agents, from the mobile version of SoloHost within the Pi Browser. Previously, setting up this remote connection required adjusting home routers and might not have worked in certain network environments. Starting with 0.6.4, Pi Desktop no longer requires users to open ports on their home network when establishing a connection. The official team described this as removing a major technical barrier to remotely accessing SoloHost applications. Two additional points: Remote access remains an optional feature, and Pioneers decide whether to enable it. Pioneers who have previously set up remote access can switch to the new connection method by selecting "Reconnect" in the remote access interface. This blog post does not explain the technical workings of the new connection method. Application Protection: Checks Before Installation, On Every Launch, and Upon First Publication The official team explained that the system now provides technical support to verify that each SoloHost application can only access its own files and network, reducing the risk of applications accessing other parts of the user's computer, Pi Node, or other application data. This check is performed before installation and every time the application is launched. The same check is also performed when an application is first published, helping to identify and prevent applications that fail the check from entering the SoloHost directory. The official team stated that this reduces risk across multiple stages, from publication and installation to launch. The official team also reminded: Pioneers should still evaluate each application or package themselves and install at their own risk. Other Updates and Downloads This version also includes minor interface improvements, including updates to the Pi Node port opening interface. Updates can be downloaded from the official Pi Node page. Official Confirmation: Protocol 28 Mainnet Upgrade Completed At the end of the blog post, the official team confirmed that the Pi Mainnet successfully completed its Protocol 28 upgrade on October 16. The team explained that this upgrade improves how the network handles transaction data latency and makes it easier for developers to maintain smart contracts, including upgrading an entire set of smart contracts at once and more securely changing stored data as applications evolve. OrbitWatch had previously monitored via the Horizon API that the switch occurred on October 16 UTC, consistent with the official announcement date. For details, see the confirmation article on the mainnet protocol switching to v28. OrbitWatch's Observations The official team previously emphasized in descriptions of SoloHost applications like OpenClaw that applications run within containers with restricted access. The 0.6.4 update extends this "restricted access scope" to checks performed before installation, upon launch, and during first publication. However, the official wording is "reducing risk," and they reiterated that Pioneers need to evaluate and install at their own risk. SoloHost, in the official team's positioning, remains a continuously expanding platform. Further Reading Pi Desktop 0.6.3: SoloHost App Exploration, Stability, and Developer Tool Updates SoloHost Adds Two New Apps: OpenClaw Local AI Agent and Atlassian MCP Server Confirmation: Pi Network Mainnet Protocol Officially Switched to v28 Data sources: Pi Network official blog (minepi.com/blog/solohost-pi-desktop-0-6-4/, published on 2026/10/22), 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 Desktop 0.6.4 simplifies SoloHost remote access by eliminating the need for users to configure home router port forwarding.
- •Enhanced security for SoloHost applications includes new access scope checks performed before installation, on every launch, and upon first publication.
Oct 23, 12:13 AM
Read Full Analysis →Confirmation: Pi Network Mainnet Protocol Switched to v28
OrbitWatch's Horizon API monitoring detected: The Mainnet protocol_version has officially switched to 28. You can verify this directly on the Block Explorer: 👉 blockexplorer.minepi.com When Did the Switch Occur? The switch occurred between these two ledgers, specifically on October 16 (UTC), aligning with the official target date for the Mainnet on October 16. OrbitWatch's monitoring detected the change during its next check on October 17. Full Timeline of This Upgrade Compared to previous upgrades: V28 was completed on time on the officially scheduled date of October 16, with only 3 days between the Node deadline and the Mainnet switch, returning to the rhythm of V22–V24 and V26. What Does v28 Bring? The official announcement on September 25 explained that Protocol 28 improves how the network handles transaction data latency and allows developers to upgrade an entire set of smart contracts at once, enabling safer changes to stored data during application evolution. OrbitWatch's Observations Since V23, official explanations for all upgrades (V23, V26, V27, V28) have revolved around smart contract capabilities. However, during OrbitWatch's most recent compilation, the official response on Developer Discord stated that smart contract functionality is not yet finalized and is currently for internal use only (see Smart Contract Status Analysis for details). The continuous expansion of protocol-level capabilities and when third-party developers can actually use them remain two separate matters. The official preview for the Pi Ecosystem Summit on November 17–19 announced new platform and feature announcements, which will be the next opportunity to observe if there's any progress on this matter. OrbitWatch's Follow-up We will continue to monitor whether the official team provides further technical details on V28, as well as the actual agenda and announcements from the Ecosystem Summit. Further Reading Official Confirmation: V27 Mainnet Upgrade Completed, V28 Announced: Node Deadline 10/13, Mainnet Target 10/16 Confirmation: Pi Network Mainnet Protocol Officially Switched to v27 Pi Network Protocol Upgrade Mechanism: From Node Deadline to Mainnet Switch Data sources: Pi Network Horizon API (api.mainnet.minepi.com), Pi Network Block Explorer, @PiCoreTeam official X account (9/25 announcement). 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 Mainnet protocol has officially upgraded to v28, as confirmed by OrbitWatch's Horizon API monitoring and verifiable on the Block Explorer.
- •The v28 switch occurred on October 16 (UTC), aligning with the official target date, and aims to improve transaction data latency and enable safer smart contract upgrades.
Oct 16, 05:15 PM
Read Full Analysis →Pi's First Ecosystem Summit Held Online 11/17–19: First Focus on Developers, New Hackathon to Be Announced
The official blog post on October 15 announced the Pi Ecosystem Summit, Pi's first-ever event dedicated to developers. Official Event Content The official statement explains that the summit will focus on Pi's developer platform, ecosystem building, and the creation of practical utilities, comprising five main parts: Platform Releases & Developer Updates: Announcing new Pi platform features, capabilities, and resources available to developers Developer Demos: Live demonstrations of how developers use specific Pi tools to build applications App Showcases: Featuring applications built by enterprise and community developers, and how they utilize Pi Developer Conversations: Developers discussing with the Pi Core Team what they want to build on Pi, how the Pi platform and community can support them, and potential future directions for the platform New Hackathon: Introducing an upcoming Pi Hackathon, with more details to be announced during the summit The official statement also clarified the difference from existing events: Pi Day and Pi2Day celebrate the progress of the entire Pioneer community and the network as a whole, whereas this summit will specifically focus on developers, the tools that support them, and the applications they build for Pioneers. Official Narrative on "Developing on Pi" The official article points out that as AI lowers the barrier to software development, "reaching users" and "acquiring distribution channels" are becoming increasingly important for developers. The official statement claims that Pi offers a ready-made distribution network and utility ecosystem, allowing developers to connect their applications to over 60 million actively engaged Pioneers (officially termed "Engaged Pioneers"), complemented by infrastructure such as app discovery, user authentication, and Pi payments. The ecosystem figures provided by the official blog post are as follows. These are self-reported by the official team, and OrbitWatch has not independently verified them: The official team also listed developer tools and resources progressively launched in 2026, including: enabling applications built with external AI tools to be imported into Pi App Studio, the release and improvements of the SoloHost platform, new SDK functionalities, and enhanced developer documentation. The official statement indicates that these updates aim to lower practical development barriers, and the summit will introduce more new capabilities and demonstrate how developers can utilize them. OrbitWatch's Observations This is the first time the official team has hosted an event solely focused on developers. The official announcement only mentioned "new platform and feature announcements" without revealing specific releases. The official team explicitly identified "reaching users and distribution" as a challenge for developers. This aligns with the exposure channel issues previously documented by OrbitWatch in its Developer Landscape Analysis, but this time it was raised by the official team itself. A key point we will monitor is whether the summit's conversation sessions will address the most frequently raised issues by developers. For example, the Mainnet migration process and when smart contracts will be open to third parties were not mentioned in this official blog post. We will update our observations once the agenda is released and compared with the actual content. OrbitWatch's Ongoing Tracking The official team stated that the detailed agenda and viewing instructions will be announced closer to the event. Details for the new hackathon will also be revealed during the summit. We will continue to monitor this information. Further Reading Official Team Adds Three Developer Features and Integrates Developer Documentation for the First Time Pi Ecosystem Developer Landscape: How Far Between Investment and Return? Pi Desktop 0.6.3: SoloHost App Discovery, Stability, and Developer Tool Updates Data Source: Pi Network official blog (minepi.com/blog/introducing-ecosystem-summit/, published on 2026/10/15). 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.
- •The Pi Ecosystem Summit, Pi's first developer-focused event, will be held online from November 17-19, 2026.
- •The summit will feature platform updates, developer demos, app showcases, conversations with the Pi Core Team, and the announcement of a new hackathon.
Oct 15, 11:18 PM
Read Full Analysis →Official blog explains Pi's stablecoin policy: Pi remains the primary cryptocurrency, stablecoins positioned as supplementary, implementation details yet to be announced
The official blog post, "Pi Network's Approach to Stablecoins," was published on October 8. This marks the first time the official team has fully articulated Pi's stablecoin policy in an article since the announcement of its partnership with Open Standard on October 1. The Official Team's Three Core Stances Stablecoins are responsible for scenarios requiring "price stability." The official team noted that the Pi ecosystem has expanded to include applications, development tools, platform services, commerce, and payments. Stablecoins can play a role in some of these use cases, especially where predictable prices are needed. However, the official team positions their role as having a narrower scope. Pi remains the primary cryptocurrency in the network's processes. The official team explicitly stated that stablecoins play a complementary role in the ecosystem. Stablecoin functionality should be directed towards situations genuinely requiring price stability, while preserving Pi's utility throughout the entire ecosystem. The introduction method will be deliberately designed and may differ from other implementations. The official team explained that simply adding a stablecoin does not guarantee it will naturally complement Pi. How the two operate in parallel depends on how the stablecoin is integrated into the Pi ecosystem. Therefore, Pi's approach may differ from how stablecoins are introduced elsewhere. Official List of Potential Stablecoin Use Cases The official team used "can" and "may" in their tone, listing several directions: Token price volatility can create practical difficulties for economic activities that rely on predictable prices; different businesses and organizations also have varying capacities and willingness to bear token price risks. Price stability may also simplify certain forms of accounting, settlement, and interactions with entities outside the blockchain ecosystem. Stablecoins can provide additional connection channels, bringing more participants into the Pi ecosystem and keeping transactions and activities that might otherwise rely on external infrastructure more within Pi. Why OUSD Was Chosen The official team explained that the partnership with OUSD was chosen because it reflects many of the same principles Pi was built upon: when a network operates best, value remains in the hands of the people and businesses who build and use it. The official team's description of OUSD includes: collective governance by a growing alliance of over 200 companies; free minting and redemption at any scale; and a design that returns most reserve earnings to partners responsible for its distribution. The official team described this as a network model, and one suitable for Pi. In this partnership, Pi will explore reward programs for Pioneers and the broader utility of OUSD within the Pi ecosystem, consistent with the official tweet on October 1. Implementation Phase: Current Focus is on "Principles," Not "Features" The official team explicitly stated at the end of the article: OrbitWatch's Observations This blog post's wording is consistent with the October 1 tweet, both using "explore," and the blog further clarifies that it is still in the "principles" phase. Therefore, only policy-level information can be confirmed at this time. This official blog post does not mention any specific payment processes, exchange mechanisms, reserve custodians, supported blockchains, specific fiat currencies, or launch timelines. Many diagrams and articles describing specific Pi × OUSD collection or settlement processes have recently circulated online. These contents are not from this official statement. When readers encounter such content, they can refer back to the official blog to distinguish between "officially stated policies" and "possible scenarios inferred by third parties." We will continue to monitor whether the official team releases more specific integration information in the future. Further Reading Pi Network Announces Partnership with Open Standard to Explore OUSD Stablecoin Integration Data Source: Pi Network Official Blog (minepi.com/blog/pi-stablecoins/, published on 2026/10/8). 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 published a blog post on October 8, clarifying its stablecoin policy after announcing a partnership with Open Standard on October 1.
- •Pi remains the primary cryptocurrency, with stablecoins serving a complementary, narrower role for scenarios requiring price stability (e.g., accounting, settlement, specific transactions).
Oct 9, 02:52 AM
Read Full Analysis →Pi Network Announces Partnership with Open Standard to Explore OUSD Stablecoin Integration
@PiCoreTeam announced on X on October 1st that Pi Network will partner with Open Standard – the company behind Open USD (OUSD), a stablecoin co-governed by partners and positioned as open infrastructure. What the Official Announcement Said The official statement explained that Open Standard brings together over 200 partners across payments, finance, technology, and cryptocurrency, including Visa, Google, and Stripe. OUSD is designed with a reward model focused on supporting ecosystem growth. Pi will explore reward programs for Pioneers and the broader utility of OUSD within the Pi ecosystem. The official announcement stated that more details would be released later. Wording to note: The official announcement used the word 'explore,' not to announce a completed integration or a live feature. Cross-Verification: Pi Network Appears on Open Standard's Official Partner List OrbitWatch verified Open Standard's official website (joinopenstandard.com/partners, last updated 9/30) partner list and confirmed that Pi Network is listed among them, alongside projects like PingPong, Plasma, and Polygon under the same alphabetical category. This list also includes over 200 companies and institutions such as Visa, Mastercard, Coinbase, Stripe, BlackRock, and Google. What Remains Unclear After reviewing multiple reports, several questions currently remain unanswered by OrbitWatch: What specific role Pi Network plays in this partnership; no independent technical explanation has been released by the official team. There is currently no timeline for OUSD's reward programs or its utility within the Pi ecosystem. Whether this partnership has a direct connection to the previous 'OpenPay restores cash-in function allowing Pi to be exchanged for OUSD' has not been clarified by the official team – OpenPay is an independent third-party Web3 wallet that previously supported Pi-to-OUSD exchange, but it's currently unconfirmed if that is on the same track as this official partnership announced by the Pi Core Team itself. OrbitWatch's Ongoing Monitoring Being included on the partner list is a verifiable fact, but it's still a distance from 'concrete integration going live.' We will continue to monitor whether the official team releases more detailed technical explanations. Further Reading Official Confirmation: V27 Mainnet Upgrade Completed, V28 Announced Simultaneously Data sources: @PiCoreTeam official X account (posted 2026/10/1), Open Standard official partner list (joinopenstandard.com/partners, verified 2026/10/1). All analysis does not constitute investment advice. OrbitWatch is an independent observer of the Pi Network ecosystem and is not affiliated with the official Pi Network team.
- •Pi Network announced a partnership with Open Standard to "explore" integrating Open USD (OUSD) stablecoin into the Pi ecosystem.
- •Pi Network has been confirmed to be listed on Open Standard's official partner list, which includes over 200 major companies and institutions.
Oct 1, 07:13 AM
Read Full Analysis →Official Confirmation of V27 Mainnet Upgrade Completion, Simultaneously Announcing V28: Node Deadline 10/13, Mainnet Target 10/16
@PiCoreTeam posted on X early this morning, officially confirming that Protocol 27 has successfully completed its upgrade on the Mainnet, and simultaneously announced that the Testnet has been upgraded to Protocol 28. Official Announcement Details The official statement explains that following the successful completion of the Protocol 27 upgrade on the Mainnet, the Testnet has been upgraded to Protocol 28. Protocol 28 improves how the network handles transaction data latency and allows developers to upgrade an entire set of smart contracts at once, enabling safer changes to stored data during application evolution. The official team also announced the timeline: All node operators must upgrade their nodes to Protocol 28 by October 13, 2026, in preparation for the Mainnet Protocol 28 upgrade on October 16. This Confirms the Complete V27 Timeline OrbitWatch previously observed via the Horizon API that the Mainnet had switched to v27 on 9/22. This official announcement serves as a post-facto confirmation, with the timing being consistent. V28 Now Has a Clear Timeline This also resolves a previous uncertainty: the official team had referred to V27 as the "final planned upgrade," but the node upgrade path later showed a step from 27.1 → 28.x, which at the time had no deadline or technical details, only marked as TBD. This official announcement now provides the complete information: Compared to previous instances: If V28 proceeds smoothly according to the official timeline, the interval between the node deadline and the Mainnet switch will be just 3 days, returning to the faster pace seen with V22-V24 and V26. OrbitWatch's Ongoing Tracking We will continue to monitor for further technical details regarding V28 on the Testnet, as well as the actual status of nodes and the Mainnet around the October 13 and October 16 dates. Further Reading Confirmation: Pi Network Mainnet Protocol Officially Switched to v27 Nodes Upgraded to v27, but Testnet 2 and Mainnet Still Awaiting Pi Network Protocol Upgrade Mechanism: From Node Deadline to Mainnet Switch Data sources: @PiCoreTeam official X account (post on 2026/9/25), Pi Network Horizon API (api.mainnet.minepi.com). All analysis does not constitute investment advice. OrbitWatch is an independent Pi Network ecosystem observer and is not affiliated with the official Pi Network team.
- •PiCoreTeam officially confirmed the successful V27 Mainnet upgrade and announced the Testnet's upgrade to Protocol 28.
- •Protocol 28 enhances transaction data latency and enables developers to upgrade smart contracts more securely in batches.
Sep 26, 11:34 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