-
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 102 #711
Comments
Action item from the #715 call: provide an update on the block/blob decoupling simulation. |
I'd like to ask whether client developers have capacity to include the following small change into Capella/Shanghai: |
Prysm already has a PR opened back in Sept. As soon as it's merged, Prysm can get that in prysmaticlabs/prysm#11452 |
I should have provided more detail on the deprecation path. The proposed change says that CL must not surface an error if the method call fails, but it also implies that CL must make this call. This is done to avoid user to see any warnings in their log related to |
Under |
On today's EIPIP call, we continued the discussion about making the EIP process more accommodating for CL folks. One solution we came to is to allow a couple CL folks to join as EIP Editors, with the ability to force-merge CL EIPs. This would hopefully reduce the friction of using EIPs, and allow more CL people to become familiar with the process. If we have time, I can give a 2-3 min recap of the conversation and make a call for CL editors 😄 |
Regarding the date for the Capella fork on Sepolia, Lighthouse is happy to go ahead with a fork date of late March. I've heard March 27th being suggested, I support that date or anything similar. Lighthouse is currently maintaining a Over the next couple of weeks we will work on performing a holistic review on The bottom line is that our implementation is ready to go and we're just working on the finer details of getting it into a release which does not block testnets. |
I want to warn the CL spec contributors that we are going to merge ethereum/consensus-specs#3215 soon and it will cause new conflicts to the open EIP-4844 PRs. |
@paulhauner did you mean late Feb or late March? Any reason you feel like we should be waiting till late March? |
Ok for teku to include that. |
Yep sorry I meant Feb 🤦 |
Consensus-layer Call 102 Agenda
prev: call 101
Meeting Date/Time: Thursday 2023/2/9 at 14:00 UTC
Meeting Duration: 1.5 hours
livestream
The text was updated successfully, but these errors were encountered: