summaryrefslogtreecommitdiff
path: root/82/9f5199ede9b25139dc1f6a1aba5bbcceda6757
blob: 55aabd75d6cada15e25c923401d812be5e4bcf42 (plain)
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
Return-Path: <vjudeu@gazeta.pl>
Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 9DF21C000D
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun, 12 Sep 2021 19:39:00 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp3.osuosl.org (Postfix) with ESMTP id 7AF1F605F5
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun, 12 Sep 2021 19:39:00 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, 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_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001,
 SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: smtp3.osuosl.org (amavisd-new);
 dkim=pass (1024-bit key) header.d=gazeta.pl
Received: from smtp3.osuosl.org ([127.0.0.1])
 by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id pbFKEL_k8-Ir
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun, 12 Sep 2021 19:38:58 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
Received: from smtpo105.poczta.onet.pl (smtpo105.poczta.onet.pl
 [213.180.149.158])
 by smtp3.osuosl.org (Postfix) with ESMTPS id 1B4EF605E4
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sun, 12 Sep 2021 19:38:57 +0000 (UTC)
Received: from pmq4v.m5r2.onet (pmq4v.m5r2.onet [10.174.32.70])
 by smtp.poczta.onet.pl (Onet) with ESMTP id 4H70KQ2hTGz1rPs;
 Sun, 12 Sep 2021 21:38:50 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gazeta.pl; s=2013;
 t=1631475530; bh=HzT7zMScANcPVpC9pB1m2P8r72OVeljtwGyYxIgftN0=;
 h=From:To:In-Reply-To:Date:Subject:From;
 b=mIsGQbtz75xhys9QhVSkSs8CBrdlHIBDPQdeBCOVQBhoZ7D2qSnes4Y18wAoEEnhJ
 zYtMJJn60tuXZALo91ARBI0uCPxEG0mWegXj8Ttfn4eM9ZqiuOQlgxvS8flSLDuebA
 BX/xCGV+FgD2lFtW6sYE91J+dIxihuoVz/imySXw=
Content-Type: multipart/alternative;
 boundary="===============7376952736231412599=="
MIME-Version: 1.0
Received: from [5.173.253.144] by pmq4v.m5r2.onet via HTTP id ;
 Sun, 12 Sep 2021 21:38:50 +0200
From: vjudeu@gazeta.pl
X-Priority: 3
To: James Lu <jamtlu@gmail.com>,bitcoin-dev@lists.linuxfoundation.org
In-Reply-To: <CANQHGB2SwZGrFAWC0Rd88qACTjPa1L+hbV54LG87M9RJZni+4Q@mail.gmail.com>
Date: Sun, 12 Sep 2021 21:38:47 +0200
Message-Id: <140815317-3f36d45615e153403b3c83e26c266773@pmq4v.m5r2.onet>
X-Mailer: onet.poczta
X-Onet-PMQ: <vjudeu@gazeta.pl>;5.173.253.144;PL;2
X-Mailman-Approved-At: Sun, 12 Sep 2021 19:49:23 +0000
Subject: Re: [bitcoin-dev] Proposal: Auto-shutdown as 5-year fork window
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: Sun, 12 Sep 2021 19:39:00 -0000

This is a multi-part message in MIME format.
--===============7376952736231412599==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

You can do that kind of change in your own Bitcoin-compatible client, but y=
ou cannot be sure that other people will run that version and that it will =
shut down when you want. Many miners use their own custom software for mini=
ng blocks, the same for mining pools. There are many clients that are compa=
tible with consensus, but different than Bitcoin Core.
Also you should notice that Bitcoin community make changes by using soft-fo=
rks, not hard-forks. Backward compatibility is preserved as often as possib=
le and there is no reason to change that. Any change can be deployed in a s=
oft-fork way, even "evil soft-forks" are possible, as described in https://=
petertodd.org/2016/forced-soft-forks. I think that kind of soft-fork is sti=
ll better than hard-fork.
On 2021-09-12 21:16:00 user James Lu via bitcoin-dev <bitcoin-dev@lists.lin=
uxfoundation.org> wrote:
If MTP-11 is greater than 5 years after the release date of the current sof=
tware version, the full node should shut down automatically.
=C2=A0
This would=C2=A0allow writing code that=C2=A0gives the community ~5 years t=
o upgrade to a version that executes a new hard fork while keeping everyone=
 in consensus, provided the change is non-controversial.
--===============7376952736231412599==
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<div>You can do that kind of change in your own Bitcoin-compatible client, =
but you cannot be sure that other people will run that version and that it =
will shut down when you want. Many miners use their own custom software for=
 mining blocks, the same for mining pools. There are many clients that are =
compatible with consensus, but different than Bitcoin Core.<br /><br />Also=
 you should notice that Bitcoin community make changes by using soft-forks,=
 not hard-forks. Backward compatibility is preserved as often as possible a=
nd there is no reason to change that. Any change can be deployed in a soft-=
fork way, even "evil soft-forks" are possible, as described in https://pete=
rtodd.org/2016/forced-soft-forks. I think that kind of soft-fork is still b=
etter than hard-fork.<br /><br /></div>
<div>On 2021-09-12 21:16:00 user James Lu via bitcoin-dev &lt;bitcoin-dev@l=
ists.linuxfoundation.org&gt; wrote:</div>
<blockquote style=3D"margin-left: 7px; border-left: 2px solid orange; paddi=
ng-left: 8px;">
<div dir=3D"ltr">
<div class=3D"gmail_default" style=3D"font-family: arial,helvetica,sans-ser=
if; font-size: small; color: #000000;">If MTP-11 is greater than 5 years af=
ter the release date of the current software version, the full node should =
shut down automatically.</div>
<div class=3D"gmail_default" style=3D"font-family: arial,helvetica,sans-ser=
if; font-size: small; color: #000000;">&nbsp;</div>
<div class=3D"gmail_default" style=3D"font-family: arial,helvetica,sans-ser=
if; font-size: small; color: #000000;">This would&nbsp;allow writing code t=
hat&nbsp;gives the community ~5 years to upgrade to a version that executes=
 a new hard fork while keeping everyone in consensus, provided the change i=
s non-controversial.</div>
</div>
</blockquote>

--===============7376952736231412599==--