-
Notifications
You must be signed in to change notification settings - Fork 325
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 194 #1124
Comments
I'd like to spend like 5 minutes pitching EIP-7732. It's part of the formal process depicted in EIP-1 and ACDE is the right place and time for it: most CL devs and researchers are already aware and have opinions on it, EL devs weren't mostly approached as the EIP is purely a consensus change, but it has strong implications on how and when the execution payload is validated. The timing is right because the spec is in a somewhat stable form and implementation is picking up pace at the moment, it's a good time to raise awareness and catch fatal flaws before they take back months of implementation |
I would like to pitch ethereum/execution-apis#570. It allows clients to remove |
I would like to discuss eth/69: Dropping pre-merge fields from the network messages: https://eips.ethereum.org/EIPS/eip-7642 It's a small EIP that will greatly reduce the bandwith required during sync (~530 GB) |
We also recently figured out (thanks to @jwasinger) that our library for bls12-381 (gnark) uses all available cores during the bls multiexponentiations. Thus the benchmarks we did for gas costs are skewed. I get 18-30MGas for G1 compared to 27-60MGas: Seems like we might need to reprice the G1 Multiexp for Pectra. It would be nice if other clients could also run some bls benchmarks to see where their current costs are at |
I'd like to discuss rebasing PeerDAS on Pectra. This has implications with regard to testing the EL-centric EIPs 7702 and EOF. |
Just read through the EIP, support from EthereumJS!
That's a great find! 🤩 Maybe we should make it a standard procedure to always have such benchmark calculations done by two different client implementations/teams min for future EIPs to minimize the risk of such side effects remain undiscovered? 🤔 |
Quick reminder, we going to have weekly Pectra Interop testing call starting from next week Monday starting at 14:00 UTC. |
Recording - https://www.youtube.com/watch?v=tbxgYq8KmmM |
Podcast (audio only) - https://open.spotify.com/episode/4QUOJ7u9KuwSRbJJyrWPHZ?si=QafZbaXBQbCwJ3HcaCxqkg |
Closed in favor of #1142 |
Meeting Info
#allcoredevs
Discord channel shortly before the callAgenda
totalDifficulty
fromBlock
schema execution-apis#570The text was updated successfully, but these errors were encountered: