Skip to content
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

Ethereum Core Devs Meeting 140 Agenda #538

Closed
timbeiko opened this issue Jun 2, 2022 · 12 comments
Closed

Ethereum Core Devs Meeting 140 Agenda #538

timbeiko opened this issue Jun 2, 2022 · 12 comments

Comments

@timbeiko
Copy link
Collaborator

timbeiko commented Jun 2, 2022

Meeting Info

Agenda

@timbeiko
Copy link
Collaborator Author

timbeiko commented Jun 6, 2022

@qizhou FYI I've added 5027 to this call's agenda, as discussed on the last one.

@qizhou
Copy link

qizhou commented Jun 6, 2022

@qizhou FYI I've added 5027 to this call's agenda, as discussed on the last one.

Received. Many thanks!

@henridf
Copy link
Contributor

henridf commented Jun 7, 2022

Time permitting I'd like to provide an update on the EIP-4444 related prototyping, to raise awareness and get feedback. I'll post a link to the work before the call.

@tkstanczak
Copy link

Proposing the bomb delay EIP:
https://eips.ethereum.org/EIPS/eip-5133

@MicahZoltu
Copy link

If it isn't fully resolved before Friday, I would like to discuss EL responsiveness to getPayload requests from CL clients. Ideally, @djrtwo or @mkalinin will be able to participate in this discussion. I am of the belief (maybe wrong) that current EL clients are misbehaving, possible in response to CL clients misbehaving.

@tvanepps
Copy link
Collaborator

tvanepps commented Jun 8, 2022

I'd like to mention the KZG-Ceremony breakout call briefly. anyone interested in learning more can follow in the KZG-ceremony in the Eth R&D discord or join the call every two weeks.

#546

@ralexstokes
Copy link
Member

I'd like to quickly discuss this issue with the devs: ethereum/builder-specs#29

it touches the Engine API so is merge-related and can go at the end of that section. I may have to leave the call early Friday in which case someone else can take over (I think @mkalinin has context) or I can pick up at the next CL meeting if we don't get to it in time

@henridf
Copy link
Contributor

henridf commented Jun 9, 2022

Time permitting I'd like to provide an update on the EIP-4444 related prototyping, to raise awareness and get feedback. I'll post a link to the work before the call.

henridf/eip44s-proto#1 for the draft spec (the repo has a tool implementing it)

@timbeiko
Copy link
Collaborator Author

timbeiko commented Jun 9, 2022

Added everything so far to the agenda 😄

@parithosh
Copy link
Member

I'd like to bring up the topic of testnet merging order. We seem to be flipping between merging goerli or sepolia next. I'd like to clarify which testnet would be next and ideally not make any changes to that. I know we said that we would wait a few weeks after Ropsten to merge the next testnet, but that implies we start planning it now - or atleast decide on an order and a potential call for a decision.

@mcdee
Copy link

mcdee commented Jun 10, 2022

RE: testnet merge order. The merge of sepolia is not, in my opinion, going to be any useful sort of dress rehearsal for the wider community due to the permissioned nature of the beacon chain and the near-empty execution chain. As such, I suggest we do it next and save the goerli/prater merge for the point at which everyone believes they are "done" with code changes and allows the wider community to have a dress rehearsal using released packages rather than compiling from source, an expectation that command-line parameters won't change, etc.

@timbeiko
Copy link
Collaborator Author

Closed in favor of #551

@henridf @qizhou I've tentatively moved both your EIPs to the next call for discussion, but can confirm closer to the actual call how likely it is we have time to go over them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants