General consensus on something like this to target Q4 Fusaka launch
although consider the above post a strawman for now
Wide agreement that we need the following before going to mainnet:
Need extensive testing of:
Non-finality scenarios and other failure cases
Syncing behavior
Network with 1000+ nodes and more realistic P2P conditions
Attendees also favored a conservative BPO rollout strategy
Initial modest increase at launch, with an observation period to gather mainnet data
Then, a second increase early next year aiming for the full theoretical gain PeerDAS can unlock
⠀Glamsterdam EIP Discussion
Focus on selecting single headliner EIP per layer
Key CL headliner candidates:
EIP-7732 (ePBS)
EIP-7782 (6-second slots)
EIP-7805 (FOCIL)
EIP-7919 (Pureth)
EIP-7942 (Available attestation)
Plenty of discussion on the best way to select a single headliner to start to form the Glamsterdam scope
Participants felt it was too early to begin headliner selection today, and after checking with EL representation we decided to coordinate more closely with ACDE which needs more time
Reflecting all of the discussion, we decided to wait for Glamsterdam headliner selection until fusaka-devnet-3 is live and healthy
Client teams still have time to assemble their opinions on headliner, but there seems to be early interest in a headliner that generally follows the “theme” of scaling
We also highlighted the need for better community input as a way to surface to core developers what is best for Ethereum at this time
fusaka-devnet-3 is still some time out, but we did agree that allocating two ACD calls, 1 for headliner discussion and 1 for headliner decision, made sense