Resumen
Solana Devnet is a test network for developers to deploy and test programs before mainnet. This page covers the public devnet RPC endpoint, chain settings, faucet for devnet SOL, common RPC methods, and how to choose a reliable provider for consistent testing.
Solana Devnet RPC Decision Checklist
Before using a devnet RPC endpoint, review these criteria to avoid common issues:
| Criterion | What to Check | Why It Matters |
|---|---|---|
| Rate limits | Shared public endpoints have per-IP limits; check documentation or consider private endpoints | Prevent throttling during testing or program deployment |
| WebSocket support | Confirm the endpoint offers wss:// for subscription methods (e.g., onProgramAccountChange) | Needed for real-time monitoring and event-driven dApps |
| Faucet availability | Ensure the network has a working faucet for devnet SOL | Without test tokens you cannot pay for transaction fees or deploy programs |
| Archive data depth | Some endpoints only keep recent state; archive endpoints provide historical data | Required for debugging past transactions and building block explorers |
| Uptime and reliability | Public endpoints may go offline or degrade; check provider SLAs | Intermittent failures waste developer time and break CI/CD pipelines |
What Is Solana Devnet?
Solana Devnet (developer network) is a test cluster that simulates the mainnet environment. It uses the same validator software, program deployment process, and runtime as mainnet, but runs on test SOL that carries no real value. Developers use devnet to:
- Deploy and iterate on Solana programs (smart contracts)
- Test client integrations and transaction flow
- Validate program performance under simulated network conditions
- Run CI/CD pipelines without risking real funds
The official public devnet endpoint operated by Solana Labs is https://api.devnet.solana.com. However, this shared endpoint has significant rate limits and is not recommended for heavy testing or production applications. Many developers switch to a private RPC provider for more consistent throughput.
Solana Devnet Endpoint and Chain Settings
| Setting | Value |
|---|---|
| Network name | Solana Devnet |
| RPC URL | https://api.devnet.solana.com (public) |
| WebSocket URL | wss://api.devnet.solana.com (public) |
| Chain ID | 901 (note: some explorers use 2305 for customs; confirm with your tool) |
| Native currency | Devnet SOL (test token, no real value) |
| Block time | ~400ms |
| Faucet | https://faucet.solana.com/ (use wallet address) |
To verify you're connected, run a curl request:
curl -X POST https://api.devnet.solana.com -H "Content-Type: application/json" -d '{
"jsonrpc": "2.0",
"id": 1,
"method": "getVersion"
}'
Expected response:
{
"jsonrpc": "2.0",
"result": {
"feature-set": 432857830,
"solana-core": "2.2.7"
},
"id": 1
}
Getting Devnet SOL from the Faucet
To cover transaction fees and rent on devnet, you need devnet SOL. Use the official Solana faucet:
- Visit https://faucet.solana.com/
- Enter your devnet wallet address (e.g., from Solana CLI or Phantom)
- Click "Request SOL"
The faucet typically dispenses 1–2 devnet SOL per request, enough for moderate testing. If you need more, run the request multiple times or use a private faucet.
Alternatively, use the CLI:
solana airdrop 1 <YOUR_ADDRESS> --url https://api.devnet.solana.com
Common RPC Methods for Devnet
Solana's JSON-RPC API offers methods for reading state, sending transactions, and subscribing to events. Here are the most frequently used on devnet:
Get Account Balance
curl https://api.devnet.solana.com -X POST -H "Content-Type: application/json" -d '
{
"jsonrpc": "2.0",
"id": 1,
"method": "getBalance",
"params": ["<WALLET_ADDRESS>"]
}'
Request Airdrop (devnet only)
curl https://api.devnet.solana.com -X POST -H "Content-Type: application/json" -d '
{
"jsonrpc": "2.0",
"id": 1,
"method": "requestAirdrop",
"params": ["<WALLET_ADDRESS>", 1000000000] // 1 SOL in lamports
}'
Send Transaction
// Using @solana/web3.js
import { Connection, clusterApiUrl } from "@solana/web3.js";
const connection = new Connection("https://api.devnet.solana.com");
// or use a private endpoint
// const connection = new Connection("https://devnet.solana.rpc.onfinality.io");
async function sendTx() {
const tx = /* build transaction */;
const signature = await connection.sendTransaction(tx);
console.log("Transaction sent:", signature);
}
Debugging Tips for Devnet
- Use
getSignatureStatusesto check if a transaction confirmed. - Simulate first with
simulateTransactionbefore sending to catch errors offline. - Monitor logs with
onLogssubscription to track program output. - Check block explorers like Solscan (devnet) to visualise transactions.
Common devnet errors:
- "Account not found" – The faucet hasn't funded it yet, or you're querying a non-existent account.
- "Blockhash not found" – The recent blockhash expired; fetch a fresh one before sending.
- "Transaction simulation failed" – Check program ID, account data, or rent exemption.
Public vs Private Devnet RPC Endpoints
Using the public endpoint (api.devnet.solana.com) is convenient but has limitations:
| Aspect | Public Endpoint | Private Endpoint |
|---|---|---|
| Rate limit | ~100 req/10s | Higher or custom tiers |
| Reliability | Shared, can be unstable | Dedicated nodes, better uptime |
| WebSocket | Supported | Supported, often more stable |
| Archive data | Limited | Full archive available |
| Cost | Free | Usage-based or subscription |
For active development, CI/CD pipelines, or teams testing concurrently, consider a dedicated devnet RPC provider. OnFinality offers Solana devnet endpoints with higher rate limits and consistent uptime — see our Solana Devnet network page and RPC pricing for details.
Choosing a Devnet RPC Provider
When evaluating providers for Solana devnet, ask:
- Does the endpoint support Websocket subscriptions?
- What are the rate limits per API key?
- Is there a free tier or trial?
- Can you upgrade to a dedicated node if needed?
- Does the provider offer archive data?
- Is there 24/7 support or a status page?
Review our guide on how to choose an RPC provider for a broader checklist that applies to test networks.
Frequently Asked Questions
Q: What is the Solana devnet RPC URL?
A: The public URL is https://api.devnet.solana.com. Private providers may offer custom endpoints like https://devnet.solana.rpc.onfinality.io.
Q: How do I add Solana devnet to my wallet? A: In Phantom or Solflare, switch to Developer Mode and select "Devnet" from the network dropdown. For manual addition, use the RPC URL and chain ID 901.
Q: Can I use the same program ID on devnet and mainnet? A: Yes, program IDs are deterministic. Deploy the same program code and the ID will match across clusters.
Q: Why do my transactions fail on devnet?
A: Common reasons: insufficient devnet SOL, outdated blockhash, or incorrect account state. Use simulateTransaction to debug.
Q: Is devnet SOL real money? A: No. Devnet SOL is a test token and has no monetary value.
Key Takeaways
- Solana Devnet is essential for testing programs and client integrations before mainnet deployment.
- The public endpoint works for light use, but heavy testing benefits from a private RPC provider with higher limits and better reliability.
- Always fund your devnet wallet via the faucet and use the correct chain ID (901).
- Debug with simulation, signature statuses, and block explorers.
- For production-grade devnet access, evaluate providers like OnFinality that offer dedicated nodes and archive data.
Ready to start building? Check our supported networks for Solana devnet endpoints and find a plan that fits your workflow on our pricing page.