1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
|
Return-Path: <eric@voskuil.org>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133])
by lists.linuxfoundation.org (Postfix) with ESMTP id 93C55C0001
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 6 Mar 2021 10:26:35 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp2.osuosl.org (Postfix) with ESMTP id 7539643022
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 6 Mar 2021 10:26:35 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: smtp2.osuosl.org (amavisd-new);
dkim=pass (2048-bit key) header.d=voskuil-org.20150623.gappssmtp.com
Received: from smtp2.osuosl.org ([127.0.0.1])
by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id VRHvq18jwWsd
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 6 Mar 2021 10:26:34 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
Received: from mail-pl1-x62a.google.com (mail-pl1-x62a.google.com
[IPv6:2607:f8b0:4864:20::62a])
by smtp2.osuosl.org (Postfix) with ESMTPS id 63A66414F6
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 6 Mar 2021 10:26:34 +0000 (UTC)
Received: by mail-pl1-x62a.google.com with SMTP id d8so2649762plg.10
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 06 Mar 2021 02:26:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=voskuil-org.20150623.gappssmtp.com; s=20150623;
h=content-transfer-encoding:from:mime-version:subject:date:message-id
:references:cc:in-reply-to:to;
bh=xG2+x2wVCHgbxLHcx6nC0UI7OJINkuugxZ5aOcZWSGM=;
b=JZd/UH4/5DlzI7a8yb8afVgzY2szJ4PHi8OqvXonmgfT0h5GYrchU/rpdOr0469Zvy
4niLK/Hf35iczczE/r1eL9o8f9ucacFAnj2czo9IW2WJlVU/AArvmuydsF9YOlq+PCFD
E1mid1FkgE8iBZMzXPFBQsBPuj4DVUyKjBlCJ2IjrJ/62ki+Bc+xFN/KmrwiQth7tLCw
s1Np2DLtKOof+tHkCc1Ga4O5nDekWSbLW+j3roNCSUI1m+oub1UnqSka7HevMpHAEU3Q
SZVOMS7Et7rOBqGJTDyoUdpXPe6HDYLyRehMG9e7/uJOZav+uKmGuelVSJItR93aG1ky
Z4ZA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:content-transfer-encoding:from:mime-version
:subject:date:message-id:references:cc:in-reply-to:to;
bh=xG2+x2wVCHgbxLHcx6nC0UI7OJINkuugxZ5aOcZWSGM=;
b=p5+YkDDWkQQyn7W24ClNFTSULxl+TPfBroNvcZuUCF2ZHLxW3k4GFZAo7ICuCOQHZT
08zH+2ywH9EczkjO8wx9oV5RTur1w4NJAKMWDEwrB0Ze4buWBHA53Dxtftk3MM5LZX+B
mdj3UvTFwAE2Tj+PXacC0StOLn4xwH+S2RQt/zdlce6ZVhi5MP7i917VgV12Uu9orlXZ
ULeg4CIkcU9K2U4PbLXzTVLgDv7zRV2yo0R8pZYlSbUXEpQojbhSjxuD9QQRvSCIdJYB
gqQolTFBj1LLQ6dtGMW8wc666DbNFUt5kua1xkJjpR9VER+AKH3Jd4u+Fs8YJpYzCJb8
yBpQ==
X-Gm-Message-State: AOAM5325bmEaXfFL8y+jLM67xl8ELHaak4a3jc63sZT383k8+32KPf7o
mgSPHNEKVqpKX7Jgv6GUF4m/0YA3BdnED62o
X-Google-Smtp-Source: ABdhPJwlXhxtCYWYiYMQBCFXeIB1l91fc/wB3JXi8ufdPykOmB75bgs0eR1gZRRZgVNG6rbcTf63zw==
X-Received: by 2002:a17:90a:ce92:: with SMTP id
g18mr15225389pju.52.1615026393712;
Sat, 06 Mar 2021 02:26:33 -0800 (PST)
Received: from ?IPv6:2601:600:9c00:1d0::250e? ([2601:600:9c00:1d0::250e])
by smtp.gmail.com with ESMTPSA id x9sm4757779pjp.3.2021.03.06.02.26.32
(version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128);
Sat, 06 Mar 2021 02:26:33 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: Eric Voskuil <eric@voskuil.org>
Mime-Version: 1.0 (1.0)
Date: Sat, 6 Mar 2021 02:26:32 -0800
Message-Id: <BFE9416D-BAC6-4772-ABA0-DC3B4784C7B7@voskuil.org>
References: <20210306092931.6jmw6o2u7a2gewwb@erisian.com.au>
In-Reply-To: <20210306092931.6jmw6o2u7a2gewwb@erisian.com.au>
To: Anthony Towns <aj@erisian.com.au>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
X-Mailer: iPhone Mail (18D52)
Subject: Re: [bitcoin-dev] Taproot activation proposal "Speedy Trial"
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Mar 2021 10:26:35 -0000
The most sensible approach I=E2=80=99ve seen yet.
e
> On Mar 6, 2021, at 01:29, Anthony Towns via bitcoin-dev <bitcoin-dev@lists=
.linuxfoundation.org> wrote:
>=20
> =EF=BB=BFOn Fri, Mar 05, 2021 at 05:43:43PM -1000, David A. Harding via bi=
tcoin-dev wrote:
>> ## Example timeline
>> - T+0: release of one or more full nodes with activation code
>> - T+14: signal tracking begins
>> - T+28: earliest possible lock in
>> - T+104: locked in by this date or need to try a different activation pro=
cess
>> - T+194: activation (if lockin occurred)
>=20
>> ### Base activation protocol
>> The idea can be implemented on top of either Bitcoin Core's existing
>> BIP9 code or its proposed BIP8 patchset.[6]
>> BIP9 is already part of Bitcoin Core and I think the changes being
>> proposed would be relatively small, resulting in a small patch that
>> could be easy to review.
>=20
> To get to specifics, here's a PR, based on #21334, that updates bip9
> to support an extra parameter to delay the transition from LOCKED_IN
> to ACTIVE until a particular timestamp is reached, and to reduce the
> activation threshold to 90%:
>=20
> https://github.com/bitcoin/bitcoin/pull/21377
>=20
> With that in mind, I think the example timeline above could translate
> to taproot parameters of:
>=20
> nStartTime =3D 1618358400; // April 14, 2021
> nTimeout =3D 1626220800; // July 14 2021
> activation_time =3D 1633046400; // October 1 2021
>=20
> That is, signalling begins with the first retarget period whose parent's
> median time is at least April 14th; and concludes with the last retarget
> period whose final block's median time is prior to July 14th; that's
> 91 days which should be about ~6.5 retarget periods, so should cover 6
> full retarget periods, but could only cover 5. Activation is delayed
> until the first retarget period where the final block of the previous
> retarget period has a timestamp of at least October 1st.
>=20
> Note that the timeout there is prior to the expected timestamp of the
> startheight block specified in the proposal for bip8 parameters:
>=20
> https://en.bitcoin.it/wiki/Taproot_activation_proposal_202102
>=20
> and earliest activation is after the expected release of 22.0 and hence
> the maintenance end of 0.20.
>=20
> Note also that the PR above specifies the delay as a deadline, not a
> delta between lockin and activation; so earlier lockin does not produce
> an earlier activation with the code referenced above.
>=20
> Cheers,
> aj
>=20
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
|
