-
Notifications
You must be signed in to change notification settings - Fork 325
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
Consensus-layer Call 92 #574
Comments
Heads up, we'll have another 4844 breakout exactly 24h after this call: #581 |
I've been chatting w/ the flashbots folks about mitigations to prevent liveness failures around the external builder network post-merge and we are narrowing in on a suggestion to implement a "circuit breaker" in the event that a relay fails to release blocks they are responsible for. I'd like a few minutes to discuss the solution and get feedback from CL teams as this is best implemented as a policy in the beacon node software. edit: here is a WIP proposal for what a MVP of this could look like: https://hackmd.io/@ralexstokes/BJn9N6Thc I'll walk through this on the spec call and posting here in case anyone wants to review ahead of time |
I would like to briefly go over expected EL's behaviour around multiple terminal blocks received via PoW gossip |
I would also like to confirm CLs agree with this PR: ethereum/builder-specs#38 which disables use of the builder network through the merge transition. It reflects our discussion from the last call and I would like a final ACK before merging. |
If there is time I would like to gather opinions of others about this PR: ethereum/builder-specs#41 which aims to standardize a proposer config file format and make it reusable across CL clients and mev-boost. A lot of the discussion happened already in this PR: flashbots/mev-boost#154 |
If there is a time I would like to discuss this PR ethereum/consensus-specs#2955 and general behaviour of a node if it ends up with the fork choice state which doesn't have viable branches in a block tree |
I would like to raise the current incompatibility between LH and Geth with
I don't really mind what happens here, I would just like to see a standard so that users can start making their nodes merge-ready as soon as possible. |
Consensus-layer Call 92 Agenda
prev: call 91
Meeting Date/Time: Thursday 2022/7/28 at 14:00 UTC
Meeting Duration 1.5 hours
livestream
The text was updated successfully, but these errors were encountered: