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 (Go)
• Besu 30303 TCP/UDP (Java, https://besu.hyperledger.org/en/stable/)
• Nethermind 30303 TCP/UDP
• Erigon 30303 TCP/UDP

• reth (Rust)

Activities

• Read about why beacon node controls the execution node and you must have one execution node per beacon node in lighthouse: https://github.com/sigp/lighthouse/blob/stable/book/src/merge-migration.md#connecting-to-an-execution-engine
• Ethereum execution layer synchronization nodes

Related

• Consensus clients, lighthouse, Teku, Prysm, Nimbus, Caplin and Lodestar
• 8551
• Paul Hauner
• Execution node
• ganache
• Ethereum node

See also

• Execution clients: geth, besu, reth, Nethermind, Erigon, 30303, 8551, 8547, Prysm, Nimbus, lighthouse
• 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