ethereum/pm

Consensus-layer Call 91

djrtwo opened this issue · 5 comments

Consensus-layer Call 91 Agenda

prev: call 90

Meeting Date/Time: Thursday 2022/7/14 at 14:00 UTC
Meeting Duration 1.5 hours
livestream

  1. Merge
  2. mev-boost
  3. Other client updates (if any)
  4. Research, spec, etc
  5. Open Discussion/Closing Remarks

following up from the last call, I've made a PR to specify the behavior for proposers using the external builder network going into the merge: ethereum/builder-specs#38

I'd like to discuss this with client devs

notes for call:
relevance: CL devs will need to implement some kind of logic into their clients to handle a special flow near the transition
why?: reduces the moving parts going into and through the Merge
current proposal: an epoch-based delay dependent on finality of the transition
discussion points: is this proposal straightforward to implement? are there concerns and if so do you have a suggestion on how to implement another way?

note: builders and relays (and by extension relay mux software like mev-boost) will need to respect the same "mev embargo" but I have heard less feedback from these entities and would defer to implementation facility wrt CL devs as priority

I'd like to discuss the single vs. dual client release merge deployment strategy, see: https://notes.ethereum.org/@timbeiko/merge-release-strategy

I'd like to give a quick update of the current Flashbots builder and relay infrastructure.

I'd like to bring up the topic of changing the name of prater to goerli or how we our plan of action for naming the merged testnet. We could potentially ask CL teams to allow for the prater or goerli flag for a duration of time before deprecating the prater flag in a future breaking release.