Blast RPC Nodes & Endpoints

Blast RPC URLs you can use right now

Third-party endpoints, free and shared. Blast accounting workloads lean hard on historical log queries, which is the first thing a public endpoint refuses to serve at the range you want.

import { JsonRpcProvider } from "ethers";

const provider = new JsonRpcProvider("https://rpc.blast.io");
const blockNumber = await provider.getBlockNumber();
console.log("Blast block:", blockNumber);

Native yield means a balance you read twice can differ

Blast pays yield on ETH and on its native stablecoin at the protocol level, and the default way it delivers that yield is rebasing: balances grow on their own, without a transfer, without an event, and without anything your indexer would normally treat as a state change. That breaks the assumption almost every EVM integration is built on, which is that a balance only moves when a Transfer log says it moved. Cache a balance on Blast and it is stale by the time you read it back, and reconstructing an account's history purely from Transfer events will not add up to its current balance.

There are two ways through, and the choice belongs to the contract rather than to you. Accounts and contracts can be configured for a non-rebasing yield mode where the balance stays fixed and yield accrues claimably instead, which restores the familiar event-driven model. Where rebasing is in play, treat balanceOf as the only source of truth and read it at the block you care about rather than deriving it, and expect any point-in-time accounting job to need archive-style historical reads instead of an event replay. That last requirement is the one that surprises budgets, because it turns a cheap log walk into a sequence of historical state reads.

Where shared Blast endpoints stop being enough

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 is a distance problem

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 dedicated Blast 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 Blast nodes will launch on the same credit model, with the waitlist 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