Consensus Client (CL) & Execution Client (EL)
Consensus Client (CL) & Execution Client (EL) ✅ The Two-Client Architecture (CRUCIAL TO UNDERSTAND) Every Ethereum node (full node or validator) runs two clients : 1. Execution Client (EL) – Geth, Nethermind, Erigon Verifies transactions (nonce, signature, gas, balance) Executes smart contracts (EVM) Maintains the world state Computes stateRoot Verifies execution payloads of blocks 2. Consensus Client (CL) – Prysm, Lighthouse, Teku, Nimbus Runs the Beacon Chain Handles validators, attestations, committees Chooses the head block (LMD-GHOST) Finalizes the chain Gossips blocks, attestations, sync messages Communication Between EL & CL: They talk through a local API called Engine API (JSON-RPC over pipe/HTTP). This API sends messages like: CL → EL : “Here is a new block’s execution payload, verify it.” EL → CL : “Execution payload is valid, here is the new stateRoot.” EL → CL : “Here is your suggested new block’s payload.” (wh...