Content-Type: multipart/alternative;
 boundary="===============7376952736231412599=="
MIME-Version: 1.0
From: vjudeu@gazeta.pl
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>
Subject: Re: [bitcoin-dev] Proposal: Auto-shutdown as 5-year fork window
Precedence: list

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==--