Execution-level MEV is a category of Maximal Extractable Value (MEV) that is captured by manipulating the execution of transactions within a single block, after the block's contents have been proposed. This contrasts with consensus-level MEV, which involves influencing which transactions are included in a block. At the execution level, validators or specialized searchers reorder, insert, or censor transactions to profit from arbitrage, liquidations, or sandwich attacks by exploiting the deterministic state changes caused by transaction sequencing.
Execution-Level MEV
What is Execution-Level MEV?
A technical breakdown of MEV extraction that occurs during the processing of a single block, distinct from consensus-layer manipulation.
The primary mechanism for execution-level MEV is the mempool, where pending transactions are visible. Searchers run complex algorithms to detect profitable opportunities, such as price discrepancies between decentralized exchanges (DEXs). They then bundle their own transactions—often using flash loans for capital—and submit them to validators with high priority fees (tips) to ensure inclusion. The validator, acting as the block builder, can maximize its own revenue by selecting and ordering these profitable bundles, a process central to the proposer-builder separation (PBS) design.
Common strategies include DEX arbitrage, where a searcher buys an asset on one DEX and instantly sells it on another for a higher price, and the sandwich attack, where a victim's large trade is front-run and back-run to profit from the induced price movement. Liquidation bots also operate at this level, racing to be the first to repay undercollateralized loans and claim liquidation bonuses. These actions occur entirely within the Ethereum Virtual Machine (EVM) execution framework.
The impact of execution-level MEV is multifaceted. While it contributes to market efficiency by arbitraging price differences, it also imposes negative externalities like increased gas fees for regular users and latency races that centralize infrastructure. Solutions such as encrypted mempools, fair sequencing services, and in-protocol PBS aim to mitigate its harmful effects by reducing the visibility of opportunities or democratizing the capture of this value.
How Execution-Level MEV Works
An explanation of the technical process by which Maximum Extractable Value (MEV) is captured during the execution of transactions within a block.
Execution-level MEV refers to the value extracted by block producers through the strategic ordering, inclusion, and potential manipulation of transactions after they have been submitted to the mempool and are being processed within a block. This is the core, on-chain phase where theoretical MEV opportunities identified at the consensus layer are realized. The process is governed by the block producer's unilateral control over the block's construction, allowing them to insert, reorder, or censor transactions to maximize their profit from arbitrage, liquidations, or other profitable patterns.
The mechanism relies on the block producer's ability to run a local execution environment (often called a sandbox or simulator) to test different transaction orderings before committing the final sequence to the chain. Using specialized software like MEV-Boost relays or proprietary builders, they simulate the outcome of potential blocks, searching for the ordering that yields the highest total value from transaction fees and embedded MEV. This often involves inserting their own frontrunning or backrunning transactions to capture value from pending user trades or DeFi interactions they observe in the mempool.
A canonical example is a DEX arbitrage opportunity. A block producer sees a large pending swap that will move prices between two decentralized exchanges. In their local execution, they first insert their own arbitrage transaction to profit from the price discrepancy the pending swap will create, then include the user's swap, and finally add a second arbitrage transaction to capture any remaining imbalance. The entire sequence is atomic; it either succeeds fully or fails, ensuring the producer captures the spread without risk. This execution is made possible by the Ethereum protocol's design, which grants the block builder control over transaction sequencing.
The infrastructure for capturing execution-level MEV has evolved into a sophisticated ecosystem. Searchers identify opportunities and submit complex transaction bundles to builders via private channels or public auctions. Builders aggregate these bundles, simulate executions, and construct the most profitable block possible. This block header is then sold to validators (proposers) through a marketplace like MEV-Boost. The validator simply signs and proposes the received block, collecting a portion of the MEV revenue, while the builder and searchers take their share. This separation of roles professionalizes MEV extraction.
The impact of execution-level MEV is multifaceted. While it contributes to protocol revenue and can improve liquidity efficiency through arbitrage, it also creates negative externalities like network congestion and increased transaction costs for regular users. Furthermore, the ability to reorder transactions can lead to time-bandit attacks or the censorship of specific transactions. Solutions such as encrypted mempools, fair sequencing services, and proposer-builder separation (PBS) aim to mitigate these harms by reducing the information asymmetry and discretionary power of individual block producers.
Key Features of Execution-Level MEV
Execution-level MEV refers to value extracted by manipulating the execution of transactions within a single block, distinct from consensus-level MEV. It is the primary domain of searchers and builders.
Arbitrage
The most common form of execution-level MEV, where a searcher exploits price differences for the same asset across different Decentralized Exchanges (DEXs) or liquidity pools within a block.
- Example: Buying ETH on Uniswap where it's priced at $1,800 and instantly selling it on SushiSwap where it's priced at $1,805 in the same block.
- This activity is generally considered benign as it helps align prices across markets, but it extracts value from liquidity providers (LPs) via slippage.
Liquidation
A searcher repays a borrower's undercollateralized loan on a lending protocol (like Aave or Compound) to claim a liquidation bonus, often in a single atomic transaction.
- This is a necessary function for protocol health, ensuring bad debt is cleared.
- Searchers compete to be the first to submit the liquidation transaction, with profits coming from the liquidation penalty paid by the borrower.
- Advanced searchers use flash loans to fund the repayment without upfront capital.
Sandwich Trading
A malicious form of MEV where a searcher front-runs a victim's large DEX trade and back-runs it, profiting from the price impact.
- Process: The searcher detects a pending large buy order for a token. They buy the token first (front-run), causing the price to rise. The victim's trade executes at the higher price. The searcher then sells (back-run) at the inflated price.
- This results in negative externalities for the victim, including worse execution (slippage) and a net loss.
Time-Bandit Attacks
A theoretical but critical risk where a validator (or a coalition) reorganizes the blockchain to steal MEV that was already extracted in a prior block.
- This attacks the finality of transactions after they appear confirmed.
- It is a form of consensus-level MEV that directly targets execution-level profits, creating systemic risk.
- Mitigated by mechanisms like Proposer-Builder Separation (PBS) and enshrined proposer commitments.
Transaction Ordering Dependency
The core vulnerability enabling MEV, where the outcome of a transaction changes based on its position relative to others in the block.
- Example: A DEX trade's slippage depends on the state of the pool, which is altered by all preceding trades.
- This creates a combinatorial auction problem for block builders, who must find the most profitable sequence of transactions.
- Searchers bundle transactions to guarantee their desired order via Flashbots bundles or similar systems.
Builder and Searcher Markets
The specialized ecosystem that has evolved to capture execution-level MEV, consisting of searchers, builders, and relays.
- Searchers: Run algorithms to discover profitable opportunities and submit transaction bundles.
- Builders: Compete to construct the most valuable block by selecting and ordering bundles from searchers.
- Relays: Act as trusted intermediaries, receiving blocks from builders and forwarding them to validators, often providing censorship resistance lists.
Common Attack Vectors & Examples
Execution-level MEV refers to value extraction that occurs during the execution of a single transaction or block, often through manipulation of the transaction's execution path or state changes. These are distinct from consensus-layer MEV (e.g., reordering).
Generalized Frontrunning
Also known as backrunning or displacement. A searcher detects a pending transaction that will change the blockchain state in a profitable way (e.g., opening a new arbitrage opportunity). They then submit their own transaction with a higher gas fee, ensuring it executes immediately after the victim's transaction in the same block to capture the newly created value.
JIT (Just-In-Time) Liquidity
A defensive/competitive MEV strategy on Automated Market Makers (AMMs). A liquidity provider watches the mempool for large swaps that would earn high fees. They add liquidity to the targeted pool in the block immediately before the swap executes, capture the fees, and then remove their liquidity in the same block, minimizing exposure to impermanent loss.
Visualizing a Sandwich Attack
A step-by-step breakdown of how a common form of Maximal Extractable Value (MEV) is executed against a pending transaction on a blockchain.
A sandwich attack is a predatory trading strategy where a searcher (or bot) exploits the public visibility of pending transactions in a mempool to profit from predictable price movements. The attacker places two transactions—one before and one after the victim's trade—effectively "sandwiching" it. The core mechanism involves front-running the victim's buy order with the attacker's own buy, and then back-running it with a sell, capitalizing on the price impact the victim's trade was about to create. This is a prime example of Execution-Level MEV, where value is extracted by manipulating transaction ordering within a block.
The attack sequence begins with surveillance. The searcher's bots monitor the mempool for a large, pending swap transaction on a decentralized exchange like Uniswap. If the swap is sizable enough to move the market price of an asset pair (e.g., buying ETH with DAI), it presents an opportunity. The attacker's first transaction, the front-run, executes an identical buy order but with a higher gas fee, ensuring it is included in the block immediately before the victim's transaction. This initial purchase drives the asset's price up due to the constant product formula used by automated market makers (AMMs).
The victim's transaction then executes at this newly inflated price, purchasing less of the desired asset than anticipated. This trade further exacerbates the price movement. Finally, the attacker's second transaction, the back-run, sells the asset purchased in the front-run transaction. Because the price is now even higher due to the victim's trade, the attacker sells at a profit. The net effect is that the victim suffers increased slippage and a worse execution price, while the attacker pockets the difference, minus gas costs. The entire attack is typically bundled and submitted to a block builder or relay as a single, atomic bundle to guarantee the profitable sequence.
Visualizing this reveals the zero-sum (or negative-sum when including gas fees) nature of this MEV extraction. The profit for the searcher is a direct, quantifiable loss for the end-user. Defensive measures against sandwich attacks include using private transaction relays (like Flashbots Protect), setting strict slippage tolerances, breaking large trades into smaller batches, or utilizing DEX aggregators that employ sophisticated routing to minimize price impact. Understanding this visualization is crucial for developers designing trading systems and for users to comprehend the hidden costs of on-chain liquidity.
Key Actors in the Execution-Level MEV Ecosystem
Execution-level MEV (Maximal Extractable Value) involves a complex supply chain of specialized participants who compete to capture value from blockchain transaction ordering. These actors operate at the block production layer, each playing a distinct role in the search, capture, and distribution of MEV.
Searchers
Searchers are entities that run algorithms to detect profitable MEV opportunities, such as arbitrage or liquidations, within the public mempool or private order flows. They construct and submit transaction bundles to validators or builders, often paying a premium (a priority fee or bid) to have their bundles included. Their strategies include:
- Arbitrage bots exploiting price differences across DEXs.
- Liquidation bots closing undercollateralized loans.
- Sandwich traders inserting transactions around a target user swap.
Builders
A block builder is a specialized node that constructs full block contents by aggregating transactions and bundles from searchers and users. Post-EIP-1559 and with the rise of PBS (Proposer-Builder Separation), builders compete to create the most valuable block possible to sell to a validator. They optimize for:
- Maximizing total block value (fees + MEV).
- Ensuring state validity (all transactions must execute successfully).
- Censorship resistance and compliance with inclusion lists.
Proposers / Validators
The block proposer (a validator in Proof-of-Stake) is the entity with the right to propose a block for a given slot. In a PBS model, the proposer's role is to select the most profitable block header from a competitive builder market. The proposer's key decisions involve:
- Choosing the builder's block offering the highest bid.
- Potentially enforcing censorship resistance rules via inclusion lists.
- Ultimately signing and propagating the selected block to the network.
Relays
A relay is a trusted intermediary in the PBS pipeline that facilitates communication between builders and proposers. It receives encrypted block bids from builders and reveals them to the proposer after selection, preventing theft of bundle strategies. Key relay responsibilities include:
- Bid aggregation from multiple builders.
- Data availability guarantee for block bodies.
- Fairness enforcement through neutral, verifiable auction rules.
- Censorship resistance monitoring.
Users
End-users submitting standard transactions are foundational to the MEV supply chain. Their transactions create the opportunities (e.g., large DEX swaps) that searchers exploit. Users can employ strategies to protect themselves:
- Using private transaction relays (e.g., Flashbots Protect, Taichi Network) to avoid frontrunning.
- Setting tighter slippage tolerances.
- Utilizing MEV-aware protocols like CowSwap that offer batch auctions.
Order Flow Auctions (OFAs) & Marketplaces
Order Flow Auctions are mechanisms that create a competitive market for user transaction flow. Instead of sending transactions to the public mempool, users or wallets sell their transaction order flow to the highest bidder among searchers/builders. This aims to:
- Democratize MEV capture, returning value to the user.
- Improve privacy and execution quality.
- Reduce negative externalities like sandwich attacks. Examples include CowSwap's solver competition and Rabbithole.
Security Considerations & User Impact
Execution-level MEV refers to value extraction that occurs during the processing of a transaction within a block, primarily through transaction ordering and inclusion. This layer directly impacts user experience, security, and fairness.
Sandwich Attacks
A predatory trading strategy where a searcher front-runs a victim's large DEX trade and back-runs it, profiting from the price slippage they create. This is the most common form of harmful MEV.
- Mechanism: The attacker places two orders around the victim's transaction.
- Impact: The victim receives a worse price, paying an implicit MEV tax.
- Example: A user's large ETH→USDC swap is sandwiched, increasing their effective price.
Time-Bandit Attacks
A severe security threat where a validator or proposer reorgs (reorganizes) the blockchain to steal already-included MEV, violating consensus finality.
- Mechanism: The validator discards a recent block to produce a new one with a more profitable transaction order.
- Impact: Undermines blockchain security, creates uncertainty for users and applications.
- Mitigation: Relies on proposer-builder separation (PBS) and strong consensus incentives.
User Impact: Slippage & Failed Transactions
Execution-level MEV directly degrades the end-user experience in two primary ways:
- Increased Slippage: Attacks like sandwiching force users to set higher slippage tolerances, which can be exploited.
- Transaction Failure: Frontrunning bots can cause user transactions to revert by changing the state (e.g., draining liquidity) before the user's transaction executes, resulting in lost gas fees.
The Role of Searchers & Builders
The MEV supply chain separates roles to manage execution complexity and risk.
- Searchers: Run algorithms to detect profitable opportunities and bundle transactions.
- Builders: Compete to construct the most valuable block from searcher bundles and public mempool transactions.
- Proposer: The validator who simply selects the highest-paying block from builders. This separation (PBS) aims to democratize access and reduce validator-level centralization risks.
Privacy Solutions: SUAVE & Encrypted Mempools
Emerging architectures designed to mitigate harmful MEV by obscuring transaction intent.
- SUAVE (Single Unified Auction for Value Expression): A dedicated chain for preference expression and block building, separating transaction privacy from execution.
- Encrypted Mempools: Use cryptographic techniques (e.g., threshold decryption) to hide transaction content until block inclusion, preventing frontrunning.
- Goal: Preserve fair ordering and reduce the information asymmetry bots exploit.
Economic Externalities & Network Congestion
MEV extraction creates negative externalities for the broader network.
- Gas Price Auctions: Bots engage in priority gas auctions (PGAs), bidding up base fee prices to get their bundles included, increasing costs for all users.
- Network Congestion: The flood of competing MEV transactions can clog the mempool, delaying ordinary transactions.
- Centralization Pressure: The high rewards from MEV can incentivize stake centralization among validators with sophisticated extraction capabilities.
Mitigation & Redistribution Strategies
Execution-level MEV (Miner/Validator Extractable Value) refers to profit extracted by block producers by reordering, inserting, or censoring transactions within a single block. These strategies aim to mitigate its negative externalities and redistribute the captured value.
MEV Auctions
A market-based mechanism where the right to extract MEV from a block is auctioned to the highest bidder, with proceeds often shared with the network or users.
- First-Price Auctions: Builders bid for the right to have their block accepted by the proposer (as seen in MEV-Boost).
- Order Flow Auctions (OFAs): Users or searchers auction their transaction bundles to builders before they reach the public mempool, capturing value for the user.
- Goal: Transparently price MEV and redistribute profits.
Fair Sequencing Services (FSS)
A class of protocols that enforce a canonical, fair ordering of transactions (e.g., first-come-first-served) before they are included in a block, neutralizing many forms of harmful MEV.
- Core Principle: Decouple transaction ordering from execution, using a decentralized sequencer or consensus mechanism to establish order.
- Mitigates: Frontrunning, time-bandit attacks, and other forms of order-dependent exploitation.
- Implementation: Often used in rollups (e.g., Arbitrum's Timeboost) or as standalone networks like Astria.
MEV Redistribution (Burn & Socialization)
Protocol-level strategies to capture extracted MEV and redistribute it to the broader network, rather than letting it accrue solely to searchers and validators.
- MEV Burn: A portion of MEV profits are permanently destroyed (burned), as with Ethereum's inclusion fee burn (EIP-1559), which burns the base fee, a component of MEV.
- MEV Socialization: Captured value is distributed to a common pool, such as the protocol treasury or directly to token holders/stakers.
- Goal: Align MEV extraction with long-term network health and user benefit.
Execution-Level MEV vs. Other MEV Types
A comparison of MEV extraction based on the layer of the blockchain stack where the opportunity originates and is captured.
| Feature / Dimension | Execution-Level MEV | Consensus-Level MEV | Application-Level MEV |
|---|---|---|---|
Primary Layer of Origin | Block execution / EVM | Block proposal / consensus | Application logic (e.g., DEX, lending) |
Key Actor | Block builder, searcher | Validator / proposer | Searcher, user, protocol |
Extraction Method | Transaction ordering & inclusion within a block | Block timing, empty blocks, consensus manipulation | Arbitrage, liquidations, front-running specific app states |
Example | Sandwich attack on a DEX trade | Timestamp manipulation, proposer boost exploitation | Liquidation cascade in a lending protocol |
Mitigation Focus | Encrypted mempools, commit-reveal schemes | Proposer-Builder Separation (PBS), in-protocol randomness | Circuit breakers, fair ordering within the app |
Protocol-Level Risk | High (centralizes block building) | Very High (threatens consensus security) | Medium (threatens application solvency) |
Visibility | Opaque, occurs inside the built block | Partially transparent on-chain | Transparent, visible in public mempool |
Dominant on Ethereum Post-Merge? |
Frequently Asked Questions (FAQ)
Answers to common technical questions about how Maximal Extractable Value (MEV) is captured during transaction execution on Ethereum and other blockchains.
Execution-level MEV is the value extracted by block builders and validators by strategically ordering, including, or excluding transactions within a block they produce. It works by leveraging the ability to see the pending transaction pool (mempool) and reordering transactions to create profitable opportunities, such as front-running a large DEX trade or performing an arbitrage between decentralized exchanges. The process involves sophisticated bots that monitor for profitable patterns, submit their own transactions with higher gas fees to ensure inclusion, and manipulate the sequence to capture the value difference. This activity occurs during the block construction phase, before the block is proposed and finalized on-chain.
Get In Touch
today.
Our experts will offer a free quote and a 30min call to discuss your project.