What Do You Need for Solana RPC Access?

Solana RPC Access decision checklist

Before integrating Solana RPC, evaluate these criteria:

Use this checklist when comparing providers, including OnFinality's Solana RPC service and dedicated node options.

Understanding Solana RPC Access

Solana is a high-performance blockchain designed for decentralized applications (dApps) and DeFi. To interact with the network, you need an RPC (Remote Procedure Call) endpoint. This endpoint acts as a gateway to submit transactions, query account balances, and fetch block data. Choosing the right access method is crucial for your dApp's reliability and user experience.

Types of Solana RPC Access

Public RPC Endpoints

Public endpoints (e.g., api.mainnet-beta.solana.com) are provided by the Solana Foundation and other community operators. They are free but have strict rate limits (typically 100 requests per 40 seconds) and no reliability expectations. Suitable for testing and low-traffic applications.

Shared Private RPC Endpoints

Many RPC providers offer shared private endpoints with API-key authentication. These provide higher rate limits (commonly 10-50 RPS) and better reliability than public endpoints. They are ideal for small to medium dApps. OnFinality's shared RPC API service for Solana includes automatic failover and caching.

Dedicated Nodes

For high-throughput applications, a dedicated Solana node gives you full control over resources. You can configure rate limits from zero to hundreds of thousands of requests per second. OnFinality provides dedicated Solana nodes with customizable specs.

Obtaining a Solana RPC Endpoint

To get started, choose a provider and sign up. Most providers issue an API key. For example, with OnFinality:

1. Create an account at onfinality.io.
2. Navigate to Networks and select Solana (mainnet, devnet, or testnet).
3. Generate an API key from the dashboard.
4. Use the provided endpoint URL in your application.

Example: Making a Solana RPC Call with cURL

curl https://solana-rpc.onfinality.io/your-api-key \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1, "method":"getBlockHeight"}'

Replace your-api-key with your actual key. The response returns the current block height.

Authentication and Rate Limits

Private endpoints require authentication, usually via API key in the header or query string. Always store keys securely (environment variables, secret managers). Rate limits vary by provider and plan. Check the pricing page for details: OnFinality RPC pricing.

WebSocket Support

For real-time updates (e.g., slot notifications, account changes), you need WebSocket endpoints. Most providers offer wss:// URLs. Example subscription:

const WebSocket = require('ws');
const ws = new WebSocket('wss://solana-rpc.onfinality.io/your-api-key');

ws.on('open', function open() {
  ws.send(JSON.stringify({
    jsonrpc: '2.0',
    id: 1,
    method: 'slotSubscribe',
    params: []
  }));
});

ws.on('message', function incoming(data) {
  console.log(JSON.parse(data));
});

Network Environments

Solana has three main networks:

• Mainnet Beta: Production environment for live dApps.
• Devnet: Test environment for developers; tokens are free from faucets.
• Testnet: Used for validators and infrastructure testing; tokens are also free.

Ensure your RPC provider supports all three if you plan to develop and test. OnFinality offers endpoints for Solana devnet in addition to mainnet.

Common Pitfalls and Troubleshooting

• Rate limit exceeded: If you get HTTP 429 errors, upgrade your plan or implement request queuing.
• Connection timeouts: Check your network latency or switch to a provider with edge caching.
• Incorrect network: Double-check you're using the right endpoint for mainnet/devnet/testnet.
• API key exposed: Rotate keys immediately if leaked; use environment variables.
• Missing archive data: For applications needing historical states, ensure your plan includes archive node access.

When to Use Shared vs Dedicated

Key Takeaways

• Understand your application's throughput and latency requirements before choosing an access method.
• Always use authenticated private endpoints in production to avoid rate limits and security issues.
• Test your integration on devnet before deploying to mainnet.
• Monitor your RPC usage to anticipate when to scale.
• OnFinality provides both shared and dedicated Solana RPC access with transparent pricing.

Frequently Asked Questions

1. Can I use Solana public RPC for production? Public RPC has low rate limits and no SLA. It's not recommended for production. Use a private shared or dedicated node.

2. How do I get Solana devnet tokens? Visit the Solana devnet faucet (e.g., https://faucet.solana.com/) and enter your wallet address.

3. What is the main difference between devnet and testnet? Devnet is for dApp development; testnet is for validator and network testing. Both use fake SOL.

4. Does OnFinality support Solana archive requests? Yes, archive access is available on dedicated plans. Check the network page for details.

5. How can I monitor my RPC usage? Most providers, including OnFinality, offer a dashboard with real-time analytics and usage logs.