Base RPC Nodes & Endpoints

Base public RPC endpoints

Free, third-party public endpoints for reads and prototyping. They are shared and rate-limited, not run by BLAZED.sh, so use a dedicated node for production traffic.

import { JsonRpcProvider } from "ethers";

const provider = new JsonRpcProvider("https://mainnet.base.org");
const blockNumber = await provider.getBlockNumber();
console.log("Base block:", blockNumber);

Dedicated Base RPC node vs shared endpoints

The public Base endpoints above are shared by every wallet, script, and indexer that found the same URL, and Base's traffic profile makes that sharing expensive. Activity arrives in bursts: a popular mint, an on-chain social moment, or a meme token launch can multiply request volume within minutes, and shared endpoints respond by throttling exactly when your app needs headroom. If your product depends on reading Base during those spikes, you are competing for capacity with the very crowd that caused them.

A dedicated Base RPC node inverts that. The node serves only your workload, so an eth_getLogs backfill over a busy NFT contract or a websocket subscription following new blocks does not queue behind strangers' traffic. BLAZED.sh goes a step further than renting you a private endpoint: your container runs on the same machine as the node, so the request never leaves the host at all.

Base RPC latency: architecture over benchmarks

Base produces a block roughly every two seconds, and public gateways add a round trip over the public internet, typically tens to low hundreds of milliseconds depending on region and load, before your code even sees the new state. On our live Ethereum product, co-locating your code with the node keeps RPC calls under 10 milliseconds because they travel over a local socket instead of the network. Dedicated Base nodes will use the same architecture: the win comes from removing the network path, not from a faster gateway.

What a dedicated Base node costs

BLAZED.sh prices node access in per-request credits granted monthly by your subscription, with a deliberately narrow weight spread: most RPC methods cost 1 credit, a few heavy operations like txpool_content and the trace_replay methods cost 4, and responses over 100KB add 50 credits per MB. The Beta plan is €75 per month with 1M credits, 1 container and 2 scripts; Beta XL is €249 per month with 5M credits, 3 containers and 4 scripts; Enterprise plans add private nodes and archive access. These are the live Ethereum plans today, and pricing is still being finalized. Dedicated Base nodes will launch on the same credit model, with the waitlist above deciding rollout priority.

For a consumer dApp on Base that mostly issues plain reads and log queries, nearly every call is a single credit, so a monthly allowance maps almost one to one to request count.

Perfect for

What is Base?

Base launched in 2023 as an OP-Stack rollup incubated by Coinbase. Because it inherits Ethereum's security and uses ETH for gas, most Ethereum tooling (ethers, viem, Foundry, The Graph) works unchanged: you just point it at a Base RPC URL with chain ID 8453. Base sequences transactions with roughly two-second block times and posts data to Ethereum, so the practical bottleneck for indexers, bots, and high-traffic dApps is RPC throughput and latency rather than the chain itself. Public endpoints are fine for reads and prototyping, but production workloads that hammer eth_getLogs, trace calls, or the mempool benefit from a dedicated node close to your compute.

Base RPC: frequently asked questions