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: <emu@emuadmin.com>
Received: from smtp4.osuosl.org (smtp4.osuosl.org [IPv6:2605:bc80:3010::137])
by lists.linuxfoundation.org (Postfix) with ESMTP id 1906CC000A
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 16 Mar 2021 17:42:37 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp4.osuosl.org (Postfix) with ESMTP id EFC754ECB2
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 16 Mar 2021 17:42:36 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level:
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, T_SPF_PERMERROR=0.01]
autolearn=ham autolearn_force=no
Received: from smtp4.osuosl.org ([127.0.0.1])
by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id NRSrOtBwhPFr
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 16 Mar 2021 17:42:35 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
Received: from mail.emuadmin.com (mail.emuadmin.com [108.61.189.74])
by smtp4.osuosl.org (Postfix) with ESMTPS id 436CF4EC95
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 16 Mar 2021 17:42:35 +0000 (UTC)
Received: by mail.emuadmin.com (Postfix, from userid 1001)
id 21C587590E; Tue, 16 Mar 2021 17:42:33 +0000 (UTC)
Date: Tue, 16 Mar 2021 17:42:33 +0000
From: Emil Pfeffer <emu@emuadmin.com>
To: Luke Dashjr <luke@dashjr.org>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Message-ID: <20210316174233.pfby4grwz5cudjqb@www01.emuadmin.com>
References: <202103151720.04687.luke@dashjr.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <202103151720.04687.luke@dashjr.org>
X-Mailman-Approved-At: Tue, 16 Mar 2021 19:24:51 +0000
Subject: Re: [bitcoin-dev] Taproot activation meeting on IRC - Tuesday 16th
March 19:00 UTC
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: Tue, 16 Mar 2021 17:42:37 -0000
On Mon, Mar 15, 2021 at 05:20:04PM +0000, Luke Dashjr via bitcoin-dev wrote:
> At the previous meeting, there was consensus for BIP8 activation parameters
> except for LOT, assuming a release around this time. Since then, a release
> has not occurred, and the new idea of Speedy Trial has been proposed to
> preempt the original/main activation plan.
>
> It's probably a good idea to meet up again to discuss these things and adjust
> accordingly.
>
> Agenda:
>
> - Speedy Trial: Can we get a comparable consensus on the proposal?
> (Note: current draft conflicts with original plan timeline)
Definitely not. This looks like a hijacking attempt.
We are already bombarded with too much information, the last thing we need is
a rushed upgrade. Even if it works out it is not a good precedent.
The current timeline of 18 months if the minimum that is acceptable for upgrades
such as taproot. We're not changing things that we worked out already. What next?
and how long till we go back and change the coin supply?
I understand some of you have no patience and would like mass adoption tomorrow
but those are exactly the people that do not have a say in Bitcoin development.
if you want to get rich quick you do not care about Bitcoin. If you want faster
development cycles then you have lightning to play with.
I have to reiterate: we *DO NOT* change things we already established in the past.
There are reasons everything is as it is and if you want to develop Bitcoin you have
to build upon the already established rules.
> - Main activation, post ST: Moving startheight (and timeoutheight?) later
> is probably a good idea at this point, both because too little progress has
> been made on it, and to avoid the conflict with the current ST draft.
There is no conflict. We're not upgrading Bitcoin using fancy new tools.
We're still on track with the already established timeline.
Although one is better than the other it doesn't really matter because we know
which way is going to go. In order to solve the LOT debate lets give Wladimir the
power to decide on his own and if he has no strong opinions he should just flip a coin.
the MAST threshold can be even lower because it is not representative of an economic
majority and it could speed up the upgrade.
>
> - Making progress: To date, too few people have been involved in materialising
> the main activation plan. If it's going to move forward, more people need to
> get actively involved. This should not wait for ST to complete, unless we
> want another 4-5 month slip of the timeline.
Nope. This is not the time where people need to get involved. There is no need for
more noise. People will get involved progressivly as time advances but as long
as Core does not release the parameters of the game there are no incentives for
the actors that will play the Taproot upgrade to show up. If Taproot is what the
market wants then the game theoretics of Bitcoin will get us there but since an
upgrade essentially means a change in consensus then some disturbance is expected and guaranteed.
At this point involve as few people as possible and get it done. This is just about
the software and the parameters of the new consesus. Theres plenty of time
for the show that's about to come, the market will do what the market does.
Worst case scenario Luke get some people behind and fork off Core with LOT=true and
lower MAST threshold. The market wants to play.
>
> This meeting is tentatively scheduled for *tomorrow*, March 16th at the usual
> time of 19:00 UTC, in freenode's ##Taproot-activation IRC channel. If turnout
> is too low, we can postpone it a week, but it'd be nice to get things
> resolved and moving sooner.
>
> As a reminder, the channel is also open for ongoing discussion 24/7, and there
> is a web chat client here:
>
> https://webchat.freenode.net/?channel=##taproot-activation
>
> Luke
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
--
|
