-
Notifications
You must be signed in to change notification settings - Fork 325
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consensus-layer Call 108 #771
Comments
I haven't had time to update EIP-4788 and I am not sure I will be able to make tomorrow's call. To summarize the latest status here: it was decided on ACDE to minimize boundary violation from EL and CL which means sending over the slot data along with the block root it corresponds to. I'm leaning towards writing the "last slot touched" to the contract storage so that to update the EL reads a special key to get the last slot The EIP itself is a fairly easy ask from the CL as you just need to pass around the slot and block root when building a block. Meanwhile, it greatly expands the design space for trustless staking pools which I think we can all agree is important. It is a bigger ask on the EL to schedule for the next hard fork along w/ 4844 but I think there is a good chance of inclusion. Coming to strong consensus on this feature for Deneb at the CL would go along way to signal support to the EL that this feature should also be prioritized in Cancun. |
I won't make it to the call either, but wouldn't mind if there was some discussion of this PR against the beacon-APIs to improve MEV relay beacon node diversity: I know @dapplion was interested in this |
There is a early draft of an EIP-6987 for the ethereum/consensus-specs#3175: |
There is an intention to finish the work on ethereum/consensus-specs#3105 and get it merged. I'd like to make a quick announcement in case if there are any objections from client developers. |
One more to quickly review on the call, from the 4844 call earlier this week: ethereum/consensus-specs#3354 |
Consensus-layer Call 108 Agenda
prev: call 107
Meeting Date/Time: Thursday 2023/5/4 at 14:00 UTC
Meeting Duration: 1.5 hours
Livestream
blob_kzg_commitments
size limit to MAX_BLOB_COMMITMENTS_PER_BLOCK (4096) consensus-specs#3338broadcast_validation
to block publishing beacon-APIs#317The text was updated successfully, but these errors were encountered: