-
Notifications
You must be signed in to change notification settings - Fork 356
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 205 #1271
Comments
I'd like to discuss EIP-7666: EVMify the Identity Precompile, which is proposed for Fusaka. Specifically the mechanism of deploying a contract as a particular address as part of the fork transition. The EOF team would like to use a similar mechanism for the TXCREATE mechanism that was part of the original EOF draft for Pectra. This could make it possible to retire Nick's method for deploying un-owned contracts at fixed addresses, especially cross-chain. |
I'd like to add ethereum/EIPs#9290 to the agenda, because I think it's important to shed a light on how EELS and EEST fit into the EIP process. |
I would like to discuss:
For Max blobs flag, barring input from L2s (rollcall is the day before) -- I would like to make a call for finalization For hardware and bandwidth requirements -- same as above, if max blobs flag is okay. Still pending input from Nixo and Oisin re what percentage of annual rewards/capital investment should be used for determining the amount an attester should pay for hardware |
I'd like to share the EOF devnet roadmap: https://notes.ethereum.org/oi698hfNTSG_oe9xHIgSaA And as part of the roadmap add 4 EIPs to the "Proposed for Inclusion" list for Osaka: ethereum/EIPs#9352 |
@shemnon I added your topics, but think we should go from highest to lowest level, so re-ordered them. @marioevz @kevaundray, I added your items to the agenda. |
Meeting Info
#allcoredevs
Discord channel shortly before the callAgenda
The text was updated successfully, but these errors were encountered: