From 8e94e9154e41e3919a6b5b9439747315581ef41e Mon Sep 17 00:00:00 2001 From: Oliver Gugger Date: Tue, 11 May 2021 14:22:09 +0200 Subject: [PATCH] chaincfg: fix deployment bit numbers On signet all previous soft forks and also taproot are always activated, meaning the version is always 0x20000000 for all blocks. To make sure they activate properly in `btcd` we therefore need to use the correct bit to mask the version. This means that on any custom signet there would need to be 2016 blocks mined before SegWit or Taproot can be used. --- chaincfg/params.go | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/chaincfg/params.go b/chaincfg/params.go index cb156863..a6d8d3e5 100644 --- a/chaincfg/params.go +++ b/chaincfg/params.go @@ -670,17 +670,17 @@ func CustomSignetParams(challenge []byte, dnsSeeds []DNSSeed) Params { ExpireTime: 1230767999, // December 31, 2008 UTC }, DeploymentCSV: { - BitNumber: 0, + BitNumber: 29, StartTime: 0, // Always available for vote ExpireTime: math.MaxInt64, // Never expires }, DeploymentSegwit: { - BitNumber: 1, + BitNumber: 29, StartTime: 0, // Always available for vote ExpireTime: math.MaxInt64, // Never expires. }, DeploymentTaproot: { - BitNumber: 2, + BitNumber: 29, StartTime: 0, // Always available for vote ExpireTime: math.MaxInt64, // Never expires. },