Skip to content

Supported clients

The Execution and Consensus clients we run, and how to route to a specific one.

The clients below are the ones we currently support on each layer. By default, requests are load balanced across them, but you can target any single client when you need to. If there's a client we don't run yet that you'd like to use, just ask — we're happy to add more.

Execution Layer clients

Geth geth Erigon erigon Nethermind nethermind Besu besu Reth reth ethrex ethrex

Consensus Layer clients

Lighthouse lighthouse Prysm prysm Teku teku Nimbus nimbus Lodestar lodestar Caplin caplin

Caplin is Erigon's built-in consensus client, and runs as part of our Erigon nodes.

Routing to a specific client

To force a request onto one client implementation, prepend the client name to the network in the hostname:

  • Execution: {client}.{network}.rpc.ethnodeops.xyz
  • Consensus: {client}.{network}.ebeacon.ethnodeops.xyz

Examples

Geth only, on Hoodi:

url 
https://geth.hoodi.rpc.ethnodeops.xyz

Lighthouse beacon only, on Hoodi:

url 
https://lighthouse.hoodi.ebeacon.ethnodeops.xyz

Tip: Most requests work fine against the load-balanced network endpoint without naming a client. Reach for client-specific routing when you're debugging client behaviour, testing against a particular implementation, or need a feature that's only on one client.

Not every client runs on every network. If you target a client that isn't available for a given network, the request won't route — fall back to the plain network endpoint, or email node-infrastructure@ethereum.org if you need a specific combination.