From 6ea5857b62d37724b1ea6947e0dc847afbc1b644 Mon Sep 17 00:00:00 2001
From: Luke Dashjr <luke-jr+git@utopios.org>
Date: Wed, 17 Feb 2021 20:58:33 +0000
Subject: BIP 8: Reduce threshold recommendation to 90%

---
 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 2b8f39e..5c6c783 100644
--- a/bip-0008.mediawiki
+++ b/bip-0008.mediawiki
@@ -49,7 +49,7 @@ The following guidelines are suggested for selecting these parameters for a soft
 # '''bit''' should be selected such that no two concurrent softforks use the same bit.
 # '''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'''.
-# '''threshold''' should be 1916 blocks (95% of 2016), or 1512 (75%) for testnet.
+# '''threshold''' should be 1815 blocks (90% of 2016), or 1512 (75%) for testnet.
 # '''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.)
 
 A later deployment using the same bit is possible as long as the startheight is after the previous one's
-- 
cgit v1.2.3

