From 1e25eb98f646f546dd1757eabecc016aceb1cbc3 Mon Sep 17 00:00:00 2001
From: Luke Dashjr <luke-jr+git@utopios.org>
Date: Wed, 17 Feb 2021 21:02:51 +0000
Subject: BIP 8: Advise not choosing a bit being used for other things

---
 bip-0008.mediawiki | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'bip-0008.mediawiki')

diff --git a/bip-0008.mediawiki b/bip-0008.mediawiki
index c09a179..ddf0890 100644
--- a/bip-0008.mediawiki
+++ b/bip-0008.mediawiki
@@ -45,7 +45,7 @@ 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:
 
 # '''name''' should be selected such that no two softforks, concurrent or otherwise, ever use the same name. For deployments described in a single BIP, it is recommended to use the name "bipN" where N is the appropriate BIP number.
-# '''bit''' should be selected such that no two concurrent softforks use the same bit.
+# '''bit''' should be selected such that no two concurrent softforks use the same bit. The bit chosen should not overlap with active usage (legitimately or otherwise) for other purposes.
 # '''startheight''' should be set to some block height in the future, approximately 30 days (or 4320 blocks) 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, and ensures a reasonable number of full nodes have upgraded prior to activation. It should be rounded up to the next height which begins a retarget period for simplicity.
 # '''timeoutheight''' should be 1 year, or 52416 blocks (26 retarget intervals) after '''startheight'''.
 # '''lockinontimeout''' should be set to true for any softfork that is expected or found to have political opposition from a non-negligible percent of miners. (It can be set after the initial deployment, but cannot be cleared once set.)
-- 
cgit v1.2.3

