Consensus-layer Call 99

[djrtwo]

Consensus-layer Call 99 Agenda

prev: call 98

Meeting Date/Time: Thursday 2022/12/1 at 14:00 UTC
Meeting Duration: 1.5 hours
livestream

1. Capella
   • testnets / progress updates
   • bound withdrawals sweep bound the maximum number of validators considered for withdrawals per sweep consensus-specs#3095
2. 4844
   • any updates worth percolating up to the larger call
   • KZG ceremony update
3. Research, spec, etc
   • (networking) attnets revamp Consensus-layer Call 99 #667 (comment)
   • (networking) ipv6 dual-stack support Consensus-layer Call 99 #667 (comment)
   • (Beacon API) checkpoint sync api status Checkpoint Sync API beacon-APIs#226 (comment)
   • (Beacon API) Attestation and sync committee aggregation selection Attestation and Sync Committee aggregation selection beacon-APIs#224
   • (engine api) engine api spec improvement proposal Consensus-layer Call 99 #667 (comment)
4. Open Discussion/Closing Remarks

[AgeManning]

If there's time, can we discuss potentially releasing some backwards compatible changes:

• Reduction in nodes per long-lived subnet: Proposed attnets revamp consensus-specs#2749
  This can be released entirely in a backwards compatible way, but the net result will be less nodes on long-lived subnets. There is a constant (SUBNETS_PER_NODE) that we can set to minimize the impact on the transition.
• Ipv6 dual-stack support. We've been working towards enabling this throughout all our protocols. First step is enabling ipv6 on our bootnodes which gives an entry-point for ipv6 compatible nodes to connect and advertise ipv6 support. This is also backwards compatible.

Not to be released, but discuss some ideas/work towards automatic NAT hole punching, which may also help finding extra nodes on long-lived subnets.

[mkalinin]

As a follow up to my recent comment ethereum/beacon-APIs#226 (comment), I would like to give an overview on Checkpoint Sync API status.

[OisinKyne]

Hi all,

I'd like a few minutes to introduce this proposal ethereum/beacon-APIs#224 to the teams if possible :)

[mkalinin]

I would like to go over Engine API spec improvement proposal, discussion points:

• engine_getCaps vs optimistic try and fallback on error, more context Engine API spec improvement proposal execution-apis#321 (comment)
  • main question: will CL client devs utilise engine_getCaps or everyone is fine with try and fallback approach
• functional vs by-fork decomposition, examples:
  • Engine API: break down the spec by fork scopes execution-apis#327
  • Engine API: apply functional breakdown execution-apis#330

[ralexstokes]

I'd like to revisit this PR: ethereum/consensus-specs#3095

that adds a bound to the sweep over the validator set per block

This is the last open question on the spec so I'd like to reach agreement on merging or not; if you want to track general progress, you can check out this document: https://notes.ethereum.org/LqHDfmQdS96KWgs3UzGeyA

[tvanepps]

I'd like to mention the KZG Ceremony briefly just to build awareness as we wrap up the second audit and move towards the public contribution period!

[benjaminion]

Call notes.

[hanabi62513]

大体地震はイーサリアム何か買ってないし貰ってもない変なメールをしてくるな購読を解除しろやり方が分からない英語だから日本人馬鹿にするなよ 2023年2月26日(日) 21:53 Heheehd ***@***.***>:

…

Consensus-layer Call 99 Agenda prev: call 98 <#660> Meeting Date/Time: Thursday 2022/12/1 at 14:00 UTC <https://savvytime.com/converter/utc-to-germany-berlin-united-kingdom-london-ny-new-york-city-ca-san-francisco-china-shanghai-japan-tokyo-australia-sydney/dec-1-2022/2pm> Meeting Duration: 1.5 hours livestream <https://youtu.be/KFc1sWYlVZ4> 1. Capella - testnets / progress updates - bound withdrawals sweep ethereum/consensus-specs#3095 <ethereum/consensus-specs#3095> 2. 4844 - any updates worth percolating up to the larger call - KZG ceremony update 3. Research, spec, etc - (networking) attnets revamp #667 (comment) <#667 (comment)> - (networking) ipv6 dual-stack support #667 (comment) <#667 (comment)> - (Beacon API) checkpoint sync api status ethereum/beacon-APIs#226 (comment) <ethereum/beacon-APIs#226 (comment)> - (Beacon API) Attestation and sync committee aggregation selection ethereum/beacon-APIs#224 <ethereum/beacon-APIs#224> - (engine api) engine api spec improvement proposal #667 (comment) <#667 (comment)> 4. Open Discussion/Closing Remarks — Reply to this email directly, view it on GitHub <#667 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASZPFZBCOQFHJIY5SXMZ2Q3WZNG33ANCNFSM6AAAAAASDO45VM> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>