Execution Layer
The component of a modular blockchain responsible for processing transactions, executing smart contracts, and updating the network's state, distinct from consensus and data availability.
Before 'The Merge' in September 2022, Ethereum execution clients (like Geth) handled both transaction execution and Proof-of-Work consensus. The Merge stripped away the PoW consensus logic, turning Geth into a pure Execution Layer client.
graph LR
Center["Execution Layer"]:::main
Pre_smart_contracts["smart-contracts"]:::pre --> Center
click Pre_smart_contracts "/terms/smart-contracts"
Rel_consensus_layer["consensus-layer"]:::related -.-> Center
click Rel_consensus_layer "/terms/consensus-layer"
Rel_data_availability_layer["data-availability-layer"]:::related -.-> Center
click Rel_data_availability_layer "/terms/data-availability-layer"
Rel_account_abstraction["account-abstraction"]:::related -.-> Center
click Rel_account_abstraction "/terms/account-abstraction"
classDef main fill:#7c3aed,stroke:#8b5cf6,stroke-width:2px,color:white,font-weight:bold,rx:5,ry:5;
classDef pre fill:#0f172a,stroke:#3b82f6,color:#94a3b8,rx:5,ry:5;
classDef child fill:#0f172a,stroke:#10b981,color:#94a3b8,rx:5,ry:5;
classDef related fill:#0f172a,stroke:#8b5cf6,stroke-dasharray: 5 5,color:#94a3b8,rx:5,ry:5;
linkStyle default stroke:#4b5563,stroke-width:2px;
🧠 Knowledge Check
🧒 Explain Like I'm 5
Think of a [blockchain](/en/terms/blockchain) like a restaurant. The **Execution Layer** is the kitchen — it takes the orders (transactions), follows the recipes ([smart contracts](/en/terms/smart-contracts)), and cooks the food (updates the state). The **[Consensus Layer](/en/terms/consensus-layer)** is the manager — it doesn't cook, but it checks that the kitchen followed the rules, agrees with the other managers on what was served, and finalizes the receipts. In modern [Ethereum](/en/terms/ethereum), the kitchen and the manager are two separate programs that talk to each other to run the restaurant.
🤓 Expert Deep Dive
The Engine API
The separation of the EL and CL requires a secure, high-bandwidth communication channel: the Engine API. The CL acts as the 'driver'. It uses engine_newPayload to hand a block of transactions to the EL for validation. It uses engine_forkchoiceUpdated to tell the EL which block is the current head of the chain and to command the EL to start building a new block (if the node is the current proposer). This architecture allows EL clients to be completely agnostic to the consensus mechanism.
Execution Clients
The Ethereum network relies on client diversity to prevent catastrophic bugs. Major EL clients include Geth (Go), Nethermind (C#), Erigon (Go, optimized for archive nodes), and Besu (Java). If a bug in Geth (which historically held >80% supermajority) causes it to produce an invalid state root, the chain could halt or fork. Client diversity ensures no single EL implementation can dictate an erroneous state.
Rollups as Execution Layers
In the modular [blockchain](/en/terms/modular-blockchain) thesis (popularized by Celestia and Ethereum's rollup-centric roadmap), execution is scaled by moving it off the base layer. Rollups (Arbitrum, Optimism, zkSync) are purely execution layers. They process EVM (or custom VM) transactions at high speed and low cost, then post the transaction data (Data Availability) and proofs (Settlement) to the L1, which provides Consensus.
❓ Frequently Asked Questions
What is the difference between the Execution Layer and the Consensus Layer?
The Execution Layer processes transactions, runs smart contracts (EVM), and updates user balances. The Consensus Layer does not process transactions; instead, it coordinates validators to vote on which blocks are valid and ensures the network agrees on a single, final history of the chain.
What were the Execution Layer and Consensus Layer called before The Merge?
Historically, the Execution Layer was referred to as 'Eth1' (the original Ethereum PoW chain), and the Consensus Layer was referred to as 'Eth2' (the Beacon Chain). The Ethereum Foundation deprecated these terms in favor of EL and CL to emphasize that they are two components of a single, unified network, not sequential upgrades.
How do Layer 2 Rollups fit into this model?
Layer 2 Rollups (like Arbitrum or Base) are essentially standalone execution layers. They handle all the heavy transaction processing off-chain, and then use Ethereum (Layer 1) strictly for consensus, data availability, and final settlement.