From e054af4a5817b604c88f9b93ca51cb427e63263f Mon Sep 17 00:00:00 2001 From: fdov Date: Sat, 6 Nov 2021 11:28:59 +0100 Subject: [PATCH] consensus: adjust bip9 period for p2sh-assets. 10x the default counting periods. Previous period was 2016 blocks or about 1.4 day. Proposed period is 20160 blocks or about 14 days. - The LOCKED_IN period is extended from 1.4 to 14 days, during which non upgraded nodes will be warned of the upcoming fork. - 10 times as expensive to potentially try to force activation with rented hashpower. - Slower activation. Previous minimum activation time from counting starts, about 3 days, with this proposal about 30 days. --- src/chainparams.cpp | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/chainparams.cpp b/src/chainparams.cpp index f89f6c17e0..ed55ba5e44 100644 --- a/src/chainparams.cpp +++ b/src/chainparams.cpp @@ -164,9 +164,9 @@ class CMainParams : public CChainParams { consensus.vDeployments[Consensus::DEPLOYMENT_P2SH_ASSETS].bit = 11; consensus.vDeployments[Consensus::DEPLOYMENT_P2SH_ASSETS].nStartTime = 1682956800; // UTC: Mon Mai 01 2023 18:00:00 consensus.vDeployments[Consensus::DEPLOYMENT_P2SH_ASSETS].nTimeout = 1714579200; // UTC: Wed Mai 01 2024 18:00:00 - consensus.vDeployments[Consensus::DEPLOYMENT_P2SH_ASSETS].nOverrideRuleChangeActivationThreshold = 2016; // 100% required, hardly happens -// consensus.vDeployments[Consensus::DEPLOYMENT_P2SH_ASSETS].nOverrideRuleChangeActivationThreshold = 1411; // Approx 70% of 2016 - consensus.vDeployments[Consensus::DEPLOYMENT_P2SH_ASSETS].nOverrideMinerConfirmationWindow = 2016; + consensus.vDeployments[Consensus::DEPLOYMENT_P2SH_ASSETS].nOverrideRuleChangeActivationThreshold = 20160; // 100% required, hardly happens +// consensus.vDeployments[Consensus::DEPLOYMENT_P2SH_ASSETS].nOverrideRuleChangeActivationThreshold = 16130; // Approx 80% of 20160 + consensus.vDeployments[Consensus::DEPLOYMENT_P2SH_ASSETS].nOverrideMinerConfirmationWindow = 20160; // The best chain should have at least this much work