diff options
| author | Pieter Wuille <pieter.wuille@gmail.com> | 2016-03-15 16:29:24 +0100 |
|---|---|---|
| committer | Pieter Wuille <pieter.wuille@gmail.com> | 2016-03-15 16:29:24 +0100 |
| commit | bce835d2ce0172bffa2858eaba21a6c6c3723110 (patch) | |
| tree | 4daca47c11805c5f1c47f45eea351ba6f9e48ed2 /bip-0009.mediawiki | |
| parent | 4c4009bfdb94d10d94908a144d768399cf40ea6f (diff) | |
| download | bips-bce835d2ce0172bffa2858eaba21a6c6c3723110.tar.xz | |
Small improvements to BIP0009
Diffstat (limited to 'bip-0009.mediawiki')
| -rw-r--r-- | bip-0009.mediawiki | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/bip-0009.mediawiki b/bip-0009.mediawiki index 83ce7d0..509a8a9 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=== |