Solana RPC Nodes & Endpoints

Solana mainnet-beta RPC endpoints you can use right now

Third-party endpoints, free and shared. Solana's own documentation is explicit that the public mainnet-beta endpoint is not intended for production, and it enforces that with hard caps on scans and subscriptions.

import { Connection } from "@solana/web3.js";

const connection = new Connection("https://api.mainnet-beta.solana.com", "confirmed");
const slot = await connection.getSlot();
console.log("Solana slot:", slot);

Commitment levels, and the two methods that get you rate limited

Solana has no equivalent of Ethereum's block tags. Instead every read carries a commitment level, and picking the wrong one is the most common source of behaviour that looks like an RPC bug. Processed returns the node's most recent view and can be rolled back. Confirmed means a supermajority voted on the slot and is what most applications should actually use. Finalized is rooted and irreversible, and it lags by roughly thirty slots, which is an eternity for a trading loop and exactly right for crediting a deposit. Reading at processed and treating the answer as settled is how transactions appear to succeed and then vanish.

Two methods account for most of the rate limiting people hit. getProgramAccounts scans every account owned by a program, and against a busy program that is an enormous amount of data to filter server-side, which is why public endpoints truncate it, reject it, or ban you for it. Heavy websocket subscription counts are the other: account and slot subscriptions fan out cheaply from your side and expensively from the node's. Both are ordinary requirements for an indexer or a market maker, and both are precisely what a shared endpoint is built to refuse, which is why Solana teams reach for dedicated capacity earlier in their life than EVM teams do.

Why Solana workloads outgrow shared RPC faster than EVM ones

Solana's public mainnet-beta endpoint is explicitly not meant for production, and it shows: getProgramAccounts scans over busy programs get rejected or truncated, websocket fan-out is capped, and rate limits arrive quickly. Serious Solana workloads, whether trading systems, indexers, or consumer apps at scale, outgrow shared RPC faster than on any EVM chain, because the chain moves at 400 millisecond slots and the common methods are heavier.

A dedicated Solana RPC node changes what is possible rather than just how fast: full getProgramAccounts scans, as many account and slot subscriptions as your architecture wants, and transaction submission that is not queued behind a public crowd. On BLAZED.sh the model will match our Ethereum product: your bot or indexer runs on the node host and reads over a local socket.

400ms slots leave no room for a round trip

With 400 millisecond slots, Solana punishes network distance more than any EVM chain: a public-internet round trip of tens to low hundreds of milliseconds can span multiple slots before your code reacts. Co-location is the structural answer. On our live Ethereum product, calls from the co-located container complete in under 10 milliseconds, and dedicated Solana RPC will apply the same architecture to the chain where the gap between local and remote is worth the most.

What dedicated Solana node hosting will cost

BLAZED.sh prices node access in per-request credits granted monthly by your subscription, with a deliberately narrow weight spread: most RPC methods cost a single credit, and only a handful of heavy operations cost more. Dedicated Solana nodes will launch on the same credit model, with the waitlist deciding rollout priority.

Solana's chatty method mix of constant polling and subscriptions is exactly where per-method weighted billing hurts most, and where a narrow credit spread keeps the forecast down to counting calls.

Perfect for

What is Solana?

Solana uses a single global state with parallel execution (Sealevel) and a proof-of-history clock to reach very high throughput and sub-second slot times. Its RPC surface differs entirely from Ethereum: methods like getSlot, getAccountInfo, getProgramAccounts, and sendTransaction, plus websocket account and slot subscriptions, and there is no EVM chain ID, so you select the cluster (mainnet-beta) by URL. Because block space is abundant but contention is real, the competitive edge for DEX trading, sniping, and market making comes from low-latency transaction submission and staked-connection priority. Heavy getProgramAccounts scans and websocket fan-out also strain public endpoints quickly, which is why serious Solana teams run dedicated RPC close to their bots and indexers.

Solana RPC: frequently asked questions