zq
    • 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

      This note has no invitees

    • Publish Note

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

      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.

      Your account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

      Your team account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

      Explore these features while you wait
      Complete general settings
      Bookmark and like published notes
      Write a few more notes
      Complete general settings
      Write a few more notes
      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
    • Note Insights New
    • Engagement control
    • Make a copy
    • 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 Note Insights Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Make a copy 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

    This note has no invitees

  • Publish Note

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

    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.

    Your account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

    Your team account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

    Explore these features while you wait
    Complete general settings
    Bookmark and like published notes
    Write a few more notes
    Complete general settings
    Write a few more notes
    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
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    --- title: Post-Merge MEV tags: MEV, Talk, Hashkey description: View the slide with "Slide Mode". --- # Post-Merge MEV Zeqing Guo, Hashkey Capital --- ## Contents - 什么是 MEV - PoW 时代的 MEV - PoS 时代的 MEV - 以太坊 roadmap 的原则 - Validator 的问题 - Builder 的问题 --- ## 什么是 MEV - MEV:miner extractable value(矿工可提取价值) - 产生原因:矿工可以决定区块内的排序,而排序本身是有价值的 --- ![](https://i.imgur.com/RVpbJMM.png) NFT User:明明是我先的 科学家:抱歉,贿赂矿工就是能为所欲为 --- ## PoW 时代的 MEV ![](https://i.imgur.com/MtnHSyz.png) --- ## 为什么要引入 flashbots? > My goal: insulate the Ethereum base layer from centralizing tendencies of complicated stuff happening on top of / around Ethereum. > > Vitalik Buterin, mev.day --- ## 为什么要引入 flashbots? - MEV 需要和共识协议分离,否则会危害去中心化 - 不分离的问题 - 举个例子:矿池 A 有自己的科学家,矿池 B 也有自己的科学家 - A 与 B 竞争链上 MEV,可能会出现 A、B 拒绝打包对方交易的情况 - 除此之外,长期来看,越大的矿池 MEV 越多,挖矿奖励越高,算力会向其集中,最终导致算力超 50%,有能力分叉或者双花以太坊 --- ## 信任链 - *科学家* 要信任 *flashbots* 不会偷跑自己的交易 - *Flashbots* 要信任 *矿池* 不会偷跑自己的交易 --- ## 博弈 - 科学家与 flashbots 是 *一对一* 的关系 - 如果 flashbots 偷跑交易,科学家立刻就能发现并将其换掉 - Flashbots 与 矿池 是 *一对多* 的关系 - 但是矿池 *数量不多* - 如果某个矿池偷跑,flashbots 很容易发现并终止合作 --- ## PoS 时代的 MEV 让我们思考一下保持之前的 MEV 模式会有什么问题? --- ## PoS 时代的 MEV - 信任链——不会改变 - 博弈——改变了 --- ## PoS 时代的 MEV - 科学家与 flashbots 是 *一对一* 的关系 - 如果 flashbots 偷跑交易,科学家立刻就能发现并将其换掉 :heavy_check_mark: - Flashbots 与 矿池 是 *一对多* 的关系 - ~~但是矿池 *数量不多*~~ :negative_squared_cross_mark: - ~~如果某个矿池偷跑,flashbots 很容易发现并终止合作~~ --- ## PoS 时代的 MEV - Flashbots 与 矿池 是 *一对多* 的关系 - Validator 数量很多,以几十万记 - Validators 数量激增且匿名,flashbots 如何信任新加坡某个公寓里的小 validator 不会为了 MEV 去偷跑交易? - Flashbots 的最优策略是只递交 MEV 给大 validators,比如 Lido、coinbase - 小 validator 每个区块收益低于大 validator,加剧 staking 向大 validator 集中 - 危害去中心化 --- ## 怎么办? 让我们回顾一下以太坊 roadmap 里最重要的两个原则 --- > My goal: insulate the Ethereum base layer from centralizing tendencies of complicated stuff happening on top of / around Ethereum. > > Vitalik Buterin, mev.day --- > Block production is centralized, block validation is trustless and highly decentralized, and censorship is still prevented. > > Vitalik Buterin, Endgame --- ## 怎么办? ![](https://i.imgur.com/m5ejDAU.png) - Validator 在签名前不知道交易的具体内容,因此无法偷跑交易内的 MEV - 以太坊基金会将这个方案成为 PBS: Proposer(validator)/builder(flashbots) separation --- ![](https://i.imgur.com/DUTKPt8.png) --- ## Validator 的问题 - Builder 给自己错误的交易怎么办? - 因为签名交易时只知道交易的 hash - 比如 builder 出现网络延迟,给了一个已经上链的交易 - Validator 再根据这笔交易出的块将不被网络承认 --- ## Validator 的问题 - 当前方案 - 声誉系统+熔断:如果 builder 在 32 个区块内提交了 5 次错误的交易将被 validator 拉黑 - 最近市场上也出现了做 builder 的 reputation 的项目 --- ## Builder 的问题 - RPC(flashbots/bloXroute) 会不会垄断 builder 市场? - 流量入口会不会垄断 builder 市场 --- ## RPC 垄断 builder 市场? - 很难 - Flashbots 为了避免中心化已经将其开源 - 任何节点服务都可以运行自己的 flashbots - 每个 flashbots 提供的服务高度同质化 --- ## 流量入口垄断 builder 市场? - 很有可能 - Metamask/opensea/uniswap 自建 builder 服务,向 validator 发送 MEV 交易 - 他们有动机做这类事 - 保护用户免受 MEV 攻击,比如 sushi 和 manifold 的合作 - BTW, manifold 很可能在 PoS 时代成为大型 RPC 服务商 - 可以获得额外利润 --- ## 流量入口垄断 builder 市场? - 考虑极端情况:通过 metamask 发送的交易全部不公开广播,只走自己的私有 builder 服务 - Metamask 占有市场 70% 的交易量 - 它的 builder 将直接占据全网出块量的 70% - 虽然不会危害协议安全(它无法双花以太坊协议,也无法分叉以太坊网络) - 但是也会获得空前影响力与利润,并被社区骂 - 中心化出块,去中心化验证 - 中心化成分从共识层分离 --- ## PoS 的未来 - 流量入口(例如钱包、超级 DApp)将会取代矿池获得大量利润与影响力 - Builder 的去中心化提上日程 --- 附送 V 神 9 月 1 日在 Stanford MEV workshop 提出的几个 builder 去中心化 ideas: - 如何保证 builder 不作恶(builder 无法攻击以太坊本身,所以考虑的是 builder 欺负科学家) - 硬件加密科学家的交易 - zk 与加密算法加密科学家的交易 - Danksharding 将 MEV 下放到 L2,让 L1 只做 DA 层,builder 不再这么重要 - 让 MEV 更进一步远离以太坊主网协议本身 - 去中心化 builder - 用 tendermint 做一个 builder 网络(cosmos 被 V 神钦定) --- 按照惯例,接下来会有很多项目尝试实现这些想法,并被 V 神推特点赞 --- ### Thank you! Q & A

    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
    Sign in via Google Sign in via Facebook Sign in via X(Twitter) Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    By signing in, you agree to our terms of service.

    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