Private Ethereum RPC Node Setup: Geth, Reth, Lighthouse

Relying on public RPC providers—Alchemy, Infura, QuickNode—means depending on someone else's uptime, rate limits, and pricing. Ethereum nodes and clients recommends running your own infrastructure for production workloads. At volumes over 100k requests/day, the economics of a private node become compelling: a typical configuration pays for itself in 3–6 months, reducing infrastructure spending by 50–70% compared to public provider plans. Beyond cost, a private node gives you full access to debug_* and trace_* namespaces that public providers often disable or charge separately for. The cost of a private solution is 2–3 times lower than public RPC at workloads above 500k requests/day.

Recently, a DeFi project came to us when their public RPC provider disabled debug methods right in the middle of testing a new AMM contract. Changing providers would have taken weeks, but the deadline was tomorrow. In two days we spun up a private node using Reth + Lighthouse, and the team continued debugging without restrictions. Contact us for a consultation on choosing the right configuration for your load.

We have been setting up private RPC nodes for 5+ years, with 50+ projects on Ethereum and sidechains. Our engineers test each node under real load and guarantee 99.9% uptime given the proper environment.

Which client to choose for Ethereum?

Two main execution clients:

Geth (go-ethereum) — the most widespread, largest documentation, stable. Archive mode takes ~16 TB. Slowest on eth_getLogs over large block ranges.

Reth (Paradigm) — written in Rust, significantly faster than Geth on historical queries. Archive mode ~2.5 TB (better compression). We recommend it for new installations.

Erigon — archive node ~3 TB, fast historical queries, but more complex to set up and update.

Why set up a private node?

Public RPCs have rate limits (typically 100–300 req/s), lack debug/trace methods, and cost extra when you exceed limits. Compare for yourself:

A private node gives you:

• Full control: any eth_*, debug_*, trace_* methods without surcharges.
• No rate limits: you pay only for hardware.
• Fast historical queries: archive node is not throttled.
• Independence: if a provider fails, your node keeps running.

How to set up a private RPC node: step-by-step

The setup process includes:

1. Install execution and consensus clients.
2. Create a JWT secret for client communication.
3. Start the execution layer (Reth).
4. Start the consensus layer (Lighthouse) with checkpoint sync.
5. Configure Nginx reverse proxy with SSL and rate limiting.
6. Set up monitoring and alerts.

Installing Reth + Lighthouse (Ethereum mainnet)

Ethereum PoS requires two clients: execution layer (Reth) + consensus layer (Lighthouse/Prysm):

# Reth
curl -L https://github.com/paradigmxyz/reth/releases/latest/download/reth-x86_64-unknown-linux-gnu.tar.gz | tar xz
sudo mv reth /usr/local/bin/

# Lighthouse (consensus client)
curl -L https://github.com/sigp/lighthouse/releases/latest/download/lighthouse-x86_64-unknown-linux-gnu.tar.gz | tar xz
sudo mv lighthouse /usr/local/bin/

# JWT secret for Engine API communication
openssl rand -hex 32 > /etc/ethereum/jwt.hex

Start execution layer (Reth):

reth node \
  --chain mainnet \
  --datadir /data/reth \
  --http \
  --http.addr 127.0.0.1 \
  --http.port 8545 \
  --http.api eth,net,web3,txpool,debug,trace \
  --ws \
  --ws.addr 127.0.0.1 \
  --ws.port 8546 \
  --authrpc.addr 127.0.0.1 \
  --authrpc.port 8551 \
  --authrpc.jwtsecret /etc/ethereum/jwt.hex \
  --full  # use --full=false for archive

Start consensus layer (Lighthouse):

lighthouse beacon_node \
  --network mainnet \
  --datadir /data/lighthouse \
  --execution-endpoint http://127.0.0.1:8551 \
  --execution-jwt /etc/ethereum/jwt.hex \
  --checkpoint-sync-url https://mainnet.checkpoint.sigp.io \
  --disable-deposit-contract-sync

--checkpoint-sync-url enables syncing the consensus client from a finalized checkpoint instead of genesis, reducing time from weeks to hours.

Configuring Nginx as reverse proxy

Exposing the RPC port directly is bad practice. Use Nginx with auth and rate limiting:

upstream ethereum_rpc {
    server 127.0.0.1:8545;
    keepalive 32;
}

server {
    listen 443 ssl;
    server_name rpc.yourdomain.com;

    ssl_certificate /etc/letsencrypt/live/rpc.yourdomain.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/rpc.yourdomain.com/privkey.pem;

    satisfy any;
    allow 10.0.0.0/8;
    deny all;

    location / {
        proxy_pass http://ethereum_rpc;
        proxy_http_version 1.1;
        proxy_set_header Connection "";
        proxy_set_header Host $host;
        proxy_read_timeout 300s;
        limit_req zone=rpc_limit burst=100 nodelay;
    }
}

limit_req_zone $binary_remote_addr zone=rpc_limit:10m rate=100r/s;

WebSocket for subscriptions — separate location:

location /ws {
    proxy_pass http://127.0.0.1:8546;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    proxy_read_timeout 3600s;
}

Other EVM networks: BSC, Polygon and their setup

Most EVM networks are forks of Geth. The principle is the same, with their own clients. For BSC we use BSC Geth, for Polygon — Bor (execution) and Heimdall (consensus), similar to the Reth+Lighthouse pair. They are launched with similar parameters, only with configs matching the respective network. For Polygon, two consensus layers are required: Heimdall (Cosmos SDK based) and Bor (Geth fork). This increases setup time, but we provide ready-made scripts.

Node monitoring

Checking sync is simple: the eth_syncing request returns status and lag. Alerts: a node is healthy if lag < 5 blocks and peers >= 5. If peers = 0, the node is isolated from the network—worse than simply being behind.

Prometheus + Grafana for long-term monitoring: Reth and Geth expose metrics natively (--metrics.port 9001). Ready dashboards are in the respective client repositories.

What's included in turnkey setup

• Installation and configuration of execution + consensus clients for the selected network.
• Nginx reverse proxy with SSL, rate limiting, and IP whitelist.
• Monitoring (Prometheus + Grafana) with alerts to Telegram/Slack.
• Load testing (up to 1000 rps) and optimization.
• Maintenance and recovery documentation.
• Training for your team (1 hour online).

Timelines and cost

Estimated timeline: from 2 to 7 days depending on the network and archive requirements. Cost is calculated individually after load analysis: contact us for a free project estimate. Order a private RPC node setup and gain full control over your infrastructure. Our engineers will help you pick the optimal configuration for your budget and load.

Get in touch—we have already set up nodes for 50+ projects, including high-load DeFi and NFT marketplaces.

Blockchain Infrastructure Deployment: Nodes, RPC, Indexing

Subgraph fell at 3:47 AM. By morning users saw outdated balances, transactions "hung" in the UI, support received 47 tickets in an hour. Cause: the handler in the subgraph failed on a transaction with a non-standard event log — and the entire index stopped. We have encountered such situations dozens of times. Our experience shows: blockchain infrastructure does not forgive gaps in observability. Guaranteeing uptime without multi-layered monitoring and fault-tolerant architecture is impossible. Over 8 years working with Ethereum, Polygon, and Solana, we have developed an approach that allows predictable deployment of infrastructure of any scale — from a single node to a multichain grid with dozens of subgraphs.

RPC Layer Architecture

Every dApp interaction with the blockchain goes through RPC — the JSON-RPC API provided by a node. Three options:

Managed providers — Alchemy, QuickNode, Infura, Ankr. Minimal operational costs, SLA, built-in monitoring. Limits: rate limits (Alchemy Free: 300 RU/sec), vendor lock, potential downtime during provider incidents. For most projects — the right choice at the start.

Self-owned nodes — full control, no rate limits, no third-party dependence. Cost: archive Ethereum node requires 2.5–3TB SSD, a strong server, and DevOps support. Sync from scratch on Ethereum via Geth/Nethermind — 3–7 days. Justified under high load or latency requirements.

Hybrid — self-owned node as primary, managed provider as fallback. Standard for protocols with high TVL. Proper load balancing can reduce costs by 20–30% compared to pure managed setup. Under high monthly request volume, hybrid saves significantly.

How to Set Up an RPC Layer Without a Single Point of Failure?

At least two providers, DNS round-robin with health check every 5 seconds, automatic fallback when latency >500 ms. In practice, this gives 99.99% availability during any provider failure. For protocols with high TVL, we recommend a custom HA-proxy (nginx or Envoy) in front of two managed providers.

Why Is a Hybrid RPC Scheme More Cost-Effective Than Pure Managed?

At high request volumes, managed providers can be very expensive; a hybrid using a self-owned node as primary and a managed fallback cuts costs significantly without losing SLA.

Ethereum Node Clients

Execution clients: Geth (most used), Nethermind (C#, fast sync), Besu (Java, enterprise), Erigon (fastest sync, efficient archive mode ~2TB instead of 3TB).

Consensus clients (post-Merge): Lighthouse (Rust), Prysm (Go), Teku (Java), Nimbus (Nim). Each node after The Merge requires a pair of execution + consensus clients.

For DevOps: eth-docker — Docker Compose configurations for all client combinations. Setting up monitoring via Grafana + Prometheus is mandatory; a standard dashboard is available in each client's repository.

The Graph: Event Indexing

The Graph Protocol — decentralized indexing. A subgraph describes which events from which contracts to index and how to transform them into a GraphQL schema.

Subgraph structure:

• subgraph.yaml — manifest: contract addresses, startBlock, events to handle
• schema.graphql — GraphQL schema of entities
• src/mapping.ts — AssemblyScript event handlers

dataSources:
  - kind: ethereum
    name: UniswapV3Pool
    network: mainnet
    source:
      address: "0x88e6A0c2dDD26FEEb64F039a2c41296FcB3f5640"
      abi: UniswapV3Pool
      startBlock: 12370624
    mapping:
      eventHandlers:
        - event: Swap(indexed address,indexed address,int256,int256,uint160,uint128,int24)
          handler: handleSwap

AssemblyScript handlers — not TypeScript. No nullable types, no closures, no many standard APIs. An error in the handler stops the subgraph indexing on that transaction. Important: add try-catch for operations that can fail (e.g., store.get() for an entity that may not exist).

How to Avoid Subgraph Indexing Stops?

Graph Node logs are monitored in real-time; on hasIndexingErrors = true an alert fires and an automatic node restart (via systemd or Kubernetes). Typical downtime on error — 150–300 seconds to recover. Additionally, for production we set up a watchdog that restarts Graph Node if subgraph lag exceeds 50 blocks.

Choosing Between Hosted Service and Decentralized Network

Graph Hosted Service (free, centralized) is deprecated in favor of Subgraph Studio + Graph Network. For production: deploy on Graph Network with GRT curation signal — the subgraph gets indexers proportional to curation.

Alternatives to The Graph: Ponder (TypeScript, self-hosted, easier to debug), Envio (ultra-fast indexer, supports EVM + non-EVM), Subsquid (TypeScript, own network), Moralis Streams (managed, webhook-based). Our experience shows: for high-load projects with unique logic, Ponder or Envio are more effective — they give full control over the process and do not require GRT tokenomics.

Webhooks and Real-Time Notifications

Alchemy Webhooks and QuickNode Streams allow receiving events in real-time via HTTP webhook or WebSocket. For monitoring addresses, new transactions, mints — this is faster than polling RPC.

Tenderly — platform for monitoring and alerts. You can set up an alert for a specific contract event, balance change, function call with certain parameters. Transaction simulation via Tenderly API is invaluable for debugging.

Monitoring and Observability

Minimum monitoring stack for a protocol:

On-chain: OpenZeppelin Defender Sentinel — watches contract events, triggers webhook or Autotask when conditions are met. Forta Network — community-maintained bots detect anomalies (large withdrawals, flash loans, governance attacks).

Infrastructure: Grafana + Prometheus for nodes, Datadog or Grafana Cloud for managed metrics. Alerts on: node is 10+ blocks behind, RPC latency >500ms, subgraph lag >100 blocks.

Uptime: Better Uptime or PagerDuty on RPC endpoint and subgraph health endpoint (The Graph provides _meta { hasIndexingErrors, block { number } }).

Why Is Monitoring Without Tenderly Insufficient?

Tenderly provides transaction simulation and detailed traces — critical for debugging subgraph and smart contract errors. Forta focuses on network anomalies, not your infrastructure. The combination of Tenderly plus a custom Grafana dashboard covers 90% of incident scenarios.

Multichain Infrastructure

A protocol on 5 chains = 5 separate RPC endpoints, 5 subgraphs, 5 monitoring configs. Manageable but requires deployment automation.

For subgraph multi-network deployment: graph deploy --network mainnet, graph deploy --network arbitrum-one etc. with a unified codebase and network-specific addresses in separate config files.

Chainlink CCIP and LayerZero for cross-chain messaging require monitoring of both chains and transactions on intermediate relayers. A reorg on the source chain after a confirmed mint on the target chain is a classic bridge problem. Solution: wait for finality (on Ethereum ~15 minutes after Merge for economic finality) before confirming on the target chain.

Infrastructure Setup Process

1. Audit current stack — determine chains, request volume, latency and availability requirements.
2. Architecture design — select providers, load balancing, redundancy.
3. Subgraph development — manifest → schema → handlers → testing on local Graph Node → deploy to testnet → mainnet.
4. Monitoring configuration — Tenderly alerts, Grafana dashboard, PagerDuty integration.
5. Documentation and runbook — what to do when: subgraph falls behind, RPC downtime, node desync.
6. Handover to operations — team training, access transfer, first month support.

What's Included

• Deployment of managed or self-hosted Ethereum, Polygon, BNB Chain nodes
• RPC layer setup with primary/fallback and load balancing
• Subgraph development and deployment for your protocol
• Monitoring connection (Tenderly, Grafana, alerts)
• Runbook and operations documentation
• Team training (up to 4 hours online)
• 30-day support after delivery

Timeline

All projects are managed in a GitHub/GitLab repository with CI/CD; configuration code stays with you. Order infrastructure deployment — we'll show how to cut costs by 20–30% without losing reliability. Get a consultation — we'll demonstrate how we deployed infrastructure for a protocol with large TVL on Ethereum and Arbitrum. Contact us.