Consensus-layer Call 102

[djrtwo]

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

1. Capella
   • devnet updates
   • relayer/builder testing
   • Sepolia fork date
   • Engine API: deprecate exchangeTransitionConfiguration execution-apis#375
2. 4844
   • block/blob decoupling (maybe simulation results)
3. Research, spec, etc
   • Warning about merge of Updated eip4844 references to deneb consensus-specs#3215
4. Open Discussion/Closing Remark
   • CL EIP and editors
   • SSZ Transactions Breakout Room  #721

[mkalinin]

Action item from the #715 call: provide an update on the block/blob decoupling simulation.

[mkalinin]

I'd like to ask whether client developers have capacity to include the following small change into Capella/Shanghai:

• Engine API: deprecate exchangeTransitionConfiguration execution-apis#375

[terencechain]

I'd like to ask whether client developers have capacity to include the following small change into Capella/Shanghai:

* [Engine API: deprecate exchangeTransitionConfiguration execution-apis#375](https://github.com/ethereum/execution-apis/pull/375)

Prysm already has a PR opened back in Sept. As soon as it's merged, Prysm can get that in prysmaticlabs/prysm#11452

[mkalinin]

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 exchangeTransitionConfiguration because it may upgrade CL client first and after that upgrade EL. If this soft deprecation isn't needed we can go hard and remove this method on both sides at the same time.

[terencechain]

Under 1. Capella, can we allocate a few mins to talk about the current progress for relayer and builder testing?

[timbeiko]

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 😄

[paulhauner]

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 capella branch separate to our mainline stable/unstable branches. We're confident to call the capella branch feature-complete and ready for public testnets.

Over the next couple of weeks we will work on performing a holistic review on capella then merging it into our mainlines branches. Our goal is to publish a fully-fledged v3.5.0 release which will be Sepolia Capella ready, before the Sepolia fork. In the worst case, we will publish a special non-mainnet, release-candidate for Sepolia which will enable the Capella fork there.

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.

[hwwhww]

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.

[barnabasbusa]

@paulhauner did you mean late Feb or late March? Any reason you feel like we should be waiting till late March?

[tbenr]

I'd like to ask whether client developers have capacity to include the following small change into Capella/Shanghai:

• Engine API: deprecate exchangeTransitionConfiguration execution-apis#375

Ok for teku to include that.

[benjaminion]

Call notes.

[paulhauner]

@paulhauner did you mean late Feb or late March? Any reason you feel like we should be waiting till late March?

Yep sorry I meant Feb 🤦