Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add detail on MEV after The Merge #7271

Closed
emmanuel-awosika opened this issue Aug 1, 2022 · 7 comments
Closed

Add detail on MEV after The Merge #7271

emmanuel-awosika opened this issue Aug 1, 2022 · 7 comments
Assignees
Labels
feature ✨ This is enhancing something existing or creating something new Status: Stale This issue is stale because it has been open 30 days with no activity.

Comments

@emmanuel-awosika
Copy link
Contributor

emmanuel-awosika commented Aug 1, 2022

Is your feature request related to a problem? Please describe.

The current page on Maximal Extractable Value (MEV) doesn't have a lot of information about MEV after The Merge (except that PoS validators will extract MEV, not miners).

Describe the solution you'd like

Seeing as MEV is predicted to factor heavily in validator incomes (a consequence of reduced ether issuance), I think it'd be great to mention how Ethereum is working on mitigating the impact of MEV on consensus-layer security and decentralization. Specifically, explaining how concepts, like Proposer-Builder Separation, and current solutions (e.g., MEV Boost) will help curb MEV's negative effects after the transition to proof-of-stake.

Describe alternatives you've considered

Putting it as an FAQ on The Merge page (e.g., "How does The Merge affect MEV?") is possible, but I think having an actual explainer would be better.

Additional context

If this sounds good, I can volunteer to start things off by creating an "MEV after The Merge" section on the MEV page.

Want to contribute?

We love contributions from the Ethereum community! Please comment on an issue if you're interested in helping out with a PR.

@emmanuel-awosika emmanuel-awosika added the feature ✨ This is enhancing something existing or creating something new label Aug 1, 2022
@jmcook1186
Copy link
Contributor

Hi Emmanuel

thanks for this - I personally would support this idea - I simply haven't had time to get to it myself among the other merge updates but acknowledge it is definitely a gap and would appreciate you working on it!

Please go ahead and take ownership of this - I'll look forward to reviewing!

@emmanuel-awosika
Copy link
Contributor Author

Hi Emmanuel

thanks for this - I personally would support this idea - I simply haven't had time to get to it myself among the other merge updates but acknowledge it is definitely a gap and would appreciate you working on it!

Please go ahead and take ownership of this - I'll look forward to reviewing!

Thanks for the prompt feedback, @jmcook1186. I'll get started on it as soon as possible.

@samajammin
Copy link
Member

Just noting this open PR: #7193

Not sure if there's info there worth grabbing/taking into account.

@samajammin
Copy link
Member

I agree with this issue overall! I think a FAQ on MEV in relation to the merge makes sense. I'd just suggest let's be wary of writing too much content within the FAQ. Let's answer the question but push visitors to the dedicated MEV page (https://ethereum.org/en/developers/docs/mev/) for most of the MEV content.

@emmanuel-awosika
Copy link
Contributor Author

Just noting this open PR: #7193

Not sure if there's info there worth grabbing/taking into account.

Sure, I'll check it out.

@github-actions
Copy link
Contributor

This issue is stale because it has been open 45 days with no activity.

@github-actions github-actions bot added the Status: Stale This issue is stale because it has been open 30 days with no activity. label Sep 17, 2022
@lukassim
Copy link
Contributor

Closing this issue as it was solved with PR #7333

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature ✨ This is enhancing something existing or creating something new Status: Stale This issue is stale because it has been open 30 days with no activity.
Projects
None yet
Development

No branches or pull requests

4 participants