From 4297d652e990a275a0dbb2fd13850e499ce3515f Mon Sep 17 00:00:00 2001 From: str4d Date: Mon, 29 Jan 2018 01:29:16 +0000 Subject: [PATCH] Explain choice of three-month network upgrade window --- drafts/str4d-overwinter-activation/draft1.rst | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/drafts/str4d-overwinter-activation/draft1.rst b/drafts/str4d-overwinter-activation/draft1.rst index e9d66d69..4d7788ce 100644 --- a/drafts/str4d-overwinter-activation/draft1.rst +++ b/drafts/str4d-overwinter-activation/draft1.rst @@ -87,7 +87,13 @@ ACTIVATION_HEIGHT It MUST be greater than the value of ``DEPRECATION_HEIGHT`` in the last software version that will not contain support for the network upgrade. It SHOULD be chosen to be reached approximately three months after - the first software version containing support for the network upgrade is released. + the first software version containing support for the network upgrade is released, for the following reason: + + - As of the time of writing (the 1.0.15 release), the release cycle is six weeks long, and nodes undergo + auto-senescence 16 weeks after release. Thus, if version ``X`` contains support for a network upgrade, + version ``X-1`` will deprecate 10 weeks after the release of version ``X``, which is about 2.3 months. A + three-month window provides ample time for users to upgrade their nodes after auto-senescence, and + re-integrate into the network prior to activation of the network upgrade. Activation mechanism --------------------