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
|
Return-Path: <lf-lists@mattcorallo.com>
Received: from hemlock.osuosl.org (smtp2.osuosl.org [140.211.166.133])
by lists.linuxfoundation.org (Postfix) with ESMTP id 34E6FC000D
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 19 Feb 2021 14:13:09 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by hemlock.osuosl.org (Postfix) with ESMTP id 204A58717A
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 19 Feb 2021 14:13:09 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
Received: from hemlock.osuosl.org ([127.0.0.1])
by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id YpDRmAtPAiIh
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 19 Feb 2021 14:13:05 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from mail.as397444.net (mail.as397444.net [69.59.18.99])
by hemlock.osuosl.org (Postfix) with ESMTPS id 538CA87492
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 19 Feb 2021 14:13:05 +0000 (UTC)
Received: by mail.as397444.net (Postfix) with ESMTPSA id F19024A65C1;
Fri, 19 Feb 2021 14:13:00 +0000 (UTC)
X-DKIM-Note: Keys used to sign are likely public at https://as397444.net/dkim/
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mattcorallo.com;
s=1613742063; t=1613743981;
bh=blrhAVr7xkz5pgCSH1stK5EY2bFcO5qH5GWQi23dO4E=;
h=Subject:From:In-Reply-To:Cc:Date:References:To:From;
b=Bc4wFLqsBY/47YwjURsCwW1L7oocUurmlZyXeDtC0Ba/RnjnfLUfmc+R4UDgm7S/S
rFv3JOCp3e/lU4lye6iBp9toB3A8+KIKdP4XrOQhl+vHfBswkhpz5p+5w8vkSeQThm
QQfo3lO3zHL94o0uWYb9pm3Tyda6ifAW4mz0KWU4MO3uiEe7vWm5jylccl71kYIx5T
3zOkmoczTWIn3NRfA6ehhm56iu54HvpCjWIZ9RLZGmFJq8kZV0NBhETB5RB7yS+Oa5
qnEmBT8kKQojUSjYpd9lJeODB/JfFGPFtSWIsLZucyVzUuYHxIZuNL+aDspeWvIfZS
/6CreMqRc/ZFg==
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
From: Matt Corallo <lf-lists@mattcorallo.com>
In-Reply-To: <CALqxMTFKbjg3yDPnrmL8TgtypirB_fDMMJD=AJxjYav51hmEAw@mail.gmail.com>
Date: Fri, 19 Feb 2021 09:13:00 -0500
Message-Id: <E3E39A9A-82B4-4096-9DA1-A4D758CC7B68@mattcorallo.com>
References: <CALqxMTFKbjg3yDPnrmL8TgtypirB_fDMMJD=AJxjYav51hmEAw@mail.gmail.com>
To: Adam Back <adam@cypherspace.org>
Cc: Michael Folkson <michaelfolkson@gmail.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Yesterday's Taproot activation meeting on
lockinontimeout (LOT)
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: Fri, 19 Feb 2021 14:13:09 -0000
(Also in response to ZMN...)
Bitcoin Core has a long-standing policy of not shipping options which shoot y=
ourself in the foot. I=E2=80=99d be very disappointed if that changed now. P=
eople are of course more than welcome to run such software themselves, but I=
anticipate the loud minority on Twitter and here aren=E2=80=99t processing e=
nough transactions or throwing enough financial weight behind their decision=
for them to do anything but just switch back if they find themselves on a c=
hain with no blocks.
There=E2=80=99s nothing we can (or should) do to prevent people from threate=
ning to (and possibly) forking themselves off of bitcoin, but that doesn=E2=80=
=99t mean we should encourage it either. The work Bitcoin Core maintainers a=
nd developers do is to recommend courses of action which they believe have r=
easonable levels of consensus and are technically sound. Luckily, there=E2=80=
=99s strong historical precedent for people deciding to run other software a=
round forks, so misinterpretation is not very common (just like there=E2=80=99=
s strong historical precedent for miners not unilaterally deciding forks in t=
he case of Segwit).
Matt
> On Feb 19, 2021, at 07:08, Adam Back <adam@cypherspace.org> wrote:
>> would dev consensus around releasing LOT=3Dfalse be considered as "develo=
pers forcing their views on users"?
>=20
> given there are clearly people of both views, or for now don't care
> but might later, it would minimally be friendly and useful if
> bitcoin-core has a LOT=3Dtrue option - and that IMO goes some way to
> avoid the assumptive control via defaults.
> Otherwise it could be read as saying "developers on average
> disapprove, but if you, the market disagree, go figure it out for
> yourself" which is not a good message for being defensive and avoiding
> mis-interpretation of code repositories or shipped defaults as
> "control".
|
