Linea RPC Nodes & Endpoints

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

Dedicated Linea RPC node vs shared endpoints

Linea's MetaMask distribution means its public endpoints absorb some of the most bursty retail traffic in the EVM world: a quest campaign, an airdrop checker, or a featured dApp can multiply request volume in an afternoon. Shared endpoints spread that pain across every tenant, so your app slows down because someone else's campaign went viral. If your Linea product has traffic spikes of its own, you are exposed twice.

A dedicated Linea RPC node isolates you from the crowd. Your quest backend, indexer, or wallet API gets the node's full capacity during exactly the windows when usage peaks, and eth_getLogs ranges stay a configuration choice rather than a plan restriction. On BLAZED.sh the workload itself runs on the node host in a container, so reads travel a local socket instead of the public internet.

Linea RPC latency: architecture over benchmarks

Linea behaves like mainnet from a tooling perspective, and it inherits the same RPC physics: a remote gateway adds tens to low hundreds of milliseconds of public-internet round trip to every call, before any queueing. The structural fix is proximity. On our live Ethereum product, co-located containers see sub-10ms calls over a local socket, and dedicated Linea nodes will ship on the same architecture.

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

Retail-facing Linea apps are read-dominated, and reads cost one credit each, so scaling from a quiet week to a campaign week changes the count, not the price per call.

Perfect for

What is Linea?

Linea aims for full EVM-equivalence using a zk proof system, so existing Ethereum contracts and tooling generally work without modification, a meaningful difference from zkEVMs that require special compilation. It benefits from Consensys' ecosystem reach through MetaMask and developer tooling, which drives real end-user traffic to Linea RPC endpoints. Batches are proven and verified on Ethereum for validity-based security, and gas remains ETH-denominated. Because the developer experience mirrors mainnet, teams often extend an existing Ethereum integration to Linea; the practical scaling limit then becomes RPC capacity for logs, traces, and subscriptions under growing usage, which a dedicated node addresses directly.

Linea RPC: frequently asked questions