-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Set default LocalBlockValueBoost to 10 #13772
Conversation
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.
I support this change. However, we should likely conduct some testing before merging, considering that local boost has been seldom used. For the reviewer's reference, a similar effort can be found at flashbots/mev-boost#635.
Marking this as blocked to get more eyes and discussion |
The same type of proposal was submitted as a PR to Lighthouse, Teku, Nimbus and Lodestar: |
Ohh cmon! when we designed this I was aiming for 20 and was voted down that anything above 0 would be controversial, Frederik proposes and it gets insta-approved, I'm jealous... definitely approve of this |
@potuz Sorry! You were right, and I was wrong, just like 99.9% of the other times. @fredriksvantes Do you think we should give this a mention in the ACD? |
yeah, I think that makes sense
|
Nimbus and Teku merged, cmon ;-) |
I approve the initiative and will approve this PR after the value is applied at the flag level |
Has anyone in this conversation looked at the data or are we just flying blind? A local block value boost of 10% does essentially nothing for censorship resistance. e.g., if we look at the |
How do you then boost an external block? With the current setup you cannot as the variable is a uint64 and it does not accept numbers lower then 0. I recommend to actually change this to what lighthouse does which allows you to prioritise local and also external blocks. |
What type of PR is this?
Feature
What does this PR do? Why is it needed?
In order to help increase censorship resistance, I propose to change the default LocalBlockValueBoost to 10. This means validators will prioritize local block building unless the bid from the external block builder is 10% or higher than what the validator would receive when building locally.
Looking at stats, it can be seen that currently 63.7% of external builders are censoring transactions compared to 8.53% of validators who do local block building, so setting a minimum 10% as default can help increase the overall censorship resistance of the network.
It is still easy for validators to opt out of this by manually setting the flag to 0, but many are likely to use the default which could help with censorship resistance for the network.