Blast RPC Nodes & Endpoints

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

Dedicated Blast RPC node vs shared endpoints

Blast's native yield creates data shapes other L2s do not have: balances rebase, rewards accrue, and points programs run claim windows that concentrate traffic into short bursts. Dashboards and integrators need precise historical logs to establish what a balance was and when it changed, and claim-window spikes hit public endpoints exactly when that accuracy matters most. Shared RPC answers with throttling and stale reads.

A dedicated Blast RPC node makes rebasing accounting tractable: historical log queries run at hardware speed, claim-day load is your capacity decision rather than a shared fate, and websocket subscriptions stay attached through the spike. On BLAZED.sh your accounting worker runs in a container on the node host, so the heavy queries stay on a local socket.

Blast RPC latency: architecture over benchmarks

Blast produces roughly two-second blocks; the round trip to a remote gateway adds tens to low hundreds of milliseconds per call on top, and claim-window congestion adds queueing after that. The fix is the same architecture we run in production on Ethereum: co-locate the code with the node so calls travel a local socket and complete in under 10 milliseconds. Dedicated Blast nodes will use that design.

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

Yield and points accounting is log-query work, single-credit calls, so reconciling a month of rebasing history prices out as the number of ranges you walk, not a method-weight table.

Perfect for

What is Blast?

Blast launched as an OP-Stack rollup with an unusual twist: native yield on ETH and stablecoins, sourced from ETH staking and RWA protocols, which shaped an ecosystem oriented around DeFi, points, and rewards mechanics. Under the hood it behaves like other OP-Stack chains: EVM execution, ETH gas, data posted to Ethereum, and standard tooling that works after a URL swap to chain ID 81457. The yield accounting introduces app patterns (claiming, rebasing balances) that indexers and dashboards must track precisely, which puts a premium on reliable historical log queries. High-traffic reward campaigns are exactly the moments public RPCs buckle, so a dedicated node keeps claim flows and analytics responsive.

Blast RPC: frequently asked questions