-
Notifications
You must be signed in to change notification settings - Fork 211
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
Spurious no bid for this getPayload payload found
#636
Comments
this seems to be an issue on mev-boost losing information about the bids. Is it possible that mev-boost restarted after the header call but before the get payload call? |
Thank you @michaelsproul for helping me with my questions, I was going to post one myself. lol The mev-boost didnot restart at that time. @avalonche I post the mev debug logs at that slot below. If you need more, just contact me here.
|
The error log you mentioned is more of a warning, but doesn't impact the request flow (code is here). The reason for the missed slot here was that the bloXroute relay didn't return the payload: Let's take a closer look at the logs for slot 8641569, mostly around block hash 0x655cbb05b29223cabe49fbcb001d0704aad928c73e4f611d9bb9561adcb3036a which is used for getPayload:
|
Thanks @metachris. I'm trying to find out from bloxroute why this payload didn't get revealed in a timely way |
Looking at the logs the best bid was block with block hash
even though mev-boost saw From the logs the error from bloxroute is that the block publishing step failed
while other relays responded with
So seems like the view of the consensus state was different between the relays and the proposer, resulting in the block publishing and validation step to fail. Will need to confirm with bloxroute though. |
I have logs from a Lighthouse user where
mev-boost
logged:this is despite a bid for the same
blockHash
appearing 1.5s earlier:Is this a known issue? What is the expected impact when
mev-boost
isn't aware of the bid? This block ended up being published ~5s after mev-boost attempted to unblind it and I'm trying to establish whether that was the relay's faultThe text was updated successfully, but these errors were encountered: