Optimism (OP Mainnet) RPC Nodes & Endpoints

Optimism 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.optimism.io");
const blockNumber = await provider.getBlockNumber();
console.log("Optimism block:", blockNumber);

Dedicated Optimism RPC node vs shared endpoints

Public OP Mainnet endpoints are fine for a wallet checking a balance, but Superchain-era workloads look different: portfolio apps read Optimism alongside Base and other OP-Stack chains, indexers backfill months of eth_getLogs history, and governance tooling replays proposal and vote events. Those are sustained, wide queries, precisely the shape shared endpoints throttle first, because one tenant's backfill degrades everyone else's reads.

A dedicated Optimism RPC node removes the contention. Your backfill can run at whatever rate the hardware sustains, subscriptions stay connected, and the block-range window is a client setting rather than a plan tier. BLAZED.sh takes it further by running your indexer or service in a container on the node host, so even the heaviest log query travels a local socket instead of the internet.

Optimism RPC latency: architecture over benchmarks

Optimism itself gives you two-second blocks; a remote RPC gateway adds a public-internet round trip of tens to low hundreds of milliseconds on top of every call, plus queueing when the gateway is busy. The architectural answer is to shorten the path, not to shop for a faster gateway. On our live Ethereum product, co-located containers see sub-10ms RPC because calls never leave the machine, and dedicated Optimism nodes will use the same design.

What a dedicated Optimism 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 Optimism nodes will launch on the same credit model, with the waitlist above deciding rollout priority.

Indexing OP Mainnet is mostly eth_getLogs and plain reads, which are single-credit calls, so a backfill budget can be estimated by simply counting the block ranges you plan to walk.

Perfect for

What is Optimism?

Optimism pioneered the optimistic-rollup approach and open-sourced the OP Stack that now powers Base, Blast, and dozens of other chains. Because those chains share a codebase, tooling and RPC semantics carry over cleanly, and an integration written for OP Mainnet usually ports to any Superchain member with a URL swap. Optimism posts transaction data to Ethereum and finalises through fault proofs, and its ecosystem skews toward DeFi, public-goods funding, and consumer apps. As with any rollup, the chain itself is rarely the constraint; sustained eth_getLogs ranges, trace calls, and websocket subscriptions are what expose weak RPC infrastructure, which is where a dedicated node earns its keep.

Optimism RPC: frequently asked questions