Scroll RPC Nodes & Endpoints

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

Dedicated Scroll RPC node vs shared endpoints

Scroll attracts teams that chose it for bytecode-level equivalence: infrastructure projects, bridges, and DeFi protocols that reuse mainnet contracts and audits unchanged. Those teams tend to run mainnet-grade tooling, steady archive reads, deep eth_getLogs backfills, and monitoring that replays historical state, and they run it against public endpoints sized for wallet traffic. The mismatch shows up as throttled backfills and gaps in monitoring.

A dedicated Scroll RPC node gives that tooling the same footing it has on mainnet: archive access as a property of the node rather than a premium tier, log windows set by client configuration, and throughput that does not depend on other tenants. On BLAZED.sh your indexer or monitor runs in a container on the node host, reading over a local socket.

Scroll RPC latency: architecture over benchmarks

Scroll's proving pipeline runs off the critical path of your reads; what your users and monitors actually experience is the RPC. A remote endpoint spends tens to low hundreds of milliseconds per call crossing the public internet. Running the code on the node host removes that path entirely: on our live Ethereum product, co-located calls complete in under 10 milliseconds, and dedicated Scroll nodes will follow the same architecture.

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

Monitoring and indexing on Scroll are read-and-logs workloads, single-credit calls almost throughout, so the credit model prices a backfill by its block count rather than by method-weight arithmetic.

Perfect for

What is Scroll?

Scroll's design goal is to match the Ethereum EVM as closely as possible at the bytecode level, which minimises surprises when porting contracts and reusing audits. It generates zk validity proofs for its batches and verifies them on Ethereum, inheriting Ethereum security while keeping fees low. For developers this means the integration is essentially an Ethereum integration with a different RPC URL and chain ID. Scroll's ecosystem leans toward DeFi and infrastructure projects that value equivalence and verifiability. The recurring theme applies here too: proving happens off-path, but your users experience the RPC, so sustained query performance for logs and state reads is what a dedicated node improves.

Scroll RPC: frequently asked questions