URL copied — paste it as a website source in a new notebook
Summary
This article provides a comprehensive technical deep-dive into how Flashbots fundamentally transformed Ethereum's MEV (Maximal Extractable Value) landscape by moving MEV extraction off-chain through custom client software and relay infrastructure. The narrative begins by establishing the foundational mechanics of the Ethereum mempool—a local database of pending transactions that varies across nodes based on geography and peer connections—and then traces how transactions are prioritized during block construction, with local transactions receiving priority over remote transactions and high gas prices determining inclusion order. The author meticulously examines the original "Priority Gas Auction" (PGA) system where competing bots would continually escalate gas prices to win block space, resulting in losers still paying gas for reverted transactions.
The bulk of the article traces the evolution of MEV-Geth from its initial v0.1 release through v0.6, explaining how each version introduced architectural innovations that gave miners progressively more power to capture MEV while improving efficiency. Version 0.1 introduced MEV bundles—atomic collections of transactions submitted through the Flashbots relay that would either execute together or not at all—changing the auction mechanism from pure gas price competition to an "Adjusted Gas Price" calculation that considers both direct coinbase payments and gas fees. Subsequent versions introduced bundle merging (v0.2), EIP-1559 compatibility (v0.3), Megabundles with signature verification (v0.4), and private transactions (v0.6), each iteration solving real problems like bundle stuffing and computational overhead.
The article explains in precise technical detail how MEV-Geth code actually implements these concepts, walking through Ethereum's Geth client source code to show the TxPool struct, transaction ordering via heap data structures, and the mathematical formula for determining bundle profitability. A critical innovation discussed is the shift from miners having to merge bundles themselves (computationally expensive) to the Flashbots relay pre-merging bundles into "megabundles" and simply presenting the highest-profit option, reducing node computational burden while requiring trust in the relay.
The piece concludes by positioning MEV-Geth as a precursor to MEV-Boost, which will implement Proposer-Builder Separation (PBS) in post-merge Ethereum, where validators (not miners) receive blinded blocks from competing builders, preventing validators from stealing MEV while still allowing them to opt into MEV rewards. Throughout, the author emphasizes how Flashbots solved a crucial coordination problem: moving MEV extraction from destructive on-chain bidding wars that waste block space and user funds, to an off-chain sealed-bid auction mechanism that preserves block space and failed transaction costs while still allowing miners to maximize revenue.
Key Takeaways
The mempool is not global—each Ethereum node maintains its own local database of pending transactions with different contents based on geography and peer connections, fundamentally affecting which transactions miners see and can include.
Before Flashbots, 'Priority Gas Auctions' forced competing bots to continuously bid up gas prices in 13.5-second block times, wasting block space and forcing losers to pay gas on reverted transactions, creating a destructive on-chain arms race.
MEV-Geth v0.1 introduced the 'Adjusted Gas Price' formula (total ETH sent to miner Ă· total gas used), shifting MEV extraction from pure gas bidding to a profitability metric that accounts for direct coinbase payments, fundamentally changing the game.
Bundle merging (v0.2) added bundle stuffing protections by excluding gas fees from transactions already in the mempool, preventing searchers from artificially inflating bundle profitability by including public transactions.
Megabundles (v0.4) offloaded computational complexity from miners to the Flashbots relay, which pre-merges bundles and returns only the single most profitable option, reducing computational load while requiring trust in relay verification.
MEV-Geth allowed reverting transactions in bundles because with bundle merging, transaction order is uncertain—a searcher might want to include a liquidation as allowed to revert in case another bundle executes first and changes state.
The evolution from v0.1 to v0.6 represents systematic optimization of the miner/searcher auction mechanism, balancing profit maximization with node performance, computational overhead, and private transaction support.
MEV-Boost represents the post-merge successor to MEV-Geth, implementing Proposer-Builder Separation where validators receive blinded blocks from builders, preventing validators from stealing MEV while allowing maximum revenue capture.
By moving MEV extraction off-chain into sealed-bid auctions, Flashbots eliminated wasted transactions and block space while making MEV extraction predictable and profitable, solving a major coordination problem.
Flashbots' relay infrastructure shifted power dynamics by letting miners outsource block construction to a relay that aggregates the most profitable opportunities from hundreds of searchers automatically.
About
Author: noxx
Publication: Substack (noxx newsletter)
Published: 2022-07
Sentiment / Tone
Highly technical and educational with a matter-of-fact tone; the author presents Flashbots as a pragmatic solution to a real coordination problem rather than making moral judgments. The piece is deeply explanatory and assumes reader sophistication—it doesn't apologize for MEV's existence but instead demonstrates how Flashbots made MEV extraction more efficient and less wasteful. There's implicit respect for the engineering elegance of the solutions across versions, with the author methodically showing how each iteration solved specific problems (bundle stuffing, computational overhead, trust requirements). The tone is neither celebratory nor critical of MEV itself, but rather analytical and instructive about how infrastructure evolved to manage it.
Related Links
Order Flows: Kingmaker of the Block Builders đź‘‘ - noxx Direct follow-up exploring how exclusive order flows concentrate power in post-merge builder market, examining risks of wallet providers like Metamask dominating if they monetize transaction flows.
Flashbots Official Website Primary source for Flashbots' mission, products (MEV-Boost, Protect), and research direction; provides official context for the evolution traced in the article.
Flashbots MEV-Geth Repository The actual implementation discussed—readers can verify code examples and trace version evolution (v0.1-v0.6) described in the technical walkthrough.
Maximal Extractable Value (MEV) - ethereum.org Official Ethereum documentation on MEV concepts (frontrunning, sandwich attacks, MEV-Boost) that the article assumes readers understand; provides authoritative context.
MEV-Boost in a Nutshell Explains MEV-Boost as the post-merge continuation of MEV-Geth's work, showing how Proposer-Builder Separation implements architectural trends discussed in the article's conclusion.
Research Notes
**Author Background**: noxx (@noxx3xxon) is an Ethereum researcher specializing in EVM internals and MEV, publishing Substack articles with deep technical dives into Ethereum architecture. The author demonstrates working-level expertise by walking through actual Geth source code, explaining heap data structures, transaction nonce ordering, and state simulation. This is not surface-level analysis. noxx's follow-up "Order Flows: Kingmaker of the Block Builders" extends MEV analysis to post-merge implications, exploring how wallet providers could monopolize order flows.
**Historical Context**: Published in mid-2022 when Ethereum's Proof-of-Stake transition was imminent. MEV-Geth was developed 2020-2021 during PoW era; the article serves as both retrospective on how MEV-Geth solved PoW-era problems and bridge to understanding why PBS was necessary. The timing was critical—MEV-Boost was still being designed for post-merge deployment.
**Broader Conversation**: Part of intense MEV research spanning Flashbots researchers, Ethereum core developers, and academics. Concurrent discussions included MEV's centralizing effects, exclusive order flow risks, and whether MEV could be minimized through protocol design (threshold encryption, encrypted mempools). The article notably treats MEV as engineering problem, not moral issue.
**Reliability and Credibility**: Code examples come directly from Ethereum's public go-ethereum and Flashbots' public mev-geth repositories, making claims highly verifiable. Technical explanations are accurate and detailed—developers building MEV infrastructure regularly cite similar analyses. Article is well-regarded in technical communities with no significant factual critiques emerging.
**Impact and Reception**: Became a standard reference for developers trying to understand MEV infrastructure. Comments from other Ethereum researchers ("awesome work noxx!") indicate it filled a knowledge gap—few accessible yet technically rigorous explainers of MEV-Geth internals existed at the time.
**Potential Limitations**: Focuses entirely on technical implementation details without deeply exploring MEV's negative externalities—sandwich attacks, frontrunning, and user harm. While mentioned in passing, the article doesn't center these concerns. Readers seeking MEV's ethical dimensions or solutions beyond Flashbots would need supplementary sources.
Topics
MEV (Maximal Extractable Value)Flashbots architecture and evolutionEthereum mempool mechanicsMEV-Geth client implementationBlock construction and mining auctionsProposer-Builder Separation (PBS)