Flashbots
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Write
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee
    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Versions and GitHub Sync Sharing URL Help
Menu
Options
Engagement control Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Write
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee
  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       owned this note    owned this note      
    Published Linked with GitHub
    8
    Subscribed
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Subscribe
    --- tags: research --- # Quantifying Realized Extractable Value _Alejo Salles -- Flashbots_ _Maximal_ (formerly _Miner_) _Extractable Value_ ($\textrm{MEV}$) is the value that can be extracted from a blockchain by any agent without special permissions. Considering this permissionless nature, any agent with transaction ordering rights will be in a privileged position to perform the extraction. In Proof of Work blockchains, it is miners who determine transaction ordering within a block, hence the former "_miner_" term. In practice, bot operators seek to extract $\textrm{MEV}$ by either paying high fees to increase the likelihood that their transactions are mined, or by fine-tuning their gas price choices in order to "time" their transactions right, as is the case when backrunning an oracle update to perform a liquidation. Despite much recent discussion about the topic and, in particular, its associated risks for the Ethereum protocol, we still lack a cohesive formal model for quantifying $\textrm{MEV}$ extraction. At [Flashbots](flashbots.net), we have released an [$\textrm{MEV}$ explorer](https://explore.flashbots.net/) where we shed light on various aspects of this phenomenon. While we do elaborate on our metrics in the site, they still lack a formal definition. Here, we attempt to provide a unifying operational framework that consolidates $\textrm{MEV}$ extraction metrics, focusing on the Ethereum network[^1]. ## General Considerations The first important point to make is that $\textrm{MEV}$ is a theoretical quantity that we can only approach asymptotically. Unforseen extraction methods can and will be devised (every new DeFi hack is an $\textrm{MEV}$ extraction event). Hence, we will here focus instead on the _Realized Extractable Value_, notated $\textrm{REV}$, where $\textrm{REV} \leq \textrm{MEV}$. In other words, $\textrm{REV}$ is the _actual value_ extracted from the blockchain from $\textrm{MEV}$ opportunities[^2]. We note that there's two classes of actors in the system, _searchers_ and _miners_. We use the generic label _miner_ for actors that bear the privileged role of transaction inclusion and ordering. _Searchers_ are any non-privileged actors aiming to profit from these opportunities. Crucially, miners can also act as searchers. Extracting $\textrm{MEV}$ incurs externalities, like increasing gas costs for all users of the network, or bloating the chain. We won't dwell into the implications of these externalities here, but we will make them manifest in the model. For more on this and the "$\textrm{MEV}$ Crisis", be sure to check our [Flashbots introductory post](https://medium.com/flashbots/frontrunning-the-mev-crisis-40629a613752). We are now ready to begin building our framework, starting with a simple model that ignores direct miner payments and searcher competition and other externalities like opportunity checks. We will revisit the model to account for these at a later stage. ## Extraction Model We begin with a model where a single searcher performs an $\textrm{MEV}$ extraction, sharing proceeds with the block miner via _gas fees only_. We further assume that miners order transactions by descending gas price, which approximates well their optimal strategy and is the default in Ethereum node software. We decompose the opportunity's $\textrm{REV}$ in two terms: $$\textrm{REV} = \textrm{REV}_S + \textrm{REV}_M, \tag{1}$$ where $\textrm{REV}_S$ is the value that goes to the searcher, and $\textrm{REV}_M$ is the value that goes to the miner. Note that, as we expand on below, $\textrm{REV}$ already encompasses the opportunity's _extraction costs_ (_i.e._ the actual $\textrm{REV}$ of an opportunity depends on the gas price of the network at extraction time[^3]). Let's dive into the two different terms. The searcher $\textrm{REV}$ is composed by: $$\textrm{REV}_S = V_{in} - V_{out} - g_{\textrm{MEV}}.s_{\textrm{MEV}}, \tag{2}$$ where $V_{out}$ is the value that flows from the searcher to the blockchain in the transactions performing the extraction (excluding gas); $V_{in}$ is the value flowing from the blockchain to the searcher; $g_{\textrm{MEV}}$ is the gas price of the transactions; and $s_{\textrm{MEV}}$ is their _size_, _i.e._ the total amount of gas they consumed. $V_{out}$, $V_{in}$, and $g_{\textrm{MEV}}$ are denominated in the base network currency (ETH), while $s_{\textrm{MEV}}$ is in units of gas. Separating the gas term from $V_{out}$ will be helpful in quantifying the extraction costs, and it is also how we compute $\textrm{REV}_S$ in practice. We use "the blockchain" loosely here to refer to any other addresses (corresponding to smart contracts or EOAs) that are not the EOA of the extracting transactions, or smart contracts controlled by the searcher. Note that identifying these is a heuristic-guided process based on known searcher patterns, and by all means fallible. Also, we stress that any ancillary transactions related to the $\textrm{MEV}$ extraction (like the "meat" in a sandwich attack) are _not_ part of the set of transactions that contribute to the above variables. Turning to the miner side, we have: $$\textrm{REV}_M = s_{\textrm{MEV}}.(g_{\textrm{MEV}}-g_{eff}), \tag{3}$$ where $g_{eff}$ is the _effective gas price_ of the transactions that _would have been included_ in the block had the opportunity not been taken. $\textrm{REV}_M$ is thus defined to include the _opportunity cost_ the miner incurs by including the $\textrm{MEV}$-extracting transactions. As transactions in the mempool are ephemeral, it is impossible to measure $g_{\textrm{eff}}$ _a posteriori_ from only blockchain data and logs. We resort to an approximation that also serves as a lower bound for the value realized by the miner: $$\textrm{REV}_M \gtrsim s_{\textrm{MEV}}.(g_{\textrm{MEV}}-g_{tail}), \tag{4}$$ where $g_{tail}$ is the gas price of the last transaction in the block[^4]. Plugging equations (2) and (4) we get for the total realized value: $$\textrm{REV} \gtrsim V_{in} - V_{out} - s_{\textrm{MEV}}.g_{tail}. \tag{5}$$ In this rendition the miner and searcher roles are blurred, but we can clearly identify the _extraction costs_ of the opportunity, given by the subtrahend $s_{\textrm{MEV}}.g_{tail}$. Finally, note that the value split between searcher and miner at this stage is entirely decided by the choice of $g_{\textrm{MEV}}$, which is in turn affected by the nature of the opportunity and the presence of other searchers trying to exploit it. ## Including Externalities The scenario presented so far ignores the fact that while single-searcher successful value extractions exist, they constitute only a small fraction of all $\textrm{MEV}$ activity. In practice, each time an opportunity arises in the network, several searchers will try to take it by engaging in Priority Gas Auctions or submitting multiple competing transactions to backrun a target state change. Moreover, sometimes searchers perform onchain calculations to validate the existence of an opportunity ("preflights"). When these checks fail, there is no value extracted, but miners will still benefit from the collected gas fees. Note, however, that all of this activity is zero-sum: all costs incurred by searchers by competing with each other, validating state, etc., directly becomes miner profit. From the miner's perspective, the fee paid by a searcher's preflight is no different from, say, the one coming from an unsuspecting token transfer. This goes to say that none of this value amounts to a contribution to the ${\textrm{REV}}$. However, it is of interest of us to quantify it, since it is precisely what generates trouble for regular users of the network not involved in this commerce. We will then need to take a broader view of $\textrm{MEV}$, and define a new term, the _Extractable Value Cost_ (${\textrm{EVC}}$), which summarizes all the extra value _induced_ by $\textrm{MEV}$ extraction activity, that is not part of the extracted value itself. With this definition, we have: $$\textrm{Total MEV Activity} = \textrm{REV}_S + \textrm{REV}_M + {\textrm{EVC}}. \tag{6}$$ In words, the _total $\textrm{MEV}$ activity_ is composed of the extracted $\textrm{MEV}$ ($\textrm{REV}$, divided among searchers and miners), and the global costs of extractable value, going directly to miners and quantified by ${\textrm{EVC}}$. Note that ${\textrm{EVC}}$ only encompasses _on-chain_ activity, ignoring off-chain costs like network bloating due same-nonce transaction replacement. We can compute the ${\textrm{EVC}}$ as follows: $${\textrm{EVC}} = \sum_{tx\in X} s_{tx}.g_{tx},\quad X=\{\textrm{preflights},\textrm{failures}, \textrm{cancellations} \}.\tag{7}$$ While altogether eliminating $\textrm{MEV}$ is likely impossible[^5], it is Flashbots' [core mission](https://ethresear.ch/t/flashbots-frontrunning-the-mev-crisis/8251) to reduce the negative externalities of $\textrm{MEV}$-related activities by improving the overall efficiency of the extraction process. The present framework allows us to state this mission concisely as that of reducing ${\textrm{EVC}}$. ## Flashbots Bundles Flashbots optimizes $\textrm{MEV}$ extraction by allowing searchers to submit bundles of ordered transactions, effectively transferring part of the ordering privileges from the miners to the searchers. These bundles are included by the miners provided they get more out of them than by mining regular transactions. While searchers can still set a gas fee, the preferred way to pay the miners for inclusion is via a direct `coinbase` transfer included in the bundle[^6]. We thus need to account for this extra term in our miner revenue formula (4): $$\textrm{REV}_M^{Flashbots} \gtrsim s_{\textrm{MEV}}.(g_{\textrm{MEV}}-g_{tail}) + V_{direct}, \tag{8}$$ where $V_{direct}$ is the total value transferred to the `coinbase` address. Note that this new term doesn't affect the total $\textrm{REV}$ as it is accounted for by a corresponding increase of the $V_{out}$ term. Apart from the extra term, we now expand the set of transactions that contribute to the terms in the formula to include all transactions included in the bundle. In particular, if a bundle includes the "meat" in an arbitrage, its size and gas price count towards the extracted value. This ensures we account for the opportunity cost incurred by miners when including bundles instead of regular transactions. Finally, expression (2) for searcher value stays the same, but also requires expanding the implied transaction set to all transactions in the bundle. The rest of the model remains unchanged by the utilization of Flashbots' bundles. With these changes, the model also encompasses alternative relay services like private mempools. It is worth noting that Flashbots reducing ${\textrm{EVC}}$ does not imply a decrease in miners' revenue, since their share of extracted value might increase as a result of the extraction optimization. Flashbots executions are deterministic and therefore searchers are likely to pay the miners more than if they risked paying for reverts or cancellations. Finding the revenue sharing equilibrium is ultimately a game-theoretic problem which deserves independent treatment. ## Final Thoughts By unifying various quantities involved in $\textrm{MEV}$ extraction, our framework enables us to pose clear-cut questions like "how big are the costs of $\textrm{MEV}$ extraction activities for the network?", or "to what extent has Flashbots helped in reducing these costs?". These and other interesting perspectives on $\textrm{MEV}$ extraction based on this framework will be included in coming versions of $\textrm{MEV}$-Explore. Throughout this work, we have swept under the rug the complications involved in actually measuring the "atomic terms" entering the definitions, like $V_{out}$, or the actual set of $\textrm{MEV}$-extracting transactions. This task involves _ad hoc_ heuristics for an ever-growing number of $\textrm{MEV}$ extraction strategies, and while we strive for establishing a useful classification, there will always be unforeseen opportunities that will elude detection[^7]. We pass no judgment as of which types of $\textrm{MEV}$ extraction are "good" and which are "bad", although there's certainly ways in which this question could be meaningfully approached ("has an unrelated third party incurred loss due to the extraction?"). We leave this subtle question for future work, but we restate our belief that ${\textrm{EVC}}$ is undesirable and we shall strive to minimize it. ## Join our Efforts! At Flashbots, we perform research and build systems for mitigating the upcoming $\textrm{MEV}$ crisis, and we would love your help. We are a distributed organization with the principles of a [pirate hacker collective](https://www.youtube.com/watch?v=T0fAznO1wA8), and have several [open positions](https://github.com/flashbots/pm/tree/main/jobs). We also issue grants to external researchers doing work aligned with ours, please find out more in our [Research repository](https://github.com/flashbots/mev-research), or join our [Discord](https://discord.gg/7hvTycdNcK)! Special thanks to Scott Bigelow, Phil Daian, Stephane Gosselin, Alex Obadia, Tina Zhen, and Jason Paryani for welcoming me onboard and all Flashbots' crew for the work and discussions leading to this post. [^1]: Note however that most of what is presented here should apply with minor variations to other blockchains that have actors with transaction-ordering privileges. [Work is underway](https://github.com/flashbots/mev-research/blob/main/FRPs/FRP-8.md) to flesh out these variations. [^2]: The definitions here are consistent with a theoretical approach to $\textrm{MEV}$ to be published in an upcoming paper (sneak peek [here](https://github.com/flashbots/pm/issues/16)). [^3]: It's up for discussion whether the (non-measurable) $\textrm{MEV}$ should also depend on this. [^4]: One would need to look into adjacent block gas prices if the entire block was taken up by $\textrm{MEV}$-extracting transactions. [^5]: Note however that it can likely be reduced to some extent with smart protocol design, there's some [ongoing efforts](https://github.com/flashbots/pm/issues/16) to this avail. [^6]: A direct `coinbase` transfer could also be present in a standard, non-bundled extraction, but it would make little sense for the searcher to do it since miners typically only look at gas prices for transaction inclusion and ordering. [^7]: See [this paper](https://arxiv.org/abs/2102.03347) for a complementary, protocol agnostic approach to $\textrm{MEV}$ detection based on flagging certain types of "transaction dynamics" (displacement, insertion, and suppression).

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully