MEV: understand how transaction ordering changes outcomes

Crypto Lived / Knowledge library · Infrastructure · 2 min read

Order can have economic value

Maximal extractable value describes value obtained through transaction inclusion, exclusion, or ordering beyond ordinary protocol rewards. Searchers, builders, proposers, and other participants can play different roles depending on the network architecture. Calling all of them “miners” obscures modern transaction supply chains.

Some ordering activity helps align prices or execute necessary liquidations. Other strategies exploit a user’s execution constraints. Evaluate the particular mechanism and who gains or loses instead of treating MEV as a single uniformly beneficial or harmful activity.

A hypothetical sandwich

A user submits a large swap with a wide minimum-output allowance. An observer can trade before it in a way that worsens the user’s price, then trade after it to reverse inventory and potentially capture value. Whether the strategy succeeds depends on ordering, liquidity, fees, competition, and the user’s allowed execution bounds.

The user’s transaction can succeed exactly as authorized while delivering a poor result. This is why successful execution and favorable execution must be judged separately. A generous slippage setting is permission for a range of outcomes, not merely a harmless technical aid to transaction completion.

Contrast that with arbitrage between two pools whose prices differ. A searcher may buy in one and sell in the other, moving prices closer. The existence of profit does not establish a sandwich; the sequence and its relation to another user’s trade matter.

Visibility and routing change exposure

Public pending transactions reveal information that can be used before inclusion. Private submission routes seek to limit that exposure or change how transaction information is shared. Their protections depend on service behavior, downstream recipients, supported networks, and what happens during fallback.

A private route is not a blanket promise of best price, anonymity, or guaranteed inclusion. Read whether transactions may later be broadcast publicly, how cancellation works, which builders receive them, and which trade types are covered. A user switching endpoints without understanding those policies can overestimate the protection.

For a trading workflow, compare final received assets, fees, failure rates, and route behavior across representative conditions. A single favorable transaction does not establish a permanent advantage. Likewise, one adverse price move does not prove intentional ordering manipulation without examining the transaction sequence.

Practical exposure review

  • Use deliberate minimum-output bounds rather than automatically maximizing tolerance.
  • Check order size relative to route liquidity and expected price impact.
  • Read private-route information-sharing, fallback, and cancellation policies.
  • Distinguish normal price movement from evidence of an ordering strategy.
  • Compare actual receipts and balance changes with the quote you authorized.

Applications can improve outcomes by exposing execution bounds clearly, simulating routes, and explaining pending states. Infrastructure-level mitigation and careful user authorization complement each other; neither makes the other irrelevant.

Frequently asked questions

Is every arbitrage trade a sandwich attack?

No. Arbitrage can exploit a preexisting price difference without targeting a particular user’s pending trade. The ordering and economic sequence determine the mechanism.

Does private submission guarantee immediate execution?

No. Inclusion still depends on network conditions, fee terms, recipient infrastructure, and service policy. Privacy and timing are separate properties.

Primary references