-
Notifications
You must be signed in to change notification settings - Fork 221
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
Proposed block and mevboost timed out #5090
Comments
nimbus-eth2/beacon_chain/spec/mev/bellatrix_mev.nim Lines 70 to 72 in 11f5250
defines a getHeader timeout of 1.5 seconds.
nimbus-eth2/beacon_chain/validators/validator_duties.nim Lines 465 to 483 in 11f5250
then uses this 1.5 second time out. This 1.5 second timeout is longer than the official 1 second timeout, but eventually, as https://github.com/ethereum/builder-specs/blob/v0.3.0/specs/bellatrix/validator.md#relation-to-local-block-building notes
According to one client I checked logs of,
shows up in your logs, which is almost two seconds after the slot began. Thus, it appeared to exactly aborted the external builder flow in favor of a local build process according to the builder specs. |
Describe the bug
I've been using nimbus + mevboost for some time and have proposed some blocks with mev normally. However a couple of days ago I noticed that mevboost timed out, fortunately nimbus proposed the block but without mev.
This happened after I had upgraded to nimbus 23.5.1.
v23.5.0 proposed blocks with mev with no isues.
Screenshots
Logs below
Additional context
flashbots/mev-boost#532
The text was updated successfully, but these errors were encountered: