zec
/
zips
mirror of https://github.com/zcash/zips.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Explain choice of three-month network upgrade window

This commit is contained in:
str4d 2018-01-29 01:29:16 +00:00
parent 7118a2a907
commit 4297d652e9
No known key found for this signature in database
GPG Key ID: 665DBCD284F7DAFF
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
drafts/str4d-overwinter-activation/draft1.rst
View File

@ -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
--------------------