aboutsummaryrefslogtreecommitdiff
path: root/src/consensus
diff options
context:
space:
mode:
authorAnthony Towns <aj@erisian.com.au>2021-03-27 23:00:14 +1000
committerAnthony Towns <aj@erisian.com.au>2021-04-12 11:14:49 +1000
commit55ac5f568a3b73d6f1ef4654617fb76e8bcbccdf (patch)
tree2119c25550db38ca3befd8030dbae8338bd65aad /src/consensus
parentdd07e6da48040dc7eae46bc7941db48d98a669fd (diff)
versionbits: Add explicit NEVER_ACTIVE deployments
Previously we used deployments that would timeout prior to Bitcoin's invention, which allowed the deployment to still be activated in unit tests. This switches those deployments to be truly never active.
Diffstat (limited to 'src/consensus')
-rw-r--r--src/consensus/params.h5
1 files changed, 5 insertions, 0 deletions
diff --git a/src/consensus/params.h b/src/consensus/params.h
index 705205c95b..28c95e0884 100644
--- a/src/consensus/params.h
+++ b/src/consensus/params.h
@@ -43,6 +43,11 @@ struct BIP9Deployment {
* process (which takes at least 3 BIP9 intervals). Only tests that specifically test the
* behaviour during activation cannot use this. */
static constexpr int64_t ALWAYS_ACTIVE = -1;
+
+ /** Special value for nStartTime indicating that the deployment is never active.
+ * This is useful for integrating the code changes for a new feature
+ * prior to deploying it on some or all networks. */
+ static constexpr int64_t NEVER_ACTIVE = -2;
};
/**