Chris Hager
Chris Hager
This is incorrect -- slashing would only occur in the case of double-signing, which is not a risk that using the external builder network poses. See also https://www.bloxstaking.com/blog/ethereum-2-0/understanding-eth2-slashing-preventative-measures/ for more...
I think that could make sense. Would love to hear inputs from the other CL clients on this too!
I see a problem with this approach, namely that mev-boost uses it's internal request timeout, waiting for the slowest relay. But it has no notion about the BN timeout for...
Good ideas! Thanks 👍
Implemented the first option in v0.7.2, moving to option 2 in the future
The default timeout used for all requests. But perhaps that's not good enough and we need to define them per request... See also #181
Perhaps this feature could be opt-in (i.e. with a request header), it might be a little risky for less sophisticated builders to accidentally overwrite their better blocks before 🤔 Implementation-wise...
Just a note that this issue is noticed. I'm just having a hard time finding the time to think about it! Will get back to you soon :)
I don't quite recall anymore, there were some errors otherwise. You could try to remove the code and run a few blocks through it to reproduce.