From bce835d2ce0172bffa2858eaba21a6c6c3723110 Mon Sep 17 00:00:00 2001 From: Pieter Wuille Date: Tue, 15 Mar 2016 16:29:24 +0100 Subject: [PATCH] Small improvements to BIP0009 --- bip-0009.mediawiki | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/bip-0009.mediawiki b/bip-0009.mediawiki index 83ce7d00..509a8a94 100644 --- a/bip-0009.mediawiki +++ b/bip-0009.mediawiki @@ -33,11 +33,11 @@ Each soft fork deployment is specified by the following per-chain parameters (fu The following guidelines are suggested for selecting these parameters for a soft fork: # '''bit''' should be selected such that no two concurrent softforks use the same bit. -# '''starttime''' should be set to some date in the future, approximately one month software release date including the soft fork. This allows for some release delays, while preventing triggers as a result of parties running pre-release software. +# '''starttime''' should be set to some date in the future, approximately one month after a software release date including the soft fork. This allows for some release delays, while preventing triggers as a result of parties running pre-release software. # '''timeout''' should be 1 year (31536000 seconds) after starttime. A later deployment using the same bit is possible as long as the starttime is after the previous one's -timeout or activation, though it is recommended to have a pause in between to detect buggy software. +timeout or activation, but it is discouraged until necessary, and even then recommended to have a pause in between to detect buggy software. ===States===