Summary
Solana RPC is the API layer that lets wallets, dApps, bots, games, and backend services read accounts, send transactions, simulate instructions, and subscribe to real-time updates on Solana. Public endpoints are useful for learning and quick tests, but production workloads usually need clearer limits, WebSocket support, monitoring, and a provider path that can scale.
Use this guide to understand which Solana RPC methods matter, how public and private endpoints differ, and what to test before relying on an endpoint for real users.
Key Takeaways
- Solana RPC lets applications query accounts, submit transactions, simulate instructions, and subscribe to logs or account changes.
- Public endpoints are best for learning and lightweight tests, not predictable production workloads.
- WebSocket subscriptions and request patterns matter more on Solana than a single block-number check.
- Compare providers by method support, Devnet access, limits, analytics, latency, and dedicated-node options.
What is Solana RPC?
Solana RPC is the interface applications use to communicate with the Solana network. It supports account reads, balance checks, transaction submission, transaction simulation, program lookups, and WebSocket subscriptions for real-time updates.
Because Solana applications often make many fast reads and subscription calls, endpoint behavior under real traffic matters. A public endpoint can be enough for a tutorial, but a production wallet, game, bot, or analytics system needs clearer limits and better operational visibility.
- Common HTTP calls include
getAccountInfo,getBalance,getProgramAccounts,simulateTransaction, andsendTransaction. - Common WebSocket flows include account, log, signature, and program subscriptions.
- Commitment levels such as
processed,confirmed, andfinalizedaffect how your app interprets state.
Solana RPC endpoint checklist
Run these checks with the same app code, wallet flow, or backend job that will use the endpoint after launch.
| Criterion | What to check | Why it matters |
|---|---|---|
| Cluster support | Mainnet, Devnet, and any test workflow your release process needs. | Testing and production should use comparable endpoint behavior. |
| Subscriptions | WebSocket reliability for accounts, logs, signatures, and programs. | Real-time apps often fail first at the subscription layer. |
| Operations | Rate limits, request analytics, error visibility, and support path. | You need to debug endpoint issues without guessing from client errors alone. |
Public vs Private Solana RPC Endpoints
Public endpoints like https://api.mainnet.solana.com are free and easy to use for development and testing. However, they impose strict rate limits (e.g., 100 requests per 10 seconds per IP) and offer no documents on availability or latency. They are not suitable for production applications with real users.
Private RPC providers offer dedicated or shared nodes with higher rate limits, lower latency, and service-level agreements (SLAs). They often provide additional features such as archive data, WebSocket support, and geographic load balancing. Choosing a private provider is a standard practice for any serious Solana project.
- Public endpoints: free, rate-limited, no support terms, best for prototyping.
- Private endpoints: paid, scalable, reliable, with support and monitoring.
- OnFinality offers both shared and dedicated Solana RPC nodes across multiple clusters.
Key Criteria for Choosing a Solana RPC Provider
When evaluating Solana RPC providers, consider the following factors to ensure your application's performance and reliability:
| Criterion | What to check | Why it matters |
|---|---|---|
| support and monitoring options | Look for providers offering consistent availability availability documents. | Downtime directly impacts user experience and can lead to lost transactions or revenue. |
| Rate Limits | Understand the maximum requests per second (RPS) allowed on each plan. | Insufficient rate limits cause request throttling and application errors. |
| Geographic Distribution | Check if the provider has endpoints in multiple regions (e.g., US, EU, Asia). | Closer endpoints reduce latency and improve transaction submission success rates. |
| WebSocket Support | Ensure the provider supports persistent WebSocket connections for real-time subscriptions. | Many dApps rely on WebSocket for live updates on accounts, transactions, and programs. |
| Archive Data Access | Does the provider offer historical state access beyond the current slot? | Archive nodes are needed for analytics, backtesting, and certain dApp features. |
| Pricing Model | Compare pay-as-you-go, monthly subscriptions, and dedicated node pricing. | Choose a model that aligns with your traffic patterns and budget. |
How to Test and Monitor Solana RPC Performance
Before committing to a provider, run benchmarks using tools like solana-bench or custom scripts. Measure latency for common methods (getBalance, getLatestBlockhash, sendTransaction) and test WebSocket subscription stability. Monitor availability and response times over several days to identify any patterns.
After deployment, continue monitoring with application performance management (APM) tools. Set up alerts for high latency or error rates. Many providers, including OnFinality, offer dashboards and API metrics to help you track performance.
- Use the Solana CLI to test endpoints:
solana balance --url <endpoint>. - Simulate transaction load with custom scripts.
- Check WebSocket reconnection behavior under network interruptions.
Getting Started with OnFinality Solana RPC
OnFinality provides reliable Solana RPC endpoints for mainnet, devnet, and testnet. With both shared and dedicated node options, you can scale from development to production seamlessly. All endpoints support HTTP and WebSocket, and dedicated nodes include full archive access.
To get started, sign up for an OnFinality account, create an API key, and choose your preferred Solana network. You can also explore the dedicated node option for maximum performance and control.
- Instant API key generation.
- Support for mainnet, devnet, and testnet.
- Dedicated nodes with customizable configurations.
- 24/7 technical support and monitoring.
Frequently Asked Questions
What is the difference between Solana RPC and Solana JSON-RPC?
Solana RPC and Solana JSON-RPC refer to the same thing: the JSON-RPC 2.0 API that allows clients to interact with the Solana blockchain. The terms are used interchangeably.
Can I use the public Solana RPC endpoint for production?
No, public endpoints (e.g., api.mainnet.solana.com) are rate-limited and have no support terms. They are intended for development and testing only. For production, use a private RPC provider like OnFinality.
What are the rate limits for Solana public RPC?
The public mainnet endpoint typically allows 100 requests per 10 seconds per IP. This is insufficient for most production applications.
Does OnFinality support Solana WebSocket subscriptions?
Yes, OnFinality Solana RPC endpoints support both HTTP and WebSocket methods, including accountSubscribe, logsSubscribe, and programSubscribe.
How do I choose between a shared and dedicated Solana RPC node?
Choose a shared node for lower cost and moderate traffic. Choose a dedicated node for more predictable resource planning, high throughput, and full control. OnFinality offers both options.
Ethereum
Solana
Polygon
Base
Arbitrum
BNB Chain
Polkadot
Optimism
