-
Notifications
You must be signed in to change notification settings - Fork 201
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
Calculate megabundle as soon as it's received #112
Conversation
f4e9cec
to
25e9d32
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there no risk that this change removes the liveness requirements of the block builder? If better megabundles keep coming than a new block will never get built?
If you notice here https://github.com/flashbots/mev-geth/pull/112/files#diff-689874b30f6f905ce6c47cdefeddcf052b467a7936a981f4b6cf38939e10d924R457 that the megabundle interrupt is submitted with "interrupt none", it will not stop the previous task (whatever it may be). So if we are getting more requests than we can handle, we still produce blocks as fast as we can, and the (non-) interrupts are queued. If a different interrupt is submitted (head/recommit) the higher interrupt is propagated to the task. |
Since megabundles are only sent if they improve the profit over previous megabundle, they should be considered for mining immediately.