Stellar chain ID, RPC URL and network config
Last updated:
Stellar network identifiers
| Identifier | Value | Source |
|---|---|---|
| Chain ID | NoneStellar is not an EVM network; transactions are signed for a network passphrase. | Stellar docs: networks |
| Network passphrase | Public Global Stellar Network ; September 2015Returned by getNetwork. A transaction signed for another passphrase is invalid on Mainnet. | Stellar docs: networks |
| CAIP-2 ID | stellar:pubnetThe chain identifier multichain wallets and WalletConnect use. | CAIP-2 stellar namespace |
Tools that expect an EVM chain ID do not apply to Stellar; multichain wallets use the CAIP-2 ID stellar:pubnet instead.
Stellar RPC URLs
| Triport RPC URL (header auth) | https://triport.io/rpc/stellar |
|---|---|
| Triport RPC URL (keyed) | https://triport.io/r/<API_KEY>/stellar |
| Required scope | stellar:rpc |
| Network-run public RPC | The Stellar Development Foundation hosts no public Mainnet RPC endpoint: its docs list third-party providers for Mainnet RPC and Horizon. Stellar docs: networks |
Public-endpoint limits are as each operator publishes them, checked 23 September 2026.
Plans and per-category rate limits: pricing. Endpoint and plans: Stellar RPC endpoint; method reference: Stellar RPC API reference.
Stellar testnets
| Network | Identifier | Official RPC | Faucet | Explorer | Status | Source |
|---|---|---|---|---|---|---|
| Testnet | Network passphrase: Test SDF Network ; September 2015 | https://soroban-testnet.stellar.org | Friendbot | — | active | Stellar docs: networks · checked 2026-10-24 |
| Futurenet | Network passphrase: Test SDF Future Network ; October 2022 | https://rpc-futurenet.stellar.org | Friendbot (Futurenet) | — | active | Stellar docs: networks · checked 2026-10-24 |
Testnet: SDF-run network that mirrors Mainnet; Horizon at horizon-testnet.stellar.org. It resets on a regular cadence — the next reset is 16 December 2026. Futurenet: Bleeding-edge features before release; resets whenever necessary. Triport serves mainnet only. These values are for switching your config; they are not Triport endpoints.
Verify you are on Stellar mainnet
Call getNetwork first. It must return Public Global Stellar Network ; September 2015 — any other value means the endpoint serves a different network.
curl https://triport.io/rpc/stellar \
-H "x-token: <API_KEY>" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"getNetwork","params":{}}'Connected to a testnet by mistake? The same call answers Test SDF Network ; September 2015 on Testnet and Test SDF Future Network ; October 2022 on Futurenet.
Sources: the chain's own documentation and the CAIP-2 namespace specs cited in the tables above; EVM chain IDs come from Triport's chain registry and match them.
FAQ
- What is the Stellar chain ID?
- Stellar has no numeric chain ID. Mainnet is identified by its network passphrase, "Public Global Stellar Network ; September 2015", which every transaction signature commits to. getNetwork returns it; the CAIP-2 ID is stellar:pubnet.
- What is the Stellar RPC URL?
- On Triport: https://triport.io/rpc/stellar with your API key in the x-token header, or https://triport.io/r/<API_KEY>/stellar where a header is impossible (wallets, config files).
- Can I add Stellar to MetaMask with wallet_addEthereumChain?
- No. wallet_addEthereumChain registers EVM networks by chain ID, and Stellar is not an EVM network. Use a Stellar wallet or SDK and point it at the RPC URL above.
- Which Stellar testnet should I use?
- Testnet: SDF-run network that mirrors Mainnet; Horizon at horizon-testnet.stellar.org. It resets on a regular cadence — the next reset is 16 December 2026. Futurenet: Bleeding-edge features before release; resets whenever necessary. Triport serves Stellar mainnet only, so test work goes to the network's own testnet endpoint.
- Is my API key sent to Triport when I use this page?
- No. Snippets are generated in your browser: the key is never submitted, never stored and never written into the page URL, which is why this page has no shareable link.