William Zhao
    • Create new note
    • Create a note from template
      • 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
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me 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
    • Save as template
    • 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 Create Help
Create Create new note Create a note from template
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
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me 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
    Subscribed
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Subscribe
    # EIP-1559 in Retrospect On August 5, 2021, Ethereum implemented *Ethereum Improvement Proposal 1559* (EIP-1559) on its mainnet as part of the London Hardfork, which modified the transaction fee mechanism on Ethereum from a first price auction to one that involves blocks of varying sizes, separating transaction fees as history-dependent base fees and tips, and burning of the base fees. How does such a mechanism fare in practice? In a recent [work](https://arxiv.org/abs/2201.05574) together with Yuxuan, Luyao, Fan, and Yulin, we analyze this mechanism using rich data from the Ethereum blockchain, mempool, and exchanges. At a high level, we find that EIP-1559 improves the user experience by making fee estimation easier, mitigates the intra-block difference of gas price paid, and reduces users’ waiting times. Moreover, EIP-1559 has only a small effect on gas fee levels and blockchain security. In this post, we will elaborate on these results. ## Transaction Fee Mechanism Public blockchain networks such as Ethereum accept transactions from anyone on the network and add them to the chain. However, processing these transactions and executing the operations requires bandwidth, computation, and memory resources. Moreover, there is a limit to the number of transactions that can be processed. For instance, Ethereum processes about 30 transactions per second. Thus, to efficiently allocate the resources and the space available, blockchains charge a transaction fee through a transaction fee mechanism (TFM). Most blockchains adopt the transaction fee mechanism first proposed by Bitcoin. Simply put, this mechanism is a first-price auction where: * Each user bids a transaction fee associated with the transaction. * The miner chooses which transactions to include in the block. * The miner gets all the transaction fees that users bid in the block. However, first-price auction is known to be inefficient and may require users to either overpay transaction fees or have a long waiting time. In particular, in periods of high demand, transaction fees can be volatile due to which it is difficult for users to make the right bid. If we overbid, we end up overpaying. If we bid low, we may experience a long waiting time. ## What is EIP-1559? EIP-1559 introduces four major changes to the transaction fee mechanism on Ethereum. First, EIP-1559 changes the requirement from fixed-sized blocks to variable-sized blocks. The block gas limit is doubled from 15 million to 30 million, while the block gas target is still set at 15 million. The following figure shows block gas used before and after EIP-1559. <figure> <img align="center" src="https://i.imgur.com/CcyXwzQ.png"> <figcaption align = "center"><b>Figure 1: Each dot represents a block. Before EIP-1559, almost all blocks used 15 million gas; after EIP 1559, block gas used varies between 0-30 million. </b></figcaption> </figure> Second, EIP-1559 introduces a base fee parameter determined by network conditions. Base fee is the minimum gas price that every transaction must pay, to be included in a block. If the block gas used in a block is greater than the target, the base fee for the next block increases, and vice versa. <figure> <img align="center" src="https://i.imgur.com/lJURP52.png"> <figcaption align = "center"><b>Figure 2: Each dot represents a block. There's no base fee before EIP-1559. Afterwards, it with occasional peaks. </b></figcaption> </figure> Third, the way users bid is modified in a backward-compatible manner. In addition to the required base fee, users can optionally bid two parameters in their transactions, max priority fee per gas ("tip") and max fee per gas ("cap"). Priority fees per gas are the tips with which users incentivize miners to prioritize their transactions. Max fees are the fee caps users will pay including both base fees and priority fees. Thus, the gas price can be obtained as $\min(\text{BaseFee + MaxPriorityFee, MaxFee})$. The difference between the max fee and the sum of the base fee and priority fee, if any, will be refunded to the user. Finally, the base fee is burned, while the priority fee is rewarded to the miners. Before EIP-1559, miners earned all the gas fees in a block. With EIP-1559 implemented, tips are de facto mandatory because miners do not earn the base fee and otherwise they may mine empty blocks. ## Our Goal This transaction fee mechanism had been studied by [Roughgarden](https://arxiv.org/pdf/2106.01340.pdf) using a game-theoretic analysis. In fact, he pointed out its incentive compatibility for myopic miners. Our goal in this study was to *empirically* evaluate this mechanism. In particular, we wanted to answer the following three questions: * Does EIP-1559 affect the transaction fee dynamics in terms of overall fee level, users’ bidding strategies, and intra-block distribution of fees? * Does EIP-1559 affect the distribution of transaction waiting time? * Does EIP-1559 affect consensus security, in terms of fork rates, network loads, and Miner Extractable Value (MEV)? ## Our Findings ### Does EIP-1559 affect the transaction fee dynamics? We observe that EIP-1559 did not lower the transaction fee level itself in our data period, but it enabled easier fee estimation for users. High gas fee is a scalability issue, not a mechanism design issue. Before EIP-1559, users paid the entirety of their bids, so they risk overpaying transaction fees if the network condition turns out less congested after they bid. With the new TFM, however, such risks are avoided, because users can set two parameters in their bids: a fee cap and a tip for the miner on top of the base fee. This separation enables a simple yet optimal bidding strategy where users just set the max fee per gas to their intrinsic value for the transaction and set the max priority fee per gas to the marginal cost of miners. We observe that the bids users submit after EIP-1559 are consistent with this obvious optimal bid. While the median gas price paid and median max fee bid are volatile and highly correlated to each other, Figure 3 shows that the max fee bids are usually higher than the gas price paid. Meanwhile, Figure 4 shows that the median max priority bid remains at a low level (almost always < 10 Gwei throughout the period and < 3 Gwei after block number 13.06M). <figure> <img align="center" src="https://i.imgur.com/FDTzpci.png"> <figcaption align = "center"><b>Figure 3: Max fee bids were usually much higher than the actual gas prices paid. Each dot represents a block. </b></figcaption> </figure> <figure> <img align="center" src="https://i.imgur.com/EwuzmrI.png"> <figcaption align = "center"><b>Figure 4: Priority fee bids remained at low level in most cases (< 10 Gwei), especially after block number 13.06M. Each dot represents a block.</b></figcaption> </figure> We also observe that users who adopt EIP-1559 bidding pay a lower fee than those who stick to the legacy bidding, which implies that fee estimation is easier with the new gas fee bidding style. <figure> <img align="center" src="https://i.imgur.com/JWGMQ14.png"> <figcaption align = "center"><b>Figure 5: Distributions of median gas prices of a block for legacy transactions and EIP-1559 transactions. The distribution of EIP-1559 transactions is overall to the left of that of legacy transactions, which means that users who adopt EIP-1559 pay a lower gas price.</b></figcaption> </figure> ### Does EIP-1559 affect the distribution of transaction waiting time? We define waiting time as the difference between the time when we first observe the transaction in mempool and when the transaction is mined. Thus, waiting time determines the latency for committing a transaction, also taking into account the time spent by the transaction in the mempool. We find that waiting time significantly reduces after London Hardfork from ~17 secs to ~10secs, possibly as a result of easier gas price bidding and variable-sized blocks. This benefits both the transactions that adopt the new bid style and the ones that still adopt legacy bidding. Thus, EIP-1559 improved the waiting time for transactions even though not all users have adopted it. <figure> <img align="center" src="https://i.imgur.com/w2VKwbB.png"> <figcaption align = "center"><b>Figure 6: Priority fee bids remained at low level in most cases (< 10 Gwei), especially after block number 13.06M. Each dot represents a block.</b></figcaption> </figure> ### Does EIP-1559 affect consensus security? EIP-1559 changes important consensus parameters such as block size and the incentives of miners and users. To understand its impact on consensus security, we identified three possible avenues through which the EIP might affect consensus: * **Fork rate.** Larger blocks may take more time to propagate through the network, and as described in a previous [post](https://decentralizedthoughts.github.io/2021-10-15-Nakamoto-Consensus/), this may lead to more forks, have the ability to tolerate fewer adversarial parties, and even possibly affect the safety guarantees of the protocol even when there are no adversaries. Our results show that London Hardfork did increase the block size on average, and consequently also led to about 3\% rise in fork rates. Thus, it did negatively impact security, but the extent of the impact is modest. * **Network load.** Another natural question is whether EIP-1559 significantly affects the amount of computation and storage required to participate in the protocol. Vitalik argued that EIP-1559 will not significantly affect the network load in his post from a [year](https://notes.ethereum.org/@vbuterin/eip_1559_spikes) ago. To answer this question, we analyzed the moving averages of block gas used over different time intervals. Our results confirm Vitalik's conclusion that EIP-1559 does not put the blockchain system under a significantly higher load for an extended period. We do observe load spikes -- periods during which an above-average amount of gas is consumed -- but its frequency is not significantly different before or after the London fork. <figure> <img align="center" src="https://i.imgur.com/2y89fJn.png"> <figcaption align = "center"><b>Figure 7: Moving averages of block gas used per second for different time intervals.</b></figcaption> </figure> * **Miner Extractable Value (MEV).** MEV refers to the profit a miner can make through their ability to arbitrarily include, exclude, or re-order transactions within the blocks they produce. We find that MEV from Flashbots becomes a much larger share of miners' revenue after EIP-1559, mainly because the base fees are burnt. This might create an incentive for miners to invest more in MEV extraction. <figure> <img align="center" height=300 src="https://i.imgur.com/G6Bw13v.png"> <figcaption align = "center"><b>Figure 8: Ratio of revenue from Flashbots to non-static revenue.</b></figcaption> </figure> You can find more details on this work including our data sources and methodology at https://arxiv.org/abs/2201.05574. Please add comments on [Twitter](...).

    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