1
0
Fork 0
mirror of https://github.com/bitcoin/bips.git synced 2025-03-15 11:59:18 +01:00

Recommend a fallow pause explicitly

This commit is contained in:
Pieter Wuille 2016-03-02 19:48:34 +01:00
parent 63d626668c
commit cd6dfb9411

View file

@ -30,9 +30,10 @@ Each soft fork deployment is specified by the following per-chain parameters (fu
The starttime should be set to some date in the future, coordinates with software release date. This is to prevent The starttime should be set to some date in the future, coordinates with software release date. This is to prevent
triggers as a result of parties running pre-release software. The timeout should be set a reasonable time after the triggers as a result of parties running pre-release software. The timeout should be set a reasonable time after the
starttime. A later deployment using the same bit is possible as long as its starttime is after the previous one's starttime. A later deployment using the same bit is possible as long as the first one its starttime is after the previous one's
timeout. This means that by setting it to 3 years after the starttime would allow around 9 deployments to be initiated timeout or activation, though it is recommended to have a pause in between to detect buggy software.
every year.
Setting the timeout to 3 years after the starttime allows at least 9 new deployments per year.
====States==== ====States====