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

Execution Layer Meeting 193 #1104

Closed
timbeiko opened this issue Jul 18, 2024 · 9 comments
Closed

Execution Layer Meeting 193 #1104

timbeiko opened this issue Jul 18, 2024 · 9 comments

Comments

@timbeiko
Copy link
Collaborator

timbeiko commented Jul 18, 2024

Meeting Info

Agenda

@michaelsproul
Copy link

I would like to seek agreement to merge engine_getBlobsV1. My prototype in Reth+Lighthouse is working well, and the spec had some input from CL+EL devs on Discord. Unfortunately I won't be able to make the call due to the timezone, but will try to nominate someone to champion it on my behalf (DM me if interested)

@yperbasis
Copy link
Member

Time permitting, I'd like to discuss Verkle quantum resistance. As @vbuterin highlighted at EthCC, many experts forecast that in 2030s quantum computers will be powerful enough to break non-trivial cryptography. Given that the cryptography in Verkle is not quantum-resistant, a couple of questions arise:

  1. How feasible/practical is this theoretical vulnerability and what would be concrete consequences of a successful attack?
  2. Is it possible to have something similar to Vekle, but quantum-resistant? Shouldn't we upgrade to that directly, given that the danger might become imminent only in a few years?

@weiihann
Copy link

I'd like to introduce and discuss EIP-7736 (Leaf-level State Expiry).

The progress on state expiry has been stagnant in recent years. Previous proposals have been stalled by increasing complexity and require heavy changes on Ethereum's structure (e.g. address space extension). The proposal offers a simpler approach to state expiry in a post-Verkle environment, where only the leaf nodes are removed and leaving the rest of the nodes intact.

@timbeiko
Copy link
Collaborator Author

@michaelsproul added to the agenda! @yperbasis @weiihann I've added both your topics for the later half of the call. I expect we'll have time to go over them, but small chance they'll get bumped two weeks if the Pectra agenda items take up most/all of the call.

@fjl
Copy link

fjl commented Aug 1, 2024

Bit of a last-minute addition to the agenda, but we would like to discuss the encoding of EIP-6110 requests objects in the engine API. Some people in Geth feel the encoding should be changed to SSZ.

@timbeiko
Copy link
Collaborator Author

timbeiko commented Aug 1, 2024

@fjl I'll add it to the Pectra section, thanks!

@timbeiko
Copy link
Collaborator Author

timbeiko commented Aug 1, 2024

Closed in favor of #1124

@abcoathup
Copy link

@poojaranjan
Copy link
Contributor

Podcast (audio only) - https://open.spotify.com/episode/297davcrPXeRxIHnO7BdPK

TeamAvarch added a commit to TeamAvarch/Ethereum-pm that referenced this issue Aug 11, 2024
Please review and Merge ethereum#1104
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

7 participants