aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDavid A. Harding <dave@dtrt.org>2016-10-17 14:14:14 -0400
committerDavid A. Harding <dave@dtrt.org>2016-10-17 14:14:14 -0400
commitbf86073e45b475c37bc250c03d1f05a18fc9a190 (patch)
tree5438d32578d1193feb48eecb2236d129e705f512
parent2de93f0a9bf244d23aa9ebbea99c412d6de82473 (diff)
Release notes: correct segwit signalling period start conditions
[ci skip]
-rw-r--r--doc/release-notes.md9
1 files changed, 5 insertions, 4 deletions
diff --git a/doc/release-notes.md b/doc/release-notes.md
index 55c764d7c1..d107f305d6 100644
--- a/doc/release-notes.md
+++ b/doc/release-notes.md
@@ -68,10 +68,11 @@ benefits to Bitcoin users.
Activation for the segwit soft fork is being managed using BIP9
versionbits. Segwit's version bit is bit 1, and nodes will begin
-tracking which blocks signal support for segwit on 15 November 2016
-(UTC). If 95% of blocks within a 2,016-block retarget period (about two
-weeks) signal support for segwit, the soft fork will be locked in.
-After another 2,016 blocks, segwit will activate.
+tracking which blocks signal support for segwit at the beginning of the
+first retarget period after segwit's start date of 15 November 2016. If
+95% of blocks within a 2,016-block retarget period (about two weeks)
+signal support for segwit, the soft fork will be locked in. After
+another 2,016 blocks, segwit will activate.
For more information about segwit, please see the [segwit FAQ][], the
[segwit wallet developers guide][] or BIPs [141][BIP141], [143][BIP143],