You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to bring up a discussion about proposers shuffling cache and validator duties BN API requests from VC, and other potential things relying on proposer shuffling stability, related comment ethereum/consensus-specs#3371 (comment).
Another topic for discussion is Engine API versioning if we have time. Particularly, if we get back to 1-1 relation between method and data structure versions, how bad that would be for CLs, that are already relying on one method supporting all data structures, do a switch to one data type one method approach? Related comment ethereum/execution-apis#376 (comment)
Consensus-layer Call 110 Agenda
prev: call 109
Meeting Date/Time: Thursday 2023/6/1 at 14:00 UTC
Meeting Duration: 1.5 hours
Livestream
data_gas_used
field toExecutionPayload
consensus-specs#3391excess_data_gas
anddata_gas_used
type fromuint256
touint64
consensus-specs#3392The text was updated successfully, but these errors were encountered: