Dedicated Ethereum RPC Nodes & Endpoints

Ethereum 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://ethereum-rpc.publicnode.com");
const blockNumber = await provider.getBlockNumber();
console.log("Ethereum block:", blockNumber);

Dedicated Ethereum RPC node vs shared endpoints

Mainnet is where shared RPC costs the most. The mempool is the most competitive in crypto, gas moves in seconds, and the same public endpoints that serve wallet balance checks also serve every bot that found the same URL. Under load they answer with rate limits, capped eth_getLogs ranges, and a pending-transaction view that is delayed, filtered, or missing entirely. Compute-unit billing adds a second tax: the trace and log methods a serious Ethereum workload leans on are exactly the ones metered at the highest multipliers.

A dedicated Ethereum RPC node on BLAZED.sh is not a private URL to a remote gateway; it is your code running on the node itself. You deploy a Docker container or script onto the host of a fully synced mainnet node and talk to it over a local socket, with RPC calls completing in under 10 milliseconds, a full txpool view served by the same machine, and no compute units or shared quotas deciding when your strategy runs. This page is not a waitlist: Ethereum is the chain BLAZED.sh runs in production today.

Ethereum RPC latency: architecture over benchmarks

Benchmark tables comparing RPC gateways miss the structural point: every remote endpoint, however well run, spends tens to low hundreds of milliseconds per call on the public-internet round trip before provider-side queueing starts. Ethereum's twelve-second blocks sound forgiving, but inclusion, MEV, and liquidations are decided in the milliseconds after a transaction hits the mempool, not at the block boundary. On BLAZED.sh, calls complete in under 10 milliseconds because they never leave the machine: your container sits on the node host and reads over a local socket. That figure is measured on the live Ethereum product, not extrapolated from a lab.

What a dedicated Ethereum 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 plans running on Ethereum in production today, and pricing is still being finalized. Sign up and your container is on a node in minutes.

Ethereum is the chain these plans serve in production today: bot loops and indexer reads are single-credit calls and txpool_content is a fixed 4 credits, so a mainnet workload prices out by counting requests rather than decoding a compute-unit table.

Perfect for

What is Ethereum?

Ethereum is the largest smart-contract platform and, since the Merge, a proof-of-stake network with twelve-second slots. Everything in the EVM ecosystem is downstream of it: rollups post their data to mainnet, bridges settle on it, and the deepest DeFi liquidity and the most competitive MEV live on the base layer itself. That competitiveness is what makes the RPC layer decisive on Ethereum in a way it is not anywhere else. A quote, a liquidation check, or a pending-transaction stream is only as good as the path between your code and a node, and on mainnet that path is contested by better-funded, better-connected actors than on any other chain. Shared gateways add rate limits, compute-unit metering, and a public-internet round trip to every call; running your own node makes sync, storage, and upgrades your problem. BLAZED.sh removes the path instead: you deploy a Docker container or script onto the host of a fully synced Ethereum node and read state, logs, and the txpool over a local socket, with archive access available on Enterprise plans.

Ethereum RPC: frequently asked questions