Zora Network RPC Nodes & Endpoints

Zora Network RPC URLs you can use right now

Third-party endpoints, free and shared. They are comfortable on a normal day and least available during a drop, which is the only moment a mint UI genuinely needs them.

import { JsonRpcProvider } from "ethers";

const provider = new JsonRpcProvider("https://rpc.zora.energy");
const blockNumber = await provider.getBlockNumber();
console.log("Zora block:", blockNumber);

Mint rushes are exactly when shared endpoints throttle

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.

Resolving token metadata is the workload, not the transfers

The interesting engineering problem on Zora is not tracking who minted what, which is a straightforward log walk. It is turning those tokens into something you can render. Each one requires a tokenURI or uri call, and for ERC-1155 the returned string frequently contains a placeholder your client has to substitute before the URI is usable at all. A feed showing a few hundred tokens is therefore a few hundred contract reads before a single image loads, and those reads are serial with respect to the user's patience.

Then the URI usually points at IPFS, and you have left the chain entirely. Gateway latency dominates from that point, gateways rate limit independently of your RPC provider, and pinning status varies by collection, so a token that resolved last week may hang today. The pattern that works is to treat metadata as a cache to be populated ahead of time rather than resolved on request: walk the collection's logs, batch the URI reads, fetch and store the metadata yourself, and serve the feed from your own storage. That turns a user-facing latency problem into a background job, and the background job is bounded by how fast you can issue contract reads, which is precisely where a dedicated node changes the numbers.

Zora RPC latency is a distance problem

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

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