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
|
Return-Path: <michaelfolkson@gmail.com>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133])
by lists.linuxfoundation.org (Postfix) with ESMTP id 2AFACC0001
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 1 Mar 2021 17:48:10 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp2.osuosl.org (Postfix) with ESMTP id 0C973430F9
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 1 Mar 2021 17:48:10 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -0.201
X-Spam-Level:
X-Spam-Status: No, score=-0.201 tagged_above=-999 required=5
tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001,
RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001]
autolearn=ham autolearn_force=no
Authentication-Results: smtp2.osuosl.org (amavisd-new);
dkim=pass (2048-bit key) header.d=gmail.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 wAdX9VozGxxJ
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 1 Mar 2021 17:48:09 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0
Received: from mail-oi1-f173.google.com (mail-oi1-f173.google.com
[209.85.167.173])
by smtp2.osuosl.org (Postfix) with ESMTPS id 57110430EC
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 1 Mar 2021 17:48:09 +0000 (UTC)
Received: by mail-oi1-f173.google.com with SMTP id x20so18866304oie.11
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 01 Mar 2021 09:48:09 -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
:content-transfer-encoding;
bh=Ogew7QdPJxtzLyiUJxxrYs3rdxAQAcsFuCPpTBZ6c20=;
b=kh/jS5zQfpWd42G0Ixzr/2CtSkQ1vITsfFPQfEXBmUOa0lhbCK6tllu9n1AnKljmvJ
m3mT6dW1NJ7yS8UKG3hGY+FAnery0IRvb7uRmumx7GAEEzQwBv26xjOpOrN/9vbJifyC
z9YzGm5pfgluyDT4cSt2wbtkDRmAQSRyQQhfax+EZdpSVxe33aBwO/Cn8l297GQfR5f5
K2OHut/afRCXVkOUfHiqozsthZUb6feHZcazCamUa/VXld4AIYE/RwaqwBOW5HMIC4WF
wFQyYoCh1ADmnovxfg4znX0n+ASV+lxh3iz4OmePAytYwfY4BKg6jKRBTJr3u8YZHtok
Pjug==
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
:content-transfer-encoding;
bh=Ogew7QdPJxtzLyiUJxxrYs3rdxAQAcsFuCPpTBZ6c20=;
b=lnyLrXsIMVvxIQaN67whQRhR1eQpa1IPTyOU89ksc+nspegYiPo+GrV6lwZwLP4h8N
iVzZvWgcMQcnzNfttwtpppmuS8jdvHSzfjTlfH/cDU96kDaqru6exrzirz/bW1oWDCQ1
/rFBHH8KqodJskt9/fLgauwQRzDhg3qxn3ocW262JJBxMm+GXE5Ldzp30lJSe8sTEmXX
j/nh9eJBtuUkuQlUa6WEjzRHP+DDB5+YvGaOLGSGrxS5HlgvDJnOTj/YZgU8aECN7GYS
ekzVoZ/Yi+ZKzNQR4Va8NOJdQIAqtb7NKmiNGcqC75r13Jgyha5y0jQoGGMnjFU3Oc+P
h60g==
X-Gm-Message-State: AOAM531kBG69U66LRCNL2g/OuxYhkRqRZIew8VeRYdctREwZXyuQyatQ
V6riwBL4fpgQQ6GWokZz3UX4W3rynrCru4doenGlKIowFomDgw==
X-Google-Smtp-Source: ABdhPJzeAYzpGr0Glg173QemRCQzx97tL1RxmjT5UNZC0pS4ZRj1tZ1VJvuCvH00Uy+cFxBgMrAW390peCZ95uwe+NQ=
X-Received: by 2002:aca:aa96:: with SMTP id t144mr3382oie.131.1614620888090;
Mon, 01 Mar 2021 09:48:08 -0800 (PST)
MIME-Version: 1.0
From: Michael Folkson <michaelfolkson@gmail.com>
Date: Mon, 1 Mar 2021 17:47:57 +0000
Message-ID: <CAFvNmHR0WwMp0eNQhvs9uFFSq3wGdHVTFUFmByLLdz7EUjg8uQ@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Mon, 01 Mar 2021 21:06:49 +0000
Subject: [bitcoin-dev] UASF (LOT=true) kick off meeting - Tuesday March 2nd
19:00 UTC on ##uasf IRC channel
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: Mon, 01 Mar 2021 17:48:10 -0000
It is approximately 8 months since Steve Lee formally kicked off the
Taproot activation discussion by setting up the ##taproot-activation
IRC channel. Obviously there was discussion that considerably predates
that but that was the first recognition that there needed to be a
focus towards a solution rather than endless circular debates.
Eight months on it appears there are some who think there is a
philosopher=E2=80=99s stone still out there that will garner 100 percent
consensus and contain zero chain split risk in the worst case
scenario. A philosopher=E2=80=99s stone that us mere mortals have failed to
find in these 8 months.
While I would be delighted if this philosopher=E2=80=99s stone is found (an=
d
all are free to continue looking) I think it is prudent at this point
to step away from the circular arguments and build on the progress we
have made in these last 8 months. We have effectively achieved
overwhelming consensus on the activation mechanism (BIP 8) and all of
the parameters apart from one (lockinontimeout or LOT). Again I=E2=80=99d l=
ike
to thank the people who have put hours of work into getting to this
point. It is thankless work and it is probably the last thing any of
us want to be doing.
At this point it is unclear whether Bitcoin Core will be able to
release any activation code whatsoever due to disagreement logjams.
Personally I hope they do but again it is prudent to prepare for the
scenario where Core is unable to. Hence I and others have assessed
that our energies are better spent working on a community release
implementing LOT=3Dtrue in a similar spirit to 2017=E2=80=99s UASF effort. =
I say
similar as this time there really is no need for any antagonism.
Approximately 90 percent of mining pools (taprootactivation.com) have
declared support and there is overwhelming community consensus to
activate Taproot. In the absence of a Core release with activation
code I hope and expect all users (including miners) to consider
supporting this UASF release and consider running it to activate
Taproot.
TL;DR Tomorrow (Tuesday) we are holding a kick off meeting for this
UASF (LOT=3Dtrue) effort on the ##uasf IRC channel at 19:00 UTC. Please
consider attending and supporting this effort to get Taproot
activated. It would be great to get users from the 2017 effort
involved in addition to recent Taproot proponents from all parts of
our community. The future of Bitcoin=E2=80=99s scalability and privacy depe=
nds
on, as it always has, on you the user.
--=20
Michael Folkson
Email: michaelfolkson@gmail.com
Keybase: michaelfolkson
PGP: 43ED C999 9F85 1D40 EAF4 9835 92D6 0159 214C FEE3
|
