Ethereum Core Devs Meeting 132 Agenda

[timbeiko]

Meeting Info

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

Agenda

• Goerli Issues
• Merge Updates
  • Kiln 🔥🧱 Updates
    • v2
      • Authentication for engine api execution-apis#167
      • Engine API: add engine_exchangeTransitionConfigurationV1 execution-apis#172
  • EIP-4399 in Review & RANDOM vs. DIFFICULTY
  • Kurtosis overview
• Shanghai Planning #450
  • EIP-4788: Beacon state root in EVM EIPs#4788
  • Beacon Chain Withdrawal EIP update
• EIP-4803: Limit transaction gas to a maximum of 2^63-1

[ralexstokes]

I'd like to discuss EIP-4788: ethereum/EIPs#4788

There are a few design decisions to walk through and it would be great to get a temperature sense of what client implementers think is reasonable to move forward on exposing the beacon root to the EVM.

[galenmarchetti]

I'd love to briefly present the work we've been doing with Kurtosis among all the client teams to help test the merge with local and CI-ready multi-client testnets. I'd also love to invite folks to join an information session in a couple weeks (will discuss details in meeting).

Brief info:
Docs on Kurtosis + The Merge
General Kurtosis docs

[axic]

If time allows, it may be useful to discuss retroactively enabling this clarifiaction/strenghething: EIP-4803: Limit transaction gas to a maximum of 2^63-1.

This is a follow up of ACD#120 where it was agreed to follow EIP-2681 and split more of EIP-1985 content into individual EIPs.

[SleepyScallop]

Your just gonna delete questions i ask about the merger date? okay bud, nice PR

[mkalinin]

Before moving EIP-4399 to Review I'd like to raise the question of re-considering the RANDOM name for the opcode. Details are in this post https://ethereum-magicians.org/t/eip-4399-supplant-difficulty-opcode-with-random/7368/16

[timbeiko]

@Sleepyflea yes, sorry, the agenda threads for these calls really isn't the place for this. We share updates in, several, places. It doesn't help the merge move any quicker to add comments on the agenda asking for a date.

[SleepyScallop]

@Sleepyflea yes, sorry, the agenda threads for these calls really isn't the place for this. We share updates in, several, places. It doesn't help the merge move any quicker to add comments on the agenda asking for a date.

Not asking the merge to move any quicker, Im asking for transparency on a company who keeps pushing back quarters further and further. And now all the sudden you think Q2 is gonna be it? Why so sure? Why not Q3, or heck Q4.

Terrible PR, like my friend said your turning half the community against you by withholding information and consistently lying about the release date of POS. Every time you push back the date, your community loses more faith in the general aspect of this project. There is a huge rumor going around that your going centralized for the shareholders. I personally know 50 people myself that will be dropping this project and i am just one person.

And why cant the merge date be discussed on meeting agendas? Im coming to a more truthful conclusion that the community has no say in this project and its based on what shareholders want.

[timbeiko]

And why cant the merge date be discussed on meeting agendas?

Because it's a pointless exercise at this stage of the process. We have rough ideas, which we've communicated, but the amount of work and uncertainty around things means that even if we chose a date today, we'd be likely to change it again and, as you said, disappoint the community. The best we can do, I think, is make it clear what we've done so far + what needs to be done.

[djrtwo]

Quick verbal update on the withdrawal EIP in addition to the beacon state read eip

[timbeiko]

Closed in favor of #481