-
Notifications
You must be signed in to change notification settings - Fork 335
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
Ethereum Core Devs Meeting 136 Agenda #508
Comments
This is in EIP-3670's Rationale section and it also includes |
Added to the agenda, @yperbasis @chfast |
Also, time permitting, I'd like to discuss compatibility between EOF and code chunking for Verkle Trees. |
I have updated Based on the analysis, I think it's important to have this supported by all EL clients as it is currently stated in the spec. |
In testnet plans we could discuss how we can mitigate a few risks. Of course, the main risk is bugs, and I believe that the sooner we start forking public testnets longer the time we should observe it. Two additional points:
|
@yperbasis the ideal solution would be to have two "account types", for legacy accounts the code chunking needs to work as described, and for the "EOF accounts" it wouldn't need to have the This could be easily accomplished by having two different values in the That being said, the current verkle chunking spec is compatible with EOF, just not as optimal as it could be. |
It would be nice to disable "undesirable* opcodes, however it will not solve the question of those existing in legacy code. If |
If there is time today, I would like to briefly get some feedback on how important a security fix people think EIP-4396 would be. Being mindful of the desire to pause CFIs for Shanghai, and given that the EIP still requires significant work in comparing its different variants & picking the optimal one, it would be helpful to get a feeling for whether this should realistically target Shanghai. |
Closed in favor of #514 |
Meeting Info
Agenda
lastestValidHash
supportThe text was updated successfully, but these errors were encountered: