-
Notifications
You must be signed in to change notification settings - Fork 336
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 168 #845
Comments
(Minor) Perhaps we should prefix all upgrades in mainnet-upgrades with the upgrade number, like 01-homestead, 02-dao-fork and so on? Or add a meta doc describing the order of upgrades. Right now you have to know the sequence of historical upgrades by heart. |
Hello! I would love to present EIP-7212, which proposes a new precompiled contract for the |
I'd like to add an update from the EIP Editors on splitting the repository and governance changes. |
@yperbasis we do have some form of Meta doc here. Let me know if you think that's sufficient or if we should still modify it. @SamWilsn @ulerdogan added your items to the agenda 👍 |
I think this is just meant for the file names in the mentioned folder, and I would say that for this it would still be pretty useful to have easier access to the files there (at the end something minor though, still nice). |
We'd like to bring up testing updates from Devnet-8 and Holesky updates (We tested out 1.4M validators and >1B ether in the network and would like to propose the same for Holesky). |
Got it @holgerd77 - added to the agenda. @parithosh same :-) |
Closed in favor of #850 |
Meeting Info
#allcoredevs
Discord channel shortly before the callAgenda
The text was updated successfully, but these errors were encountered: