How Ethereum Validators Earn MEV and Priority Tips: Execution and Consensus Rewards Explained

Ethereum validators earn compensation through two separate mechanisms: base issuance from the consensus layer and transaction tips from the execution layer. When users submit transactions, they include priority fees to secure block space, while specialized block builders pay validators out of the profit they extract by ordering these transactions. Understanding validator economics requires separating these two distinct streams of revenue.

The Dual-Layer Architecture

The Ethereum network operates via two distinct layers working in tandem. The consensus layer manages the proof-of-stake mechanism, tracking validator balances, attestations, and block proposals. The execution layer processes smart contracts, user transactions, and network state changes ¹.

Validators receive different types of rewards from each layer. The consensus layer provides deterministic rewards in the form of newly minted $ETH. Validators earn these by successfully proposing blocks, attesting to the validity of other blocks, and participating in sync committees. The execution layer provides variable rewards derived from user transactions, specifically priority fees and Maximal Extractable Value (MEV).

Priority Fees and Network Congestion

Under the Ethereum fee market structure established by EIP-1559, every transaction pays a base fee and an optional priority fee. The base fee is algorithmically determined by network demand and is permanently burned, effectively removing it from the total ETH supply ².

To incentivize validators to include a specific transaction in a block, users attach a priority fee, often called a tip. During periods of low network activity, a minimal tip is sufficient for block inclusion. During high congestion, users increase their priority fees to outbid others for limited block space. If a validator builds a block manually, they collect all the priority fees attached to the transactions they include.

MEV-Boost and Block Builder Bids

Instead of building blocks themselves, most validators outsource this process to specialized actors via software called MEV-Boost. This creates a marketplace where searchers find profitable transaction orderings (such as arbitrage or liquidations) and submit them to block builders. Builders aggregate these transactions into full blocks and bid for the right to have their block proposed by the validator assigned to the current slot ³.

When using MEV-Boost, the winning builder pays the validator a single lump sum, known as the builder bid. This bid represents the total execution layer payment to the validator.

Consider a numerical example. Suppose a validator is selected to propose a block. They receive consensus layer issuance (e.g., 0.025 ETH) for the proposal. On the execution layer, a block builder using MEV-Boost submits a bid of 0.08 ETH to have their block proposed. This 0.08 ETH bid already accounts for the priority fees attached to the transactions inside that block, plus the builder's MEV profits. The validator's total compensation for this block is 0.105 ETH (0.025 ETH issuance + 0.08 ETH builder bid). The priority fees are not paid separately on top of the builder bid; they are captured by the builder and passed on to the validator through the bid itself.

The Block Proposal Lottery

Consensus layer attestation rewards are highly predictable, as active validators are called upon to attest once every epoch (approximately every 6.4 minutes). Block proposals, however, are assigned randomly. A validator might go weeks without proposing a block, or propose multiple blocks in a single week ¹.

Because execution layer rewards (priority fees and MEV) are only earned when a validator successfully proposes a block, validator revenue exhibits high variance. A validator that happens to propose a block during a volatile market event might capture a builder bid worth several ETH, while another validator might only capture minimal tips during a quiet period.

Smoothing Pools for Solo Stakers

To combat the unpredictable nature of execution layer rewards, some solo stakers and node operators join smoothing pools. A smoothing pool aggregates the execution layer rewards from all participating validators and distributes them proportionally based on each validator's active stake and performance.

By pooling these unpredictable payouts, operators achieve a more stable, predictable yield that mirrors the network average, rather than relying on the luck of block proposal assignments. This mechanism functions similarly to mining pools in proof-of-work systems, though it only aggregates the execution layer tips and MEV bids, leaving consensus layer issuance independent. Smoothing pools are often discussed alongside Distributed Validator Technology (DVT) as methods to reduce operational variance and risk for smaller node operators.

Common Misconceptions

• Validators extract MEV directly: Under the current MEV-Boost architecture, validators do not search for or extract MEV themselves. They simply sell the block proposal right to a builder who has done the extraction work.
• High gas prices equal high staking yields: While high network congestion increases priority fees, the base fee is burned. Sustained high gas prices primarily result in ETH deflation rather than directly proportionally increasing validator yield.
• Priority fees are paid on top of builder bids: A common error is double-counting execution rewards. The builder bid submitted via MEV-Boost represents the entire execution layer payout, absorbing the priority fees from the transactions within the block.

What to Watch

Ethereum researchers are actively developing in-protocol Proposer-Builder Separation (ePBS). This upgrade would enshrine the separation of block builders and block proposers directly into the Ethereum consensus protocol, potentially eliminating the need for third-party MEV-Boost relays and altering the trust assumptions involved in capturing execution layer rewards. Changes to maximum effective balances, such as Ethereum Validator Consolidation, will also impact how institutional operators manage proposal probability across large fleets of validators.