Episode Summary
Executive Summary: This episode examines MEV (maximal extractable value) in Ethereum, focusing on who should capture it: users, validators, or the protocol. Uri Klarman argues for minimizing front-running and eventually burning or rebating excess value, while Justin Drake frames MEV as something users should reclaim through better UX, rebates, and eventually MEV burn. They debate MEV blocker tools, PBS, and the future of decentralized block building.
Main Topics: What MEV is and how it works (Priority: 5/5): The guests define MEV as value captured by ordering transactions, front-running, back-running, and arbitrage, and walk through the roles of users, searchers, builders, relays, proposers, and attesters. Who should capture MEV (Priority: 5/5): A core disagreement is whether MEV should accrue mostly to users, validators, or the protocol. Justin argues for user sovereignty and protocol capture; Uri stresses validator power and optimal execution over rebates. MEV Blocker and MEV rebating (Priority: 5/5): They discuss emerging products like MEV Blocker, Flashbots MEV-Share, Backrun Me, Wallet Boost, and OpenMEV, which aim to protect users from front-running and return some value via rebates. Front-running versus back-running (Priority: 4/5): Uri argues front-running is harmful and should be prevented, while back-running can be useful if it rebates value to users or captures excess MEV without harming execution; Justin emphasizes optimal execution at the time of trade. MEV burn and protocol-level redistribution (Priority: 5/5): Justin explains MEV burn as analogous to EIP-1559, where contention fees are burned or redistributed to ETH holders, improving security, reducing validator incentives to reorg, and changing Ethereum economics. PBS, relays, and block-building centralization risks (Priority: 4/5): They debate proposer-builder separation (PBS), relay trust assumptions, and whether sophisticated block building will centralize around a few entities despite attempts to decentralize the pipeline. Future of real-time DeFi and pre-confirmations (Priority: 4/5): The conversation expands to pre-confirmations, restaking, and real-time execution, with Justin suggesting new consensus-level services may become a new category of extractable value.
Key Arguments: MEV does not disappear; it is redistributed among users, validators, searchers, builders, or the protocol depending on the system design. Front-running is the main harmful form of MEV because it worsens user execution by exploiting visible transaction intent. Back-running can be beneficial if it captures price dislocations without harming the original user and can be rebated. MEV blockers and similar products are order-flow auctions where searchers compete to return the most value to the user. Users have sovereignty over the value they create, but need better tools to realize it; current wallets and mempools are not enough. Validators have real power because they control inclusion and timing, so they can delay transactions or demand higher tips. MEV burn could improve Ethereum security by removing incentives for reorgs, double-signing, and validator competition over windfalls. Proposer-builder separation improves security by removing semi-trusted relays, but may not change the basic MEV distribution pipeline much. Exclusive order flow could centralize power among preferred searchers/builders and raise censorship and fairness risks. A long-term solution may require low-latency cryptography, threshold encryption, SGX, or intent-based systems rather than simple transaction-level rebates.
Data Points: Episode date: April 18, 2023 - The Unchained episode discussed Ethereum MEV distribution. MEV Blocker claimed value captured from users: $1.38 billion - Laura cites MEV Blocker’s stated estimate of profits extracted by MEV entities. Web3 project losses in 2022: nearly $4 billion - Mentioned in sponsor copy about security losses across crypto projects. Crypto.com sign-up bonus: $25 - Listener incentive for using the promo code in the ad read. Zero credit card fees promotion: first 7 days - Crypto.com app promotion for crypto purchases. Flashbots / ecosystem product count: about 12 teams - Laura notes many teams are building MEV-rebating / protection products. MEV split estimate: roughly 50/50 - Justin estimates about half of MEV is user-generated and half is excess latent MEV. User rebate estimate: 99% back to the user - Justin suggests well-defined user-generated MEV could mostly be rebated to the user. Validator share estimate: 1% - Justin frames validators as potentially receiving only a small residual share in his ideal system. Pre-confirmation latency: ~100 milliseconds - Justin cites rollup sequencer soft confirmations as a UX benchmark. Liquidity pool sizing example: 4 ETH mini-pools - Justin discusses Rocket Pool mini-pools in the context of MEV spikes and smoothing. Potential MEV spike example: 10 ETH or 100 ETH - Used to illustrate validator incentives versus smoothing / burn mechanics. Potential tax optimization: ~2.5x - Justin argues burn may be more tax-efficient than paying rewards as income. Validator stake threshold example: 100 gwei tip - Uri describes a scenario where validators might only include transactions above a higher minimum tip. Latency comparison: 100 ms to 10 ms - Justin says reducing latency yields diminishing user-value gains at very low levels.
Pivotal Quotes: "if somebody else Saw me what I'm doing, my transaction, my trade, and then did something in order to take advantage of what I'm about to do, that's unfair." — Uri Klarman: Uri’s concise definition of harmful front-running and why he sees it as the central MEV problem. "any MEV that's kind of generated by the user should go back to the user, and then all the rest should go to the protocol." — Justin Drake: Justin’s ideal MEV precedence list for where extractable value should accrue. "You want to prevent the front running, but enable the backrunning." — Justin Drake: Justin’s framing of the design goal for MEV-protection systems and user rebates.
Implications: The debate suggests MEV is shifting from covert extraction by validators toward explicit markets for order flow, rebates, and protocol-level capture. The outcome could reshape wallets, builders, and staking incentives while pushing Ethereum toward more user-protective, intent-based, and possibly burned/redistributed value flows.