post merge updates: mev #7193
Merged
post merge updates: mev #7193
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jmcook1186
requested review from
samajammin,
wackerow,
corwintines,
pettinarip and
minimalsm
as code owners
github-actions
bot
added
content 🖋️
Gatsby Cloud Build Reportpost-merge 🎉 Your build was successful! See the Deploy preview here. Build Details🕐 Build time: 2m |
59 tasks
minimalsm
requested changes
Jul 27, 2022
Co-authored-by: Joshua <[email protected]>
corwintines
reviewed
Aug 14, 2022
corwintines
reviewed
Aug 14, 2022
corwintines
reviewed
Aug 15, 2022
Co-authored-by: Corwin Smith <[email protected]>
|
This seems blocked on review from a subject matter expert. I've asked in the ETH R&D Discord for a review. |
ralexstokes
reviewed
Aug 15, 2022
| Flashbots is an independent project which extends the go-ethereum client with a service that allows searchers to submit MEV transactions to miners without revealing them to the public mempool. This prevents transactions from being frontrun by generalized frontrunners. | ||
|
|
||
| As of this writing, a significant portion of MEV transactions is routed through Flashbots, meaning generalized frontrunners aren't as effective as they used to be. | ||
| Flashbots is an independent project which extends the go-ethereum client with a service that allows searchers to submit MEV transactions to validators without revealing them to the public mempool. This prevents transactions from being frontrun by generalized frontrunners. |
There was a problem hiding this comment.
mev-boost is client-independent
There was a problem hiding this comment.
link to flashbots website or docs?
wackerow
reviewed
Aug 15, 2022
Comment on lines
11
to
13
| ### Miner extractable value | ||
| ### Maximal extractable value {#maximal-extractable-value} | ||
|
|
||
| This concept was first applied in the context of [proof-of-work](/developers/docs/consensus-mechanisms/pow/), and was initially referred to as "miner extractable value". This is because in proof-of-work, miners control transaction inclusion, exclusion, and ordering. However, after the transition to proof-of-stake via [The Merge](/upgrades/merge) validators will be responsible for these roles, and mining will no longer be applicable. The value extraction methods here will still persist after this transition, and thus the term "miner extractable value" is no longer valid. "Maximal extractable value" is now used as a more inclusive replacement. | ||
| Maximal extractable value was first applied in the context of [proof-of-work](/developers/docs/consensus-mechanisms/pow/), and initially referred to as "miner extractable value". This is because in proof-of-work, miners control transaction inclusion, exclusion, and ordering. However, since the transition to proof-of-stake via [The Merge](/upgrades/merge) validators have been responsible for these roles, and mining is no longer part of the Ethereum protocol. The value extraction methods still exist, though, so the term "Maximal extractable value" is now used instead. |
There was a problem hiding this comment.
We used the heading "Miner" extractable value here intentionally to offer an explainer to what happened to that name, partially for SEO purposes, allowing site crawlers to catch this.
The entire doc is called "Maximal Extractable Value" so if we don't want to use "miner extractable value" anymore, we should consider renaming this header or ditching it entirely to avoid duplicating the header name.
There was a problem hiding this comment.
agree with Paul, can we change it back?
Co-authored-by: Paul Wackerow <[email protected]> Co-authored-by: Alex Stokes <[email protected]>
jmcook1186
commented
Aug 30, 2022
Co-authored-by: Joseph Cook <[email protected]>
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
wackerow
approved these changes
Aug 30, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
updates mev page for post-merge
NB @wackerow please give this a thorough read and I'm not 100% confident in the applicability of some of the mev methods to pos Ethereum. I've changed the bits I am pretty sure of.
Related Issue
#7075