Earlier today I presented to All Core Devs our case for 2x shorter slot times in Glamsterdam. We believe shorter slots are a strong option for Ethereum to consider on this timeline, with myriad benefits from better UX to improving one of the main value propositions of Ethereum L1, its confirmation engine. Glamsterdam is a fork expected to ship in 2026. The presentation is linked below, along with a discussion on how this proposal slots in (pun :)) with others, in particular slot restructuring proposals. If the decisions to make are "which restructuring proposal should be selected" and "in what order should we ship shorter slots and restructured slots", I believe it is key to find answers with the lens of shorter slots and transaction latency. Some valuable next steps: - A proper accounting of the work needed on both paths (shortening -> restructuring vs restructuring -> shortening) - An analysis of attestation and aggregation propagation - Finding our preferred points on the throughput/slot time trade-off curve for each of the restructuring proposals. It is an open question whether we could aim for lower than 6 seconds with some of these restructured slots. It sounds from the conversation that it may be the case! If you are interested to contribute, please reach out :)

Recording of the presentation and discussion

Slides

Link to our proposal