-
Notifications
You must be signed in to change notification settings - Fork 202
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
Missed proposal getExecutionPayload: newExecutionPayload invalid
#4094
Comments
Had the exact same issue today of a block proposal failure on mainnet running Nimbus v22.8.2-3a8abd:
At that point Besu v22.7.2 started throwing errors:
I had mev-boost active (main Flashbots relay) but no issue reported in its logs:
Running Ubuntu 22.04.1 LTS AMD64. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I've just missed a proposal on mainnet with the following Nimbus logs:
Geth showed this in its logs at the same time:
Mev-boost didn't show any logs at the time of proposal, but the closest lines were this:
The connection between the EL and CL seems to be fine as I have both
Established connection to execution layer
andObtained terminal block from Engine API
in my logs on startup.To be honest I didn't know mev-boost even did anything yet until the merge!
To Reproduce
Steps to reproduce the behavior:
The text was updated successfully, but these errors were encountered: