zkSync Era RPC Nodes & Endpoints

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

Dedicated zkSync Era RPC node vs shared endpoints

zkSync Era adds surfaces that generic shared endpoints handle unevenly: the zks_ namespace for fee estimates and L1 batch data, and native account abstraction, which turns wallets and paymasters into services that poll constantly. A bundler or paymaster loop asking for fees and nonces every few hundred milliseconds is exactly the steady, chatty traffic that shared rate limits punish, and a public endpoint that lags on zks_ methods breaks fee UX in ways users notice immediately.

A dedicated zkSync RPC node serves that polling at whatever rate your product needs and keeps the zks_ namespace as fast as the standard one. Indexers tracking L1 batch commitments get consistent throughput instead of backoff loops. On BLAZED.sh, the bundler or indexer itself runs in a container on the node host, reading over a local socket.

zkSync Era RPC latency: architecture over benchmarks

Account-abstraction UX is a latency product: the wallet waits on a fee estimate, the paymaster waits on a balance read, and every one of those calls pays the network path to the endpoint. Over a public gateway that is tens to low hundreds of milliseconds per call. On our live Ethereum product, co-located code completes calls in under 10 milliseconds over a local socket, and dedicated zkSync Era nodes will use the same design. That gap is the difference between AA flows that feel native and ones that feel like waiting.

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

AA infrastructure generates many small reads, and small reads are single-credit calls, so even a paymaster polling around the clock arrives at a monthly number you can compute in advance.

Perfect for

What is zkSync Era?

zkSync Era uses zkEVM technology to prove batches of transactions with validity proofs, giving faster economic finality than optimistic rollups once a proof is verified on Ethereum. It is EVM-compatible rather than fully EVM-equivalent: most Solidity works, but contract deployment uses a different bytecode path and the chain exposes zkSync-specific RPC methods (the zks_ namespace) for fees, L1 batch details, and paymaster flows. Native account abstraction is a first-class feature, so wallets, gasless UX, and smart-account tooling are common here. Connecting uses chain ID 324, and as with every rollup the RPC layer, not the prover, is what most apps feel day to day, especially indexers tracking L1 batch commitments.

zkSync Era RPC: frequently asked questions