Solana chain ID, RPC URL and network config
Last updated:
Solana network identifiers
| Identifier | Value | Source |
|---|---|---|
| Chain ID | NoneSolana is not an EVM network; the CAIP-2 spec identifies a cluster by its genesis hash. | CAIP-2 solana namespace |
| Cluster | MainnetSolana-run public endpoint: api.mainnet.solana.com. | Solana docs: clusters and public RPC endpoints |
| Genesis hash | 5eykt4UsFv8P8NJdTREpY1vzqKqZKvdpKuc147dw2N9dWhat getGenesisHash returns on Mainnet (checked on api.mainnet.solana.com, 23.09.2026). The CAIP-2 spec gives its first 32 characters. | CAIP-2 solana namespace · Solana docs: getGenesisHash method |
| CAIP-2 ID | solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdpThe chain identifier multichain wallets and WalletConnect use. | CAIP-2 solana namespace |
Tools that expect an EVM chain ID do not apply to Solana; multichain wallets use the CAIP-2 ID solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp instead.
Solana RPC URLs
| Triport RPC URL (header auth) | https://triport.io/sol |
|---|---|
| Triport RPC URL (keyed) | https://triport.io/r/<API_KEY>/sol |
| Triport WebSocket URL (keyed) | wss://triport.io/ws/sol/<API_KEY> |
| Required scope | solana:rpc |
| Public RPC by Solana | https://api.mainnet.solana.comRate-limited public endpoint: 100 requests per 10 seconds per IP, and "not intended for production applications". Solana docs: clusters and public RPC endpoints |
Public-endpoint limits are as each operator publishes them, checked 23 September 2026.
Plans and per-category rate limits: pricing. Network overview: Solana RPC; method reference: Solana documentation.
Verify you are on Solana mainnet
Call getGenesisHash first. It must return 5eykt4UsFv8P8NJdTREpY1vzqKqZKvdpKuc147dw2N9d — any other value means the endpoint serves a different network.
curl https://triport.io/sol \
-H "x-token: <API_KEY>" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"getGenesisHash"}'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 Solana chain ID?
- Solana has no EVM-style numeric chain ID. A cluster is identified by its genesis hash: Mainnet returns 5eykt4UsFv8P8NJdTREpY1vzqKqZKvdpKuc147dw2N9d from getGenesisHash. Wallet standards use the CAIP-2 ID solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp, the first 32 characters of that hash.
- What is the Solana RPC URL?
- On Triport: https://triport.io/sol with your API key in the x-token header, or https://triport.io/r/<API_KEY>/sol where a header is impossible (wallets, config files). WebSocket: wss://triport.io/ws/sol. Solana also runs a public endpoint, https://api.mainnet.solana.com; it is rate-limited, and the limits its operator publishes are cited in the RPC URL table.
- Can I add Solana to MetaMask with wallet_addEthereumChain?
- No. wallet_addEthereumChain registers EVM networks by chain ID, and Solana is not an EVM network. Use a Solana wallet or SDK and point it at the RPC URL above.
- 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.