What Is MEV on Layer 2s? How It Differs from L1

MEV, or maximal extractable value, on layer-2 chains refers to the profit that can be extracted by controlling the order, inclusion, or exclusion of transactions within a block or batch — the same basic concept as on Ethereum mainnet, but with a critical structural difference: most L2s today have a single, centralized sequencer controlling transaction ordering, rather than a decentralized, competitive set of block producers.

MEV on L1: a quick refresher

On Ethereum mainnet, MEV typically arises because validators (or the block builders they work with, under the current proposer-builder separation model) choose which transactions to include and in what order, and can profit from strategies like arbitrage, liquidations, and sandwich attacks by exploiting that ordering power. This is a well-studied area, with an entire supply chain of specialized searchers and builders competing to capture this value, and a live marketplace determining who gets to include which transactions.

How the picture changes on most L2s

Most rollups and validiums today run with a single sequencer, usually operated by the project's core team, responsible for ordering every transaction on the chain. This concentrates MEV-extraction power much more heavily than Ethereum's competitive, decentralized block-building market. A centralized sequencer is, in principle, in a position to reorder transactions for its own benefit, front-run visible pending transactions, or sell privileged ordering access — with far less competitive pressure checking that behavior than exists on Ethereum's base layer today.

This isn't necessarily happening in practice on any particular chain — many sequencer operators have public commitments around fair ordering, and some chains have moved toward first-come-first-served or time-based ordering rules specifically to reduce this risk. But structurally, the concentration of ordering power in one operator is a meaningfully different trust model than Ethereum's more competitive market, and it's worth understanding rather than assuming L2 automatically means "no MEV risk."

Cross-rollup MEV: a newer and less understood problem

As the number of active rollups has grown, a newer category of MEV has emerged: opportunities that span multiple chains, extracted by parties who can observe pending transactions or arbitrage opportunities across several rollups simultaneously. This is much harder for any single rollup's own mitigations to address, since the extraction happens across chain boundaries rather than within one chain's own ordering. Efforts like shared sequencers are partly aimed at giving the ecosystem more visibility and potential control over this cross-chain MEV, though solutions remain early-stage.

Comparing MEV dynamics: L1 vs. typical L2 today

Aspect	Ethereum L1	Typical L2 today
Ordering control	Competitive market of builders/validators	Usually one centralized sequencer
Transparency of ordering rules	Well-studied, PBS-based market	Varies by chain, often less transparent
Cross-chain MEV	Not directly applicable (single chain)	Growing concern as rollups proliferate
User-facing mitigations	MEV-protected RPCs, private mempools	Varies; fewer mature options currently

Practical implications for users

The most direct consequence for ordinary users is the same core risk mainnet users already know: sandwich attacks and unfavorable execution on decentralized exchange trades. Using reasonable slippage settings and being cautious with large trades on any DEX — whether on L1 or an L2 — remains sound practice, as covered in our DEX vs CEX comparison. Beyond that, it's worth treating a chain's sequencer decentralization status as part of your overall risk assessment, alongside the other criteria in our evaluating L2 decentralization checklist.

Encrypted mempools as a mitigation for sequencer-level MEV

One mitigation some L2s and infrastructure providers have explored is encrypting pending transactions so that even the sequencer itself can't see their contents until after the ordering decision is locked in. This directly addresses one of the more concerning forms of sequencer-level MEV — a centralized operator using visibility into pending transactions to front-run or reorder them for its own benefit — by removing that visibility in the first place, rather than merely trusting the operator not to misuse it. This approach is still relatively early in adoption across the L2 landscape, and its practical effectiveness depends heavily on correct implementation, since encryption schemes that can be circumvented or that introduce their own delays and failure modes wouldn't meaningfully improve on the status quo.

Why sequencer decentralization is the long-term fix

Ultimately, most proposed mitigations for L2 MEV concerns — encrypted mempools, fair ordering rules, shared sequencers, and based rollups that tie ordering to Ethereum's own decentralized proposer set — point toward the same underlying conclusion: concentrating ordering power in a single, centralized sequencer is the root structural issue, and the long-term fix is reducing or eliminating that concentration rather than layering ever more mitigations on top of a fundamentally centralized design. Progress on this front varies significantly by chain, which is why sequencer decentralization status remains one of the more important, and still evolving, factors to check when evaluating any specific L2's trustworthiness.

Bottom line

MEV exists on layer-2 chains just as it does on Ethereum mainnet, but the structural picture is different: most L2s currently concentrate transaction ordering power in a single sequencer rather than a competitive market of builders, which changes who is positioned to extract MEV and how transparently. A newer, less-solved problem is cross-rollup MEV, extracted by parties observing multiple chains at once — an area shared sequencing and related infrastructure are still working to address. Treat sequencer decentralization as a genuine part of a chain's risk profile, not an afterthought.