Skip to content

December Network Upgrade  #356

@timbeiko

Description

@timbeiko

TL;DR: we need to make the following decisions in the next 1-2 ACD calls:

  • Assuming the merge is not ready by December, do we want to plan for more than a difficulty bomb pushback?
    • If potentially yes, what can we do to minimize any delays or impact on the merge work?
    • If not, do we keep the name "Shanghai" for the difficulty bomb pushback upgrade?

Longer post, more context:

With EIP-3554 pushing back the difficulty bomb, we will need to have a network upgrade in December.

In the most optimistic of scenarios, this upgrade could be the merge, but given the amount of open items on the mainnet readiness checklist, we cannot be certain of this.

If we assume we have a non-merge upgrade, we need to decide whether we want to include anything else aside from another difficulty bomb delay (and whether to keep the name "Shanghai" if we only delay the difficulty bomb, or use another "glacier-themed" name :-) ).

If we only delay the difficulty bomb, the upgrade is drastically simpler to test and implement: it is a single constant change, and will not require to be deployed on testnets prior to mainnet. This means that we could choose the appropriate delay in October, release clients in November, and upgrade in December.

Alternatively, if we decide to include any "feature EIP", then testing and testnet deployements will be needed. Working backwards, and following the London schedule, it means we would need to follow this timeline:

  • Early December: mainnet upgrade
  • Early November: mainnet releases
  • October: testnet upgrades
  • Late Sept/Early Oct: testnet releases
  • Late Aug/September: devnets
  • Early August: EIPs chosen

This timeline would be slightly shorter than London. It is also worth noting that working on a network upgrade would likely delay some of the progress on the merge given that client teams will need to split their focus. For reference, the EIPs that have been loosely discussed for Shanghai so far are: EIP-2537, EIP-3540, EIP-2935, EIP-3074 and EIP-3651.

Given that the next ACD calls are on July 23 and August 6, unless we have a list of EIPs chosen on the August 6th call, then we will default to not including any non-difficulty-bomb EIPs in the December upgrade.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions