Solana RPC endpoints, rate limits and chain ids
A reference for developers and anyone configuring a wallet or tool: the public endpoints, what their headers allowed on the night we checked, and the identifiers that stand in for an EVM chain id.
Solana's public RPC endpoints are https://api.mainnet.solana.com (the older api.mainnet-beta.solana.com still answers), https://api.devnet.solana.com and https://api.testnet.solana.com, with WebSocket on the same hosts over wss://. Solana has no EVM-style numeric chain id: a cluster is identified by its genesis hash, which for mainnet is 5eykt4UsFv8P8NJdTREpY1vzqKqZKvdpKuc147dw2N9d (read with getGenesisHash on 10 November 2026); wallets use solana:mainnet, CAIP-2 uses the hash's first 32 characters, and bridges assign their own numbers.
Every Solana app talks to the network through an RPC node: a server that keeps up with the chain, answers questions such as “what is this account’s balance?” and forwards transactions to the leaders. Solana runs three public clusters (separate networks with separate validators and separate SOL), each with a free public endpoint.
Public endpoints
| Cluster | HTTP endpoint | WebSocket | What it is for | Genesis hash (read with getGenesisHash) |
|---|---|---|---|---|
| Mainnet | https://api.mainnet.solana.com |
wss://api.mainnet.solana.com |
real SOL, real apps | 5eykt4UsFv8P8NJdTREpY1vzqKqZKvdpKuc147dw2N9d |
| Mainnet (older name) | https://api.mainnet-beta.solana.com |
wss://api.mainnet-beta.solana.com |
the same cluster | same |
| Devnet | https://api.devnet.solana.com |
wss://api.devnet.solana.com |
app testing; free test SOL from the faucet | EtWTRABZaYq6iMfeYKouRu166VU2xqa1wcaWoxPkrZBG |
| Testnet | https://api.testnet.solana.com |
wss://api.testnet.solana.com |
validator and upgrade testing | 4uhcVJyU9pJkvQyS88uRDiswHXSCkY3zQawwpjk2NsNY |
Endpoints are from Solana’s docs; the genesis hashes are what each endpoint returned on 10 November 2026. Devnet and testnet SOL has no value, and either network can be reset. Testnet usually runs newer software than mainnet: on that date mainnet and devnet reported the same feature set and testnet a different one.
The docs also list gossip entrypoints for people running nodes: entrypoint.mainnet.solana.com:8001, entrypoint.devnet.solana.com:8001 and entrypoint.testnet.solana.com:8001. A local test validator answers on http://localhost:8899, with WebSocket on ws://localhost:8900.
Rate limits: documented and served
| Limit, per IP | Docs say | Headers said on 10 Nov 2026 |
|---|---|---|
| Requests per 10 seconds | 100 | 250 (x-ratelimit-rps-limit) |
| Requests per 10 seconds for one method | 40 | 150 (x-ratelimit-method-limit) |
| Concurrent connections | 40 | 40 (x-ratelimit-conn-limit) |
| New connections per 10 seconds | 40 | 40 (x-ratelimit-connrate-limit) |
| Data per 30 seconds | 100 MB | not shown |
| WebSocket subscriptions | not stated | 5 (x-ratelimit-pubsub-limit) |
Some heavy methods have tighter limits of their own: on mainnet, the seventh getBlock call within 10 seconds was refused with a 429 and retry-after: 10. The docs warn that the limits “are subject to change” and that the public endpoints “are not intended for production applications”. A 429 means you are over the limit (wait for the Retry-After time); a 403 means your IP or site has been blocked.
Two other habits of the public endpoints worth knowing: requests from some cloud networks are refused outright, and full blocks are large (2 to 4.6 MB of JSON each when we sampled them). For anything beyond light use, the docs point to private RPC providers.
What “chain id” means on Solana
On Ethereum and the networks built like it, every chain has a number (Ethereum 1, Base 8453) that wallets put inside each signed transaction so it cannot be replayed on another chain. Solana has no such number. A Solana transaction is tied to one network by its recent blockhash, which only exists on that network. When a tool asks for a “Solana chain id”, it means one of these:
| Where you meet it | Identifier for mainnet | Source |
|---|---|---|
| The network itself | genesis hash 5eykt4UsFv8P8NJdTREpY1vzqKqZKvdpKuc147dw2N9d |
getGenesisHash |
| Wallets (Wallet Standard) | solana:mainnet (also solana:devnet, solana:testnet, solana:localnet) |
wallet-standard |
| Cross-chain standards (CAIP-2) | solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp (the genesis hash cut to 32 characters) |
CAIP-2 Solana namespace |
| Wormhole | 1 |
Wormhole SDK |
| LI.FI | 1151111081099710 |
LI.FI chains API |
| Relay | 792703809 |
Relay chains API |
The bridge numbers are each company’s own label, not something Solana defines, and they differ from each other. By the same CAIP-2 rule, devnet is solana:EtWTRABZaYq6iMfeYKouRu166VU2xqa1 and testnet solana:4uhcVJyU9pJkvQyS88uRDiswHXSCkY3z.
Adding Solana to an Ethereum wallet
You cannot add Solana to an EVM wallet as a “custom network” with an RPC URL and chain id, because Solana is not an EVM chain. Wallets that support Solana do it as a separate account type. Our guide on adding Solana to MetaMask covers that case.
Getting test SOL
- Web faucet: faucet.solana.com for devnet and testnet.
- CLI:
solana config set --url devnet, thensolana airdrop 2. The docs limit devnet airdrops to 5 SOL per request and suggest the web faucet if the CLI is rate-limited.
Test SOL is only for testing. Anyone offering to sell devnet or testnet SOL is selling something worthless.
What this means for you
If you are configuring a tool: use https://api.mainnet.solana.com for light reads, a provider for anything heavy, and the genesis hash (or solana:mainnet in a wallet) wherever a “chain id” is asked for. If you are a holder and a website asks you to “switch network” by adding a Solana RPC to an Ethereum wallet, it is either confused or a trick; check the official links first.
Questions people ask
What is the Solana chain id?
Solana has no numeric chain id like Ethereum's (1) or Base's (8453). A Solana network is identified by its genesis hash; mainnet's is 5eykt4UsFv8P8NJdTREpY1vzqKqZKvdpKuc147dw2N9d. Wallets use the label solana:mainnet, the CAIP-2 standard uses solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp, and bridges use their own numbers, such as 1 in Wormhole or 1151111081099710 in LI.FI.
What is the Solana mainnet RPC URL?
https://api.mainnet.solana.com, the URL Solana's docs now list; https://api.mainnet-beta.solana.com reached the same nodes and returned the same genesis hash on 10 November 2026. WebSocket subscriptions use wss:// on the same host.
Is there a free Solana RPC?
Yes, the public endpoints are free and need no key, but they are rate-limited and not meant for production. On 10 November 2026 their headers allowed 250 requests per 10 seconds per IP and 40 connections; the docs list stricter figures. Apps that need reliability use a paid provider or their own node.
How do I get devnet or testnet SOL?
From the web faucet at faucet.solana.com, or with the CLI command solana airdrop on devnet, which the docs limit to 5 SOL per request. Devnet and testnet SOL has no value and those networks can be reset.
What is the difference between mainnet-beta and mainnet?
Only the name. Solana's main network was called mainnet-beta for years, and tools still use that label; the docs now say mainnet and list api.mainnet.solana.com. Both hostnames served the same cluster when we checked.
Sources
- Solana docs: clusters and public RPC endpoints (docs source)
- Solana docs: RPC overview (cluster endpoints, commitment)
- Solana docs: Solana CLI basics (devnet airdrop limit of 5 SOL per request)
- Solana RPC: getGenesisHash
- ChainAgnostic CAIP-2 namespace for Solana
- Wallet Standard: Solana chain identifiers (solana:mainnet, solana:devnet, ...)
- Wormhole SDK: ChainIDSolana = 1
- LI.FI API: chains (Solana id 1151111081099710)
- Relay API: chains (Solana id 792703809)
- Solana Faucet