Compare
eRPC vs web3-proxy
AI agents: fetch https://docs.erpc.cloud/compare/erpc-vs-web3-proxy.llms.txt for the complete machine-readable version of this page (full configuration schema, defaults, worked examples, and source links). Append `.llms.txt` to any docs URL for the same treatment.AIFor agents: /compare/erpc-vs-web3-proxy.llms.txt

eRPC vs web3-proxy

web3-proxy (opens in a new tab) is the Rust proxy that ran LlamaNodes' public RPC. It ships a full RPC-as-a-service layer: wallet login, keys, tiers and compute-unit billing. eRPC is an EVM and Solana JSON-RPC proxy built around failover, a finality-aware cache, and cost control. Every cell below links to the page or line that states it. Facts were checked on 2026-10-22.

Feature table

eRPCweb3-proxy
Language, licenseGo, Apache-2.0 (LICENSE (opens in a new tab))Rust, GPL-3.0 (LICENSE (opens in a new tab))
Latest release0.4.0, 2026-10-11 (release (opens in a new tab))No GitHub releases; last tag v1.43.99, 2023-12-03 (tags (opens in a new tab))
Last commit2026-10-22 (commits (opens in a new tab))2023-12-05 (commit (opens in a new tab))
ChainsEVM and Solana, many chains per process (networks)EVM, one chain_id per process (example.toml (opens in a new tab))
ConfigYAML or TypeScript (quick start)TOML (example.toml (opens in a new tab))
Upstream selectionScore from errors, latency, 429s, block lag (selection policies)Synced head, latency tiers, peak-EWMA load (one.rs (opens in a new tab))
Failover and retryYes, per method (retry)Next ranked upstream on error (consensus.rs (opens in a new tab))
Hedged requestsYes (hedge)No; "fastest" mode is todo!() (many.rs (opens in a new tab))
Circuit breakerYes (circuit breaker)Not found in source (src (opens in a new tab))
Cross-checking answersConsensus across N upstreams (consensus)Head-block agreement only; response quorum is todo!() (many.rs (opens in a new tab))
CacheMemory, Redis, PostgreSQL, DynamoDB; finality-aware (drivers, cache)In-memory; keys include block hash (app/mod.rs (opens in a new tab), block_number.rs (opens in a new tab))
Rate limitsPer client, project, network, upstream (rate limiters)Per upstream soft/hard limits; per IP and per key tier (config.rs (opens in a new tab), authorization.rs (opens in a new tab))
Client authSecret, JWT, SIWE, IP, database (auth)RPC keys, SIWE login, IP/origin/referer allowlists (authentication.rs (opens in a new tab))
BillingNo; cost headers for an external meter (directives)Yes: compute units, balances, deposits, Stripe (compute_units.rs (opens in a new tab))
eth_getLogs splittingYes (getLogs splitting)No; ranges over 200,000 blocks rejected (block_number.rs (opens in a new tab))
JSON-RPC batchYes (batch)Yes (app/mod.rs (opens in a new tab))
eth_subscribenewHeads, logs, newPendingTransactions (websocket)newHeads, newPendingTransactions (ws.rs (opens in a new tab))
Metrics, tracingPrometheus, OpenTelemetry (monitoring, tracing)Prometheus, InfluxDB stats, Sentry (prometheus.rs (opens in a new tab), Cargo.toml (opens in a new tab))
Archive routingBlock availability per upstream (upstreams)Probes each upstream's history depth automatically (one.rs (opens in a new tab))
DeploymentBinaries, Docker, Kubernetes manifests, npx start-erpc (docker, kubernetes)Build with cargo or the Dockerfile (Dockerfile (opens in a new tab))

"Not found in source" means a search of the web3-proxy source found no code for it.

Where web3-proxy is stronger

Where eRPC is stronger

  • Active releases; web3-proxy has had no commit since December 2023.
  • Hedging, circuit breaker and response consensus (failsafe).
  • Shared, finality-aware cache on Redis, PostgreSQL or DynamoDB (cache).
  • eth_getLogs range splitting instead of a range cap (getLogs splitting).
  • Many chains, EVM and Solana, in one process (networks).
eRPC vs web3-proxy — agent referenceExpand for every option, default, and edge case — or copy this entire section into your AI assistant.

Sources and snapshot

  • eRPC: erpc/erpc at 32a8a1e450c6ab5a78477859c85221b6a9058c72, docs at docs.erpc.cloud.
  • web3-proxy: llamanodes/web3-proxy main at f4a71ee0b621c461828956436f6d55372228ec18 (2023-12-05). The repo is not archived.
  • Checked 2026-10-22. "Not found in source" and "No" for hedging, circuit breaker and OpenTelemetry rest on a source search and the todo!() branches cited. The code was not run.

Moving from web3-proxy to eRPC

web3-proxy concepteRPC equivalent
one process per chain_idone process, many networks[] (networks)
balanced_rpcsprojects[].upstreams[] (upstreams)
backup = true upstreamfallback tier in a selection policy (selection policies)
soft_limit / hard_limitupstream rate-limit budget (rate limiters)
RPC keys in the URLsecret or database auth (auth)
in-memory response cachedatabase.evmJsonRpcCache (cache)

Keep web3-proxy when

  • You need its built-in billing and user accounts and accept an unmaintained codebase.

Related pages