From 26e56f7c09a518570bfda68a1896e504833b3f69 Mon Sep 17 00:00:00 2001 From: Josh Stein <46639943+jcstein@users.noreply.github.com> Date: Thu, 24 Oct 2024 09:38:09 -0400 Subject: [PATCH] Update network-upgrade-process.md Temp hotfix for 2 weeks upgrade timeline --- how-to-guides/network-upgrade-process.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/how-to-guides/network-upgrade-process.md b/how-to-guides/network-upgrade-process.md index 73fdeda641d..7eea9f1d270 100644 --- a/how-to-guides/network-upgrade-process.md +++ b/how-to-guides/network-upgrade-process.md @@ -23,7 +23,7 @@ The upgrade process can be broken down into a few steps: 1. A new binary is released with the new features to be tested on testnets. 1. Validators upgrade their nodes to the new binary, on [Arabica devnet](./arabica-devnet.md), [Mocha testnet](./mocha-testnet.md), and finally on Celestia [Mainnet Beta](./mainnet.md). - Upgrades using pre-programmed height (v2) activate at a predetermined block number. - - Upgrades using in-protocol signaling (v3+) activate one week after 5/6 of the voting power has signaled for a particular version + - Upgrades using in-protocol signaling (v3+) activate two weeks after 5/6 of the voting power has signaled for a particular version ### Upcoming upgrade @@ -38,7 +38,7 @@ Key features include: - [CIP-27](https://cips.celestia.org/cip-27.html): Block limits for number of PFBs and non-PFBs - [CIP-28](https://cips.celestia.org/cip-28.html): Transaction size limit -Unlike the Lemongrass upgrade, there will not be a pre-programmed upgrade height. Instead, validators will signal their readiness for v3 through in-protocol signaling, and the upgrade will automatically activate one week after 5/6 of voting power have signaled for a particular version. +Unlike the Lemongrass upgrade, there will not be a pre-programmed upgrade height. Instead, validators will signal their readiness for v3 through in-protocol signaling, and the upgrade will automatically activate two weeks after 5/6 of voting power have signaled for a particular version. :::info Validators should ensure they are running a v3 binary before signaling support for the upgrade.