-
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
Proposal to specify Shanghai for October (3 months after London) #267
Comments
IMO, 3 months is too short of a window after London. As soon as London ships we need to immediately get another hard fork ready. I think January 2021 (~6 months after London) would be a better choice. |
My hunch here is we should get a feel for what the big "feature" or "theme" of Shanghai would be before committing to a timeline. I think the amount of client work will end up dictating what a possible timeline is. We should perhaps set a maximum delay (using the difficulty bomb?) though. I suspect 6 months is probably the most we want to wait, but am open to others' opinion on this :-) |
Noting one thing here: there have been many conversations about accelerating the Eth2 merge (i.e. @vbuterin's recent doc). We should consider whether we want Shanghai to be focused on the merge, rather than having another "feature fork". |
@timbeiko yeah, that's seems to be the right timing to me setting the merge as more or less the single focus for Shanghai, we definitely need some dedicated attention for this. |
Issue related to this: #278 |
@timbeiko Whether it comes before or after the merge, I think a clear candidate for a future "feature" fork is to pull together our outstanding EVM proposals into a coherent whole. I've re-opened an EVM group on the Magician's as a place to start on these and others.
|
Closing this because we agreed on ACD111 to start working on Shanghai as soon as London is done. We can open issues related to specific EIPs to be included in Shanghai 2-3 calls from now. |
This will open space for discussion on EIPs inclusion that will not delay the schedule of the much awaited London release.
The text was updated successfully, but these errors were encountered: