Ethereum Core Devs Meeting 130 Agenda

[timbeiko]

Meeting Info

• January 21, 2022, 14:00 UTC
• Duration: 90 minutes
• Youtube Stream: https://youtu.be/VffwWtklJvA
• Zoom: To be shared on #allcoredevs Discord server shortly before the call

Agenda

• Kintsugi 🍵 office hours
  • Engine API: extend semantics of executePayload and forkchoiceUpdated methods execution-apis#165
  • Engine API: proposal for authentication execution-apis#162
  • Tooling support for DIFFICULTY to RANDOM change #457
  • Post-merge testnets
• Shanghai Planning #450
  • EIP-2537
  • EIP-2315
  • EIP-4444/4488

[haltman-at]

I'd like to discuss the question of how tooling should handle the change of DIFFICULTY to RANDOM; see issue #457.

[timbeiko]

Added, @haltman-at

[gcolvin]

I put on the agenda already, but so it doesn't get missed:

• EIP-2315: Simple Subroutines for the EVM

is still alive.

[ralexstokes]

@ineffectualproperty and i are looking to steward EIP-2537 into Shanghai.

i'd like to grab some time during the call to discuss where client teams stand wrt status/implementation/blockers of the EIP and how much appetite there is for inclusion into Shanghai.

[haltman-at]

Hi, sorry, but how does one actually join this Discord server where apparently the Zoom link will be given?

[mkalinin]

Hi, sorry, but how does one actually join this Discord server where apparently the Zoom link will be given?

https://discord.gg/Ha8xnfnk

[haltman-at]

Thank you!

[mkalinin]

I'd like to briefly go through this PR ethereum/execution-apis#165, and upcoming updates to the Merge spec.

[holiman]

Last week, we briefly touched upon a slew of 'potentially shanghai eips', one of them EIP-4444, which I know a lot of people are optimistic about and want to push forward, since it's something of a prerequisite for 4488.

However, 4444 says this, about where to get blocks from>

For the purposes of this proposal, we assume clients always start with a configured and valid weak subjectivity checkpoint. The way this is achieved is out-of-scope for this proposal.

And also

We suggest that a specialized “full sync” client is built.

I think it's fine if it's left out of 4444, but in practice, IMO these things needs to be discussed and ironed out and put into production before we go ahead with 4444. And these are two distinct problems: obtaining WSC versus obtaining all blocks. Who put what where, and why (any incentives?), and how is the data discovered and downloaded?

If we have any time over, maybe this could be brought up?

[timbeiko]

Closed in favor of #459