Skip to content

MEV Roast 9 Agenda #2

@CarboClanC

Description

@CarboClanC

MEV Ship Treasure Map Roast VIIII
Date: Wednesday, Dec 16
Time: 1:30pm EST / 10:30am PST / 6:30pm UTC

Flashbots Calendar | Slides

  1. Flashbots Flash News Updates (20min)
    MEV Ship stewards will make a succinct presentation on the progress.
  • Research update:
    • Evolution of MEV: from Miner Extractable Value to Maximum Extratable Value
    • Flashbots Research Proposals (FRPs) submitted
  • Engineering update:
    • Special Purpose Vessel: MEV-Search
  • Organization update: The Flashbots Rulebook (WIP)
  1. MEV Ship Community Presentation (15min)
    Each Roast we will invite MEV Ship research collective members to present MEV-related projects they are working on or interesting early stage proposals for community feedback.
  • Title: Protocol Rights Token
  • Presenters: Dan Elitzer & Austin Williams
  • Description: Present for feedback an early design of a mechanism that uses NFTs assigned via Harberger taxes as a solution to certain classes of MEV issues. The mechanism may also have applications beyond MEV.
  1. MEV Roast (50 min)
    Each Roast we will invite an ecosystem stakeholder on-board to the Roast to provide constructive criticism on Flashbots' work.
  • Roast Master of the week: Dan Elitzer
  • Roast Questions:
    1. How much burden of minimizing MEV should be placed at the network level vs the contract/application level?
    2. In the near-to-mid term, should all high-volume front-end applications start routing directly to mining pools the way 1inch is doing?
    3. What would be the impact of infrastructure of traditional financial markets starting to make its way into crypto, such as Payment for Order Flow to wallets or interfaces? (h/t Trent Elmore)
    4. What is the likelihood of advances in cryptographic techniques enabling a meaningful reduction in MEV, vs addressing MEV primarily through game theory and economic mechanism design?
    5. Does the practice of node and mining pool operators actively sorting/filtering transactions based on their outcomes make it harder to fight back against the STABLE ACT or other future legislation that looks to hold nodes and validators accountable for certain types of transactions? (h/t Alex Lindgren)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions