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
|
Return-Path: <johnqrand@gmail.com>
Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138])
by lists.linuxfoundation.org (Postfix) with ESMTP id EFA47C000A
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 3 Mar 2021 23:33:14 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp1.osuosl.org (Postfix) with ESMTP id B0D6384377
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 3 Mar 2021 23:33:14 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: 0.602
X-Spam-Level:
X-Spam-Status: No, score=0.602 tagged_above=-999 required=5
tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001,
HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001,
SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: smtp1.osuosl.org (amavisd-new);
dkim=pass (2048-bit key) header.d=gmail.com
Received: from smtp1.osuosl.org ([127.0.0.1])
by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id YRenyYbuS0U4
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 3 Mar 2021 23:33:08 +0000 (UTC)
X-Greylist: delayed 00:30:39 by SQLgrey-1.8.0
Received: from mail-oi1-x236.google.com (mail-oi1-x236.google.com
[IPv6:2607:f8b0:4864:20::236])
by smtp1.osuosl.org (Postfix) with ESMTPS id C45B784374
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 3 Mar 2021 23:33:07 +0000 (UTC)
Received: by mail-oi1-x236.google.com with SMTP id q203so4999825oih.5
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 03 Mar 2021 15:33:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:from:date:message-id:subject:to;
bh=plTRR4XNNcc70VD51ucBD+VHjs2WhCIkFzy4ilMQMc4=;
b=C+swfyktXZ0ClcVYaxxWHjj+BwzzhAtH9of48d3DpzchWlwaApHDeXgSqoH9j7z8NY
d/hphmMPN8Sau2DkhNlO2VEGqtDjieloXQG51Km908Q+WMJShgcCeRTtmieTKdAERCjN
FP+tb3miglIlSouibmibV0knjgeX+dlKh38Pz+N2UlfPdMVVSr8llDsdcC3S0UZDaHk3
8UffnHXIDa4IFkdW92XvJd+8MP2q+47gY8G9Kw3QHHgPxhLZhHmeZ9FRDpuA61UZcXba
KFhaK6EJer7rCHHusDJtfFv+l/1cJuZ4UdnNAM3wCVj70z733xcR7DZRJBZO54yFghAf
3Gww==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
bh=plTRR4XNNcc70VD51ucBD+VHjs2WhCIkFzy4ilMQMc4=;
b=jtDoBVZQhKMzKJuPVuyCAJ+Qd1QOHwyzEraiTVmJUr9l9Nz+oV1f7bLPsoc+Pil6+N
3o3PL0rWGwN5LATyiR7YNMtX3PbEYlV5Aac/Jbs4N8T5vAuSCrLGL4yitE0BW5uoUg9f
eSEkh1qX2eUBYbS3noB+Zha0B0NyzC0/Gktm/79bURKBb7m0dNuQKKD4fK793C3Uvx+p
pFU0E1butBPrduXcOUeroWfX59gMWj+cIqQw71478MUKl60aqrY7JKOS/DIQFSUpFPND
yQjJ4dAJRpUFV4hr10squ9XvbZrYZg07sMlh2ippjyq0RxkXO9+iGefAnrtR+69yg9e8
E09w==
X-Gm-Message-State: AOAM530xgFxC1c+1UieJpTLbhDb+f4pWR+2PXPb+qlmc5srWLxxrEgf4
f+OOYFZZRSG3iM75/Ww+0e7YIeI8NufddLpWUHs0X4Jfxr7FmM79
X-Google-Smtp-Source: ABdhPJwpFJQA3OO/mtPsFjSTkdhnJVjCKh5sDrhpX49T3m0QQWN5j+tf/kOadHVJkMB00nZLCZPWXpSTssPY41lUAyU=
X-Received: by 2002:aca:d68e:: with SMTP id n136mr953394oig.179.1614812547148;
Wed, 03 Mar 2021 15:02:27 -0800 (PST)
MIME-Version: 1.0
From: John Rand <johnqrand@gmail.com>
Date: Wed, 3 Mar 2021 23:02:14 +0000
Message-ID: <CAJXtxW=Rix7Q-ra=CADsB00r13pr5DC_76QMGcYrt74FxAWEbQ@mail.gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary="000000000000406f3305bca9d8aa"
X-Mailman-Approved-At: Thu, 04 Mar 2021 09:06:54 +0000
Subject: [bitcoin-dev] activation mechanism considerations
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: Wed, 03 Mar 2021 23:33:15 -0000
--000000000000406f3305bca9d8aa
Content-Type: text/plain; charset="UTF-8"
Consensus is important for both taproot and separately for the activation
mechanism. There are more soft-forks that Bitcoin will need, so it is
important to achieve positive progress on the activation topic also, not
get impatient and rush something ill-considered. Not all future soft-forks
maybe as widely supported as taproot, and yet it could become existentially
critical that Bitcoin prevails in achieving a future upgrade in dramatic
circumstances, even against powerful interests counter to Bitcoin user and
investors interests. We should treat the activation topic in a considered
way and with decorum, provide tight non-emotive reasoning devoid of
frustration and impatience. This is a low drama and convenient time to
incrementally improve activation. People have varied views about the
deciding factor, or even which factors resulted in segwit activating after
BIP 141 failed using BIP 9. We do not have to solve everything in one
step, incremental improvement is good, for complex unintuitive topics, to
learn as we go - and it should not be hard to do less badly than what
transpired leading up to BIP 148 and BIP 91. Failure to upgrade if
permanent, or demoralizing to protocol researchers could be a systemic risk
in itself as there are more upgrades Bitcoin will need. We are not Ents
but we should use our collective ingenuity to find an incremental
improvement for activation.
John R
--000000000000406f3305bca9d8aa
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Consensus is important for both taproot and separately for=
the activation mechanism.=C2=A0 There are more soft-forks that Bitcoin wil=
l need, so it is important to achieve positive progress on the activation t=
opic also, not get impatient and rush something ill-considered.=C2=A0 Not a=
ll future soft-forks maybe as widely supported as taproot, and yet it could=
become existentially critical that Bitcoin prevails in achieving a future =
upgrade in dramatic circumstances, even against powerful interests counter =
to Bitcoin user and investors interests.=C2=A0 We should treat the activati=
on topic in a considered way and with decorum, provide tight non-emotive re=
asoning devoid of frustration and impatience.=C2=A0 This is a low drama and=
convenient time to incrementally improve activation.=C2=A0 People have var=
ied views about the deciding factor, or even which factors resulted in segw=
it activating after BIP 141 failed using BIP 9.=C2=A0 We do not have to sol=
ve everything in one step, incremental improvement is good, for complex uni=
ntuitive topics, to learn as we go - and it should not be hard to do less b=
adly than what transpired leading up to BIP 148 and BIP 91.=C2=A0 Failure t=
o upgrade if permanent, or demoralizing to protocol researchers could be a =
systemic risk in itself as there are more upgrades Bitcoin will need.=C2=A0=
We are not Ents but we should use our collective ingenuity to find an incr=
emental improvement for activation.<div><div><br></div></div><div>John R</d=
iv></div>
--000000000000406f3305bca9d8aa--
|
