ePBS Breakout room #3
Closed this issue ยท 3 comments
- June 21 (Fri), 2024 , 14:00 UTC ๐ โ
- Duration: 60 minutes
- Zoom link
Agenda
- EIP Status
- Advantages/Disadvantages for builders/proposers to not use the in-protocol auction.
If time permits, I want to discuss the Beacon API complications related to the get_block function. Currently, get_block returns the full block, which includes both consensus and execution parts. However, most CL clients do not store the execution part and rely on an EL client to blind/unblind it upon request. With ePBS, the consensus-only block becomes the first class citizen on the CL side. It would make sense for the Beacon API specification to assume get_block always returns the first-class consensus block. If users need the execution block, they should retrieve it from the execution API endpoint. This would significantly reduce design complexity by avoiding the need for a third block type that would be used only for the Beacon API.
Call notes: https://hackmd.io/@ttsao/epbs-breakout3
Recording: https://youtu.be/J1e5iUvcTDU