The execution layer (formerly called “Eth1”) is one of the two primary components of Ethereum’s post-Merge architecture, responsible for processing transactions, executing smart contracts, and maintaining the current state of the Ethereum network. Following the September 2022 Merge, Ethereum’s architecture was formalized as two distinct but coordinating layers: the execution layer (handling computation and state transitions) and the consensus layer (handling validator coordination, block proposal, and finality via proof-of-stake). The execution layer runs the Ethereum Virtual Machine (EVM), processes all transaction data including smart contract interactions, maintains the accounts and balances database, and generates execution payloads that the consensus layer includes in blocks. Client software implementing the execution layer includes Geth (go-ethereum), Nethermind, Besu, and Erigon. The separation of execution and consensus into distinct layers was a key architectural milestone enabling Ethereum’s transition from proof-of-work to proof-of-stake without rewriting the smart contract execution logic.
Origin & History
| Date | Event |
| 2015 | Original Ethereum combines execution and consensus in “Eth1” clients |
| 2020 | Ethereum research formalizes “Eth1/Eth2” terminology; later renamed execution/consensus |
| 2020 | Beacon Chain launches as separate consensus layer; begins PoS validator coordination |
| 2021 | Engine API specification developed to connect execution and consensus layers |
| 2022 (Jun) | “Eth1″/”Eth2” terminology deprecated; renamed execution layer/consensus layer |
| 2022 (Sep 15) | The Merge: execution layer coupled to Beacon Chain; PoW mining disabled |
| 2023 | Shanghai/Capella upgrade (Shapella): execution layer enables ETH withdrawal processing |
| 2024 | EIP-4844 (Dencun): execution layer adds blob transactions for L2 data availability |
“The separation of execution and consensus is not just technical architecture – it’s a philosophical statement about specialization, upgradability, and the future of Ethereum scaling.”
How It Works
POST-MERGE ETHEREUM ARCHITECTURE:
CONSENSUS LAYER (Beacon Chain) ┌─────────────────────────────────┐ │ Validators propose/attest blocks│ │ PoS fork choice rule │ │ Finality (2 epochs ~12 min) │ │ Slashing of dishonest validators│ └──────────┬──────────────────────┘ │ Engine API │ (newPayload, forkchoiceUpdated) ▼ EXECUTION LAYER (EVM) ┌─────────────────────────────────┐ │ Processes transactions │ │ Executes smart contracts │ │ Maintains state (accounts, code)│ │ Generates execution payload │ │ Manages mempool │ └─────────────────────────────────┘
| Responsibility | Execution Layer | Consensus Layer |
| Transaction processing | ✓ | ✗ |
| Smart contract execution | ✓ | ✗ |
| State management (ETH balances) | ✓ | ✗ |
| Block proposal | ✗ | ✓ (validators) |
| Finality | ✗ | ✓ |
| Sybil resistance | ✗ | ✓ (ETH staking) |
| P2P network | Both (different protocols) | Both |
| Mempool | ✓ | ✗ |
In Simple Terms
- The computer of Ethereum: The execution layer is where all actual computation happens – every smart contract interaction, token transfer, and DeFi transaction is processed here.
- Separation of concerns: Before the Merge, one system handled both transactions AND validator coordination. Post-Merge, these are separated – the execution layer focuses purely on computation.
- EVM lives here: The Ethereum Virtual Machine, which processes all smart contracts, is the core of the execution layer.
- Powered by client diversity: Multiple independent software teams (Geth, Nethermind, Besu, Erigon) implement the execution layer, preventing a single software bug from halting all of Ethereum.
- Engine API bridge: The execution and consensus layers communicate through the Engine API – the consensus layer instructs the execution layer which transactions to process and when.
Real-World Examples
| Scenario | Implementation | Outcome |
| ETH transfer | Execution layer validates, processes transaction | Balances update; state root changes |
| Uniswap swap | EVM in execution layer runs Uniswap contract bytecode | Token balances swap atomically |
| Validator proposes block | Consensus layer requests execution payload via Engine API | Execution layer provides transactions + state root |
| Shapella withdrawal | Shanghai upgrade adds withdrawal processing to execution layer | Validator ETH withdrawals enabled |
| L2 blob data | Dencun adds blob transaction type to execution layer | Cheaper data availability for rollups |
Advantages
| Advantage | Description |
| Specialization | Execution layer focuses purely on computation, improving optimization |
| Modular upgrades | Execution upgrades (EIPs) independent from consensus upgrades |
| Client diversity | Multiple execution clients prevent single point of failure |
| EVM stability | Core execution logic unchanged by consensus layer changes |
| L2 data support | Execution layer extended with blob transactions for L2 scaling |
| Formal specification | Execution layer formally specified for cross-client compatibility |
Disadvantages & Risks
| Disadvantage | Description |
| Client dominance risk | Geth ~65-70% share; single client bugs could affect majority |
| Engine API complexity | Coordination between layers adds complexity |
| MEV concentration | Execution layer’s mempool enables MEV extraction |
| Gas limit constraints | Execution layer throughput still limited by block gas limit |
| Cross-layer synchronization | Both layers must upgrade coordinated for hard forks |
Risk Management Tips:
- Node operators should consider running minority execution clients (Nethermind, Besu, Erigon) to improve client diversity
- Monitor execution layer gas usage to anticipate fee spikes for scheduled transactions
- Track execution layer upgrade proposals (EIPs) that may affect DApp behavior
- For DApp developers, test on testnets that use the same execution layer client diversity as mainnet
FAQ
Q: What is the difference between the execution layer and the consensus layer?
A: The execution layer processes transactions and smart contracts (the “what happened” layer). The consensus layer coordinates validators to agree on which blocks to include and achieve finality (the “who decides what happened” layer). They communicate via the Engine API.
Q: What happened to “Eth1” and “Eth2”?
A: The Ethereum Foundation deprecated these terms in 2022 because they implied Eth2 would replace Eth1 as a new chain. In reality, the original chain continues as the execution layer, and the Beacon Chain is the consensus layer. Both are necessary parts of a single Ethereum network.
Q: Which execution layer client should I run as a node operator?
A: Any execution client works, but for network health, choose a minority client. Geth dominates (~65-70% share), which is a centralization risk. Nethermind, Besu, and Erigon are excellent alternatives that reduce network risk and are fully compatible.
Q: How does the execution layer affect Layer 2 scaling?
A: L2 solutions (Optimism, Arbitrum, zkSync) post transaction data or proofs to the execution layer. The Dencun upgrade (March 2024) added “blob” transactions to the execution layer specifically to reduce L2 data costs, cutting L2 fees by 10-100x.
Q: Can the execution layer be upgraded independently from the consensus layer?
A: Hard forks coordinate both layers simultaneously (e.g., Shanghai for execution + Capella for consensus = “Shapella”). However, the modular architecture means execution layer EIPs can be scoped to execution-only changes without requiring consensus layer modifications.
Related Terms
- Consensus Layer– Partner layer handling PoS validator coordination
- EVM (Ethereum Virtual Machine) – Core of the execution layer
- The Merge – Event that formally separated execution/consensus layers
- Engine API- Communication bridge between execution and consensus layers
- Geth (go-ethereum) – Most popular execution layer client
- Layer 2 – Uses execution layer for data availability and settlement
- EIP (Ethereum Improvement Proposal) – Process for upgrading the execution layer
