-
Notifications
You must be signed in to change notification settings - Fork 333
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
Comments
I would like to seek agreement to merge |
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:
|
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. |
@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. |
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. |
@fjl I'll add it to the Pectra section, thanks! |
Closed in favor of #1124 |
Call summary on Eth Magicians: |
Podcast (audio only) - https://open.spotify.com/episode/297davcrPXeRxIHnO7BdPK |
Please review and Merge ethereum#1104
Meeting Info
#allcoredevs
Discord channel shortly before the callAgenda
engine_getBlobsV1
execution-apis#559The text was updated successfully, but these errors were encountered: