Repository navigation
Execution Layer Meeting 168 #845
Description
Activity
(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.
Reacted by Holger Drewes, Jochem Brouwer and Andrei MaiborodaReacted by Holger Drewes and Jochem BrouwerHello! I would love to present EIP-7212, which proposes a new precompiled contract for the
secp256r1curve. We want to receive feedback or reviews from the community and raise awareness while the EIP is being improved, as it's a Core Track EIP on the EL.Reacted by estmcmxci.eth, Alim Şahin, doganalpaslan, Kristof Gazso, Colton || Coltron, Yoav Weiss, Tahir Özpala and rafiI'd like to add an update from the EIP Editors on splitting the repository and governance changes.
Reacted by xinbenlv and Yoav WeissReacted by g11tech@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 👍
Reacted by Ulaş Erdoğan@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.#843
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 :-)
Meeting Info
#allcoredevsDiscord channel shortly before the callAgenda