Pi Network Ecosystem
| Author | Hakkyung Lee |
|---|---|
| Discussions-To | https://github.com/ChainAgnostic/namespaces/pull/199 |
| Status | Draft |
| Type | Informational |
| Created | 2026-08-19 |
| Requires | CAIP-2 |
Table of Contents
Namespace for Pi Network Chains
The pinet namespace gives software a consistent way to distinguish Pi Network
chains from one another and from other blockchain ecosystems.
For example, pinet:mainnet identifies Pi Network Mainnet, while
pinet:testnet identifies Pi Network Testnet.
Rationale
Pi Network is a Layer 1 blockchain with distinct Mainnet and Testnet
environments.
Although its protocol and transaction model are derived from Stellar, Pi
Network has its own governance, validator set, native asset, public
infrastructure, and network passphrases.
Reusing the stellar namespace would therefore obscure the operational and
trust boundaries between the ecosystems and could cause software to resolve a
Pi chain as a Stellar network.
The pinet namespace keeps those boundaries explicit while retaining short,
human-readable chain references.
Each reference maps deterministically to an exact, case-sensitive Pi Network
passphrase exposed by the network’s Horizon API.
Wallets, applications, and cross-chain systems can use that mapping to verify
which Pi Network environment they are connected to before processing accounts,
assets, or transactions.
The mapping and its resolution procedure are defined in the
Pi Network CAIP-2 Profile.
Governance
Pi Network protocol and public-network upgrades are coordinated by the Pi Core Team and communicated through official Pi Network announcements and developer documentation. Node operators and infrastructure providers adopt the corresponding software and configuration updates for each network.
Changes to this namespace follow the review process of the Chain Agnostic
namespaces repository.
Change controllers for this namespace are members of the PiCoreTeam GitHub
organization.
While that organization’s membership is not public, updates will be accepted
from the following GitHub users: @hklee93, @aurelienshz, and @kokkalis.
Any listed change controller may update this list.
A new chain reference should be added by a change controller only when Pi
Network exposes a stable environment with a distinct network passphrase and
deterministic resolution mechanics.
Temporary or private deployments should not be assigned a shared reference
unless they become persistent interoperability targets.
References
- Pi Network CAIP-2 Profile - Defines Pi Network chain identifiers and their resolution mechanics.
- CAIP-2 - Defines the chain-agnostic blockchain identifier format.
- Pi Whitepaper - Introduces the Pi Network protocol, ecosystem, and governance model.
- Pi Developer Documentation - Documents Pi Network application and blockchain integration.
- Pi Network Updates - Publishes protocol and public-network upgrade announcements.
Copyright
Copyright and related rights waived via CC0.
Citation
Please cite this document as:
Hakkyung Lee, "namespaces/pinet: Pi Network Ecosystem [DRAFT]," Chain Agnostic Namespaces, pinet, August 2026 / . [Online serial]. Available: https://github.com/ChainAgnostic/namespaces/pinet.md