Back to collection
Research

Pi’s service stack separates identity, local work and network upgrades

Reported interfaces shorten access, but each permission and execution boundary remains distinct.

A lit concrete passage ends at a closed steel door with a small access reader.
Technical illustration

Pi’s service account names SoloHost beta for local AI work, Pi Login for external sign-in and PiVerify for identity checks, alongside a Protocol v25 upgrade scheduled for July 22. Its reported network count above 60 million is not a count of users of each service. Hosting work, proving identity and authorizing an application are different functions; the upgrade date is a reported plan, not confirmation that it completed.

The broader roundup describes VALR access to Hyperliquid perpetuals, fomo trading with TradingView data, Sui gas-free stablecoin transfers and public confidential-transfer testing. It also describes NEAR account access from more than 35 chains to over 50 markets and Infinex use of Confidential Intents. A shorter interface still needs to distinguish collateral location, execution rules and recovery when one connected service fails.

References