From 66b0cf74cedd733c5d86afe420ed888d65ce7b57 Mon Sep 17 00:00:00 2001 From: UdjinM6 Date: Thu, 2 Mar 2023 19:55:44 +0300 Subject: [PATCH] fix: postpone v19 hf start time on testnet (#5231) ## Issue being fixed or feature implemented Block 847000 hf should happen somewhere around March 4th. We need mining nodes to be upgraded to follow that chain and mine correct blocks. However we don't want v19 to be activated shortly after (~300 blocks), we want to give it a little bit of time to let (new) platform quorums form and make sure everything is ok. With this patch we should have ~2 days (instead of half of a day). ## What was done? bumped v19 activation start time to March 6th ## How Has This Been Tested? n/a ## Breaking Changes yes :) ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation **For repository code-owners and collaborators only** - [ ] I have assigned this pull request to a milestone --- src/chainparams.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/chainparams.cpp b/src/chainparams.cpp index c69a21062d..0945f964c4 100644 --- a/src/chainparams.cpp +++ b/src/chainparams.cpp @@ -486,7 +486,7 @@ public: // Deployment of Deployment of Basic BLS, AssetLocks, EHF consensus.vDeployments[Consensus::DEPLOYMENT_V19].bit = 8; - consensus.vDeployments[Consensus::DEPLOYMENT_V19].nStartTime = 1677024000; // Wed, Feb 22, 2023 0:00:00 + consensus.vDeployments[Consensus::DEPLOYMENT_V19].nStartTime = 1678060800; // Tue, March 06, 2023 0:00:00 consensus.vDeployments[Consensus::DEPLOYMENT_V19].nTimeout = 999999999999ULL; consensus.vDeployments[Consensus::DEPLOYMENT_V19].nWindowSize = 100; consensus.vDeployments[Consensus::DEPLOYMENT_V19].nThresholdStart = 80; // 80% of 100