Pi Network has pushed four developer-focused updates as it counts down to its Ecosystem Summit on Nov. 17–19 — moves that touch app configuration, token tracking, AI-assisted desktop packaging and identity checks.
What’s new
- Developer Portal overhaul: The old onboarding checklist has been replaced by a centralized App Configuration area where teams can manage domains, API keys, app wallets and privacy settings. Navigation has also been reorganized to make it easier to find Pi Sign-In, Ecosystem Listing, PiNet and the Pi Ad Network.
- SoloHost packaging with AI helpers: Developers bringing existing apps to Pi Desktop can now supply a public Docker image and rely on an automated SoloHost “skill” to generate the files needed for submission. Pi says supported code assistants (Claude Code, Cursor and Codex) ask which capabilities an app needs and then generate and validate two configuration files to speed packaging.
- Pi BlockExplorer token history: The explorer now shows price-history for Launchpad Testnet tokens (for example SLICE) quoted against Test-Pi. These experimental tokens are publicly visible — no Pi account or Pi Browser required — and Pi stresses they “will never go on Mainnet.” The Launchpad model routes proceeds into a liquidity pool paired with the ecosystem token rather than directly to the issuing project.
- PiVerify identity checks: A new “face uniqueness” check aims to detect duplicate identities, and additional liveness checks let businesses re-run verification after an initial check. Third-party customers pay in Pi to use the service, which is built on the network’s KYC technology.
Context and prior changes
These updates build on a September developer release that added local storage for selected Pi Browser apps (keeping preferences and session data on-device and tied to account+device, not synced across devices), app-specific staking data and file-sharing functions. Documentation was consolidated onto a single Pi-owned domain with guidance on registration, sandbox development, authentication, payments and preparing apps for Mainnet.
Pi Desktop developments
The SoloHost packaging feature follows Desktop 0.6.4, which removed the need to configure a home router for remote access to SoloHost apps. In Oct. 22 release notes, Pi explained users can reach apps running on their computers via Pi Browser on phones; remote access is optional and existing users can select “Reconnect” to migrate to the new method. The desktop client also now enforces checks on application access to files and networks — running when software is published, before installation, and on startup — intended to limit access to unrelated files, other applications and Pi Node data.
Numbers and transparency gaps
Pi’s October summit announcement lists over 300 Mainnet applications, more than 420,000 Nodes and 18.1 million fully KYC-verified users. However, Pi has not published an active-developer total or time series showing app growth, and the app count alone does not indicate regular user activity or payment volumes.
Privacy questions remain
Pi’s new verification features raise unanswered questions: the Oct. 29 update does not say how biometric records are handled, how long they are retained, or what specific customer data is shared with participating businesses.
What to expect at the Nov. summit
Pi plans three days of online presentations, demos and discussions between builders and the Core Team. The event will showcase company and community apps, dig into developer tools and reveal more details about a forthcoming hackathon.
Bottom line
The latest releases show Pi continuing to mature its developer tooling and ecosystem services — from streamlined app configuration and AI-assisted packaging to token testing and identity services — but also leave notable transparency gaps around usage metrics and biometric data handling ahead of a major community event.
What’s new
- Developer Portal overhaul: The old onboarding checklist has been replaced by a centralized App Configuration area where teams can manage domains, API keys, app wallets and privacy settings. Navigation has also been reorganized to make it easier to find Pi Sign-In, Ecosystem Listing, PiNet and the Pi Ad Network.
- SoloHost packaging with AI helpers: Developers bringing existing apps to Pi Desktop can now supply a public Docker image and rely on an automated SoloHost “skill” to generate the files needed for submission. Pi says supported code assistants (Claude Code, Cursor and Codex) ask which capabilities an app needs and then generate and validate two configuration files to speed packaging.
- Pi BlockExplorer token history: The explorer now shows price-history for Launchpad Testnet tokens (for example SLICE) quoted against Test-Pi. These experimental tokens are publicly visible — no Pi account or Pi Browser required — and Pi stresses they “will never go on Mainnet.” The Launchpad model routes proceeds into a liquidity pool paired with the ecosystem token rather than directly to the issuing project.
- PiVerify identity checks: A new “face uniqueness” check aims to detect duplicate identities, and additional liveness checks let businesses re-run verification after an initial check. Third-party customers pay in Pi to use the service, which is built on the network’s KYC technology.
Context and prior changes
These updates build on a September developer release that added local storage for selected Pi Browser apps (keeping preferences and session data on-device and tied to account+device, not synced across devices), app-specific staking data and file-sharing functions. Documentation was consolidated onto a single Pi-owned domain with guidance on registration, sandbox development, authentication, payments and preparing apps for Mainnet.
Pi Desktop developments
The SoloHost packaging feature follows Desktop 0.6.4, which removed the need to configure a home router for remote access to SoloHost apps. In Oct. 22 release notes, Pi explained users can reach apps running on their computers via Pi Browser on phones; remote access is optional and existing users can select “Reconnect” to migrate to the new method. The desktop client also now enforces checks on application access to files and networks — running when software is published, before installation, and on startup — intended to limit access to unrelated files, other applications and Pi Node data.
Numbers and transparency gaps
Pi’s October summit announcement lists over 300 Mainnet applications, more than 420,000 Nodes and 18.1 million fully KYC-verified users. However, Pi has not published an active-developer total or time series showing app growth, and the app count alone does not indicate regular user activity or payment volumes.
Privacy questions remain
Pi’s new verification features raise unanswered questions: the Oct. 29 update does not say how biometric records are handled, how long they are retained, or what specific customer data is shared with participating businesses.
What to expect at the Nov. summit
Pi plans three days of online presentations, demos and discussions between builders and the Core Team. The event will showcase company and community apps, dig into developer tools and reveal more details about a forthcoming hackathon.
Bottom line
The latest releases show Pi continuing to mature its developer tooling and ecosystem services — from streamlined app configuration and AI-assisted packaging to token testing and identity services — but also leave notable transparency gaps around usage metrics and biometric data handling ahead of a major community event.