Understanding MEV Discrepancies in DeFi Protocols #115
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
Signed-off-by: Arthurim <arthurbdauphine@gmail.com>
|
Thank you for submitting this FRP! Our research team is currently away at an onsite, but they will begin reviewing the proposal next week and we will get back to you with feedback and any questions. |
|
Also interested in this |
|
Hi @IlluvatarEru- sorry for the long delay in processing! Our data team noted that mev-inspect-py does have by protocol MEV already. Given that and limited data team availability to assist on new projects, we are not able to accept this proposal for an FRP grant. |
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.
Following discussions on the flashbots forum, I wanted to open a new FRP to quantify the type of MEV extracted on each protocol and understand discrepancies that may arise.