Ethereum execution clients

Execution clients are upgraded versions of existing Ethereum clients like Besu, EthereumJS, Erigon, Geth and Nethermind. These clients have had the proof-of-work components removed and now rely upon a Consensus Client to perform the functions of a consensus mechanism.

Execution client Default Port

• Geth 30303 TCP/UDP
• Besu 30303 TCP/UDP
• Nethermind 30303 TCP/UDP
• Erigon 30303 TCP/UDP

Consensus client Default Port

• Prysm 13000 TCP, 12000 UDP
• Lighthouse 9000 TCP/UDP
• Teku 9000 TCP/UDP
• Nimbus 9000 TCP/UDP

Related

• Consensus Clients

See also

• {{execution clients}]
• Ethereum 2.0, API, Ethereum tasks, Beacon Chain, Ethereum Staking, validator, Consensus clients, Execution clients, Validation clients, Mainnet, testnets: Prater, Goerli ETH, Inclusion distance, Ethereum attestation, Attestation effectiveness, Attestation Reward Scale, slot, Ethereum upgrades: The Merge, Epoch, Slots, rETH, sETH, stETH, Lido Staked ETH, faucet, Ethereum ports, Subjectivity, Lido Staked ETH, ENR, Sharding, Ethers.js, Yellow paper, synchronization, ECFSDS
• Consensus, Proof of Stake (PoS), Consensus clients, Execution clients, Prysm, Lighthouse, Lodestar, Teku, Nimbus, Consensus Layer (CL), Beacon client