From 831b5ea4ddd3644ef5df74aa49ed488e3ed89d17 Mon Sep 17 00:00:00 2001 From: Barnabas Busa Date: Thu, 23 Oct 2025 10:01:16 +0200 Subject: [PATCH 1/2] Clarify mainnet upgrade date requirement --- processes/protocol-upgrade.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/processes/protocol-upgrade.md b/processes/protocol-upgrade.md index 75ec68e75..4524360a5 100644 --- a/processes/protocol-upgrade.md +++ b/processes/protocol-upgrade.md @@ -33,7 +33,7 @@ Ethereum has regular protocol upgrades that introduce performance, security and ### Mainnet -- Mainnet should not have an upgrade date set until all testnets have been upgraded. +- Mainnet should not have an upgrade date set until at least one testnet have been upgraded. - The upgrade must have gone through at least two testnets. - Mainnet must not upgrade less than 30 days after the final testnet has been verified to have been successfully upgraded. This is to ensure enough time has been given to test and spot potential issues before going live on mainnet and to allow for downstream projects to plan their upgrades. L2s need time to produce DAO proposals, organize their own upgrades, etc. From 348c2ea91533d54fb3ddfc535111530615106c74 Mon Sep 17 00:00:00 2001 From: Barnabas Busa Date: Thu, 23 Oct 2025 10:09:13 +0200 Subject: [PATCH 2/2] Fix grammatical error in protocol-upgrade.md --- processes/protocol-upgrade.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/processes/protocol-upgrade.md b/processes/protocol-upgrade.md index 4524360a5..213a078c6 100644 --- a/processes/protocol-upgrade.md +++ b/processes/protocol-upgrade.md @@ -33,7 +33,7 @@ Ethereum has regular protocol upgrades that introduce performance, security and ### Mainnet -- Mainnet should not have an upgrade date set until at least one testnet have been upgraded. +- Mainnet should not have an upgrade date set until at least one testnet has been upgraded. - The upgrade must have gone through at least two testnets. - Mainnet must not upgrade less than 30 days after the final testnet has been verified to have been successfully upgraded. This is to ensure enough time has been given to test and spot potential issues before going live on mainnet and to allow for downstream projects to plan their upgrades. L2s need time to produce DAO proposals, organize their own upgrades, etc.