Zora Network RPC Nodes & Endpoints

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

Dedicated Zora RPC node vs shared endpoints

Zora's traffic is shaped by drops. When a mint goes live, thousands of collectors arrive in the same minute, and every marketplace, bot, and indexer watching the collection starts hammering eth_getLogs and token-URI reads at once. Public endpoints throttle under exactly that load, which means the moments that matter most on Zora, the first minutes of a mint, are the moments shared RPC is least reliable.

A dedicated Zora RPC node keeps your platform responsive through the rush: log queries over a hot collection run at hardware speed, websocket subscriptions stay attached, and no shared quota decides whether your feed updates. On BLAZED.sh, dedicated goes further than a private URL: your indexer or media backend runs in a container on the node host, so reads travel a local socket rather than the public internet.

Zora RPC latency: architecture over benchmarks

Zora produces a block roughly every two seconds, but mint UX is decided in far smaller windows: the difference between showing a token as available or already claimed is a read that either returns immediately or queues at a remote gateway for tens to low hundreds of milliseconds. On our live Ethereum product, co-locating code with the node keeps calls under 10 milliseconds over a local socket, and dedicated Zora nodes will use the same architecture.

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

NFT indexing on Zora is log queries and state reads, single-credit calls almost without exception, so a collection backfill prices out by block range and a live feed by its polling rate.

Perfect for

What is Zora?

Zora Network launched in 2023 as an OP-Stack rollup and is a member of the Superchain, so it behaves like other OP-Stack chains from an integration standpoint: EVM execution, ETH for gas, data posted to Ethereum, and standard tooling that works after swapping the RPC URL to chain ID 7777777. What sets it apart is what runs on it. Zora's protocol and marketplace centre on minting and trading media NFTs, so activity concentrates around drops: a popular mint compresses thousands of transactions and metadata reads into minutes. Indexers tracking collections, marketplaces resolving token URIs, and creator platforms rendering feeds all lean on eth_getLogs and state reads at exactly those moments, which is why the RPC layer, not the chain's throughput, is usually the first thing teams need to upgrade.

Zora RPC: frequently asked questions