path: root/78/9be099ba95ec701f172852a84e2e59b0794ad3

Return-Path: <raystonn@hotmail.com>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 7355DC0001
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat, 22 May 2021 19:55:57 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp2.osuosl.org (Postfix) with ESMTP id 6171440209
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat, 22 May 2021 19:55:57 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 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, SPF_HELO_PASS=-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=hotmail.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 lsXKG8bjpAxd
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat, 22 May 2021 19:55:55 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
Received: from NAM12-DM6-obe.outbound.protection.outlook.com
 (mail-dm6nam12olkn20816.outbound.protection.outlook.com
 [IPv6:2a01:111:f400:fe59::816])
 by smtp2.osuosl.org (Postfix) with ESMTPS id BABB240101
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat, 22 May 2021 19:55:55 +0000 (UTC)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none;
 b=muqGfjUPIxkMRkOXvHJoGBvUMw0vZKVx5hVLAh6oN/61AkVSPlJI8YJI08Dto2ZR1ib/A1pD2GoDu8OYioBDQHHS5OdYs5ESURLzzpCO0MF8ibc4OCcNb4kW3EhlPEqzdeO9Ynv2SLyRUjZF3d2V9vOBuG+fyRTTWTA7hshlWrDOeUMLySpCrVyspK03NoWIfRIntM2RAWBtG3nk0XtTV94fW+Zk2NZmC34MJvXQsMCemQuq7BaO4RAHPbdR2/P43/k0qnpBtkcKNStU7VErCrT+K2NwQNH0g8h4H2sBShHiBtS7ao3CkWtVUza2joeglLBAEtEth8vAKZgyMAtQ9A==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; 
 s=arcselector9901;
 h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
 bh=Wi7msG9dVH2pKJ8jExxd+6KEpP4Vg/iXoN5r6YNs/QA=;
 b=HpUbpKgGWY7yAtzZjpMCGsMvfuuj+DAUuKT6t622kcnO3hTW7lXMN2HF0ZOELP3n2O0TD60B/cj5S6FmDFWY0aVRI+b0w4rffsnEQwTkmHMstbx8Ib0leZGe+MrUtDPGTkKLXu2l3CyGRui8zYKSOZBJcRF1rT+p/vEO0tHdRqg++zBkscAol8s/TS+ZwRzAuNfz1I80xbOVvg5J6MR65dpPT6YydoEEpSfbhuI+71pTm/SPUSeZUiHSnvChad5PHl1aHOB+gLSc9dmAu1bIZOhsRlM0bsq95OR8tYMuIr5IEo7HsuEZYXHwUcZnCXDU2RzTayS19AdPR3qmOEpfCw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=none; dmarc=none;
 dkim=none; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com;
 s=selector1;
 h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
 bh=Wi7msG9dVH2pKJ8jExxd+6KEpP4Vg/iXoN5r6YNs/QA=;
 b=Bv7kNdMNJS+uVfhTCYLw1Zv2DU+6IvOL7hXapWtoQ9nxW0lmejY1Yv46unaaWf3X2Sy82sMLcZHxgIUnjc7AzSRGrJeCHGEQ4yV4CmlzQ0OopQALYfYtaoj6tlBVJLo3KQp0EHCwdyQt5EmpsUsE5gL/LZZPmu2tXII2SfhZ5WiOJEmA4DJ0GN3HAN/fDruMU5xYcM336RH7D3tcfMh2JK7BOaPHf6EFY+Kw78NgAbK2etqSDLTS1/h1GBmB4+HqaHFitaa4FXts1Ou3TUTTWq3riC2OEaboOWcma/wKsbwBaf0v53Dw4n/yoHrvPYBqHaih5ZnKvmw1qptE9nowVw==
Received: from DM6NAM12FT013.eop-nam12.prod.protection.outlook.com
 (2a01:111:e400:fc64::48) by
 DM6NAM12HT226.eop-nam12.prod.protection.outlook.com (2a01:111:e400:fc64::239)
 with Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4150.11; Sat, 22 May
 2021 19:55:53 +0000
Received: from DM6PR02MB6187.namprd02.prod.outlook.com
 (2a01:111:e400:fc64::41) by DM6NAM12FT013.mail.protection.outlook.com
 (2a01:111:e400:fc64::66) with Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4150.11 via Frontend
 Transport; Sat, 22 May 2021 19:55:53 +0000
Received: from DM6PR02MB6187.namprd02.prod.outlook.com
 ([fe80::fd60:5248:224b:50b]) by DM6PR02MB6187.namprd02.prod.outlook.com
 ([fe80::fd60:5248:224b:50b%7]) with mapi id 15.20.4150.026; Sat, 22 May 2021
 19:55:53 +0000
From: "Raystonn ." <raystonn@hotmail.com>
To: =?iso-8859-1?Q?Jorge_Tim=F3n?= <jtimon@jtimon.cc>, Bitcoin Protocol
 Discussion <bitcoin-dev@lists.linuxfoundation.org>
Thread-Topic: [bitcoin-dev] Consensus protocol immutability is a feature
Thread-Index: AQHXTpAv6/wYfx0CHEOdYVdnKwLU7qrvl92AgABSVUg=
Date: Sat, 22 May 2021 19:55:53 +0000
Message-ID: <DM6PR02MB6187F5E2A74950211F3934C9CD289@DM6PR02MB6187.namprd02.prod.outlook.com>
References: <DM6PR02MB6187B30D0941044E24699FF8CD299@DM6PR02MB6187.namprd02.prod.outlook.com>,
 <CABm2gDpSWEA+AU1OKGBatuFT8biSO2S8MxfvRH8wHbF7=OEetQ@mail.gmail.com>
In-Reply-To: <CABm2gDpSWEA+AU1OKGBatuFT8biSO2S8MxfvRH8wHbF7=OEetQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-incomingtopheadermarker: OriginalChecksum:0473F32F31D4D2DD3B66F73AC4A4391339363DE8F02121B4670AFF17110C3FCF;
 UpperCasedChecksum:503308A929AECEDE079C2F8EFE38DE1781AF2F5D9C7DC5CAD670C2FF54B8D91A;
 SizeAsReceived:7201; Count:44
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [8TE0IqlPTwNzKXlwsYEzkaZ0E//YGYi7Gveku5Zg1dQ7Dso5W+OUKq5Fecw9Vf/Y]
x-ms-publictraffictype: Email
x-incomingheadercount: 44
x-eopattributedmessage: 0
x-ms-office365-filtering-correlation-id: c47ece75-b351-4131-c732-08d91d5b9b81
x-ms-traffictypediagnostic: DM6NAM12HT226:
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: dBnQVKFNQsPkGCFTb86rFbDuU5OBsmBD0v40ydSx6x4KVhRBPxkvi9TvC481kVskG+PXkaJWeB2LajrsSJ7+e1ulZD3FshwBip3hOySRNGPbLQgSXTkfIIrPDp2lOg2LJf97ZIETIOaUWwG0C2/0cl2Rfh4JuNr6bzom/ZSp4zjozo58476n9ryrDy1HGmVkAupr3X/n82xzRyAcVbKb37vNGl6p8WkrIokwm0Xiv3dn360ORejPSZ2UWXm7PJu3X1Vp9sqmNnjRa5HiOvV6fpEuPrqm5XhZO0vNYSUuWmZnyTn9vezooPLD5zQb/KfaAr5zGxOz5V7qrBQRi7VLpzO2NGlJNUeQhtI4BefA2TwmsmgzR7s9jMo/Rvw68oOIU/MHbSfFFLJJFp70KYecK7yJ44WcjssHkOF/Mhb+gfC8pWfIvO6q6AHI/9teRU1420sHMbb5gVffMuVynUAocg==
x-ms-exchange-antispam-messagedata: xjil/iFYEQipZoTZmqrjbM0x9iDDljAXMd5cWKcMYmSsSFkf3NAfeQYYQ9slVkDUtHIzUXVMQwkPz/FglqADP8z6vPGBBuxGR49S7x8/3ae/ou2Ti9beoaCJ9KKXkF6sHCGPXSNeOd3oFDo96qc9KPrJ2rGFjV85CpaxmYX/bkZ2/qxCwA/zju5imwHd0z+l+5+5gu1ddkLhikv0DF/4nA==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative;
 boundary="_000_DM6PR02MB6187F5E2A74950211F3934C9CD289DM6PR02MB6187namp_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-AuthSource: DM6NAM12FT013.eop-nam12.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: c47ece75-b351-4131-c732-08d91d5b9b81
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 May 2021 19:55:53.6669 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6NAM12HT226
X-Mailman-Approved-At: Sat, 22 May 2021 20:25:29 +0000
Subject: Re: [bitcoin-dev] Consensus protocol immutability is a feature
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: Sat, 22 May 2021 19:55:57 -0000

--_000_DM6PR02MB6187F5E2A74950211F3934C9CD289DM6PR02MB6187namp_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

None of these required a hard fork.  I should rephrase my previous email to=
 clarify the intended topic as hard consensus changes, requiring a hard for=
k.  "Soft" forks can be useful.

Raystonn

________________________________
From: Jorge Tim=F3n <jtimon@jtimon.cc>
Sent: Saturday, May 22, 2021 7:55 AM
To: Raystonn . <raystonn@hotmail.com>; Bitcoin Protocol Discussion <bitcoin=
-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Consensus protocol immutability is a feature

That is clearly not true. People entretain making changes to the protocol a=
ll the time. Bitcoin is far from perfect and not improving it would be stup=
id in my opinion.
Some improvements require changes to the consensus rules.
Recent changes include relative lock time verify or segwit. These are impor=
tant changes that made things like lightning much easier and efficient than=
 they could possibly be without them.
Taproot, which is a recent proposal, could help simplify the lightning prot=
ocol even further, and make it more efficient and its usage more private. A=
nd there are more use cases.

There have been consensus rule changes since bitcoin started, and with good=
 reason. As a user, you can always oppose new changes. And if enough users =
agree with you, you will be able to maintain your own chain with the old ru=
les. At the same time, there's nothing you can do to stop other users who w=
ant those changes from coordinating with each other to adopt them.

Perhaps you're interested in bip99, which discusses consensus rule changes =
in more detail.



On Sat, May 22, 2021, 13:09 Raystonn . via bitcoin-dev <bitcoin-dev@lists.l=
inuxfoundation.org<mailto:bitcoin-dev@lists.linuxfoundation.org>> wrote:
Suggestions to make changes to Bitcoin's consensus protocol will only ever =
be entertained if Bitcoin is completely dead without such a change.  Any at=
tempt to change consensus protocol without a clear and convincing demonstra=
tion to the entire network of participants that Bitcoin will die without th=
at change is a waste of your own time.  Bitcoin's resistance to consensus c=
hanges is a feature that makes it resistant to being coopted and corrupted.=
  I recommend developers focus on making improvements that do not attempt t=
o change the consensus protocol.  Otherwise, you are simply working on an a=
ltcoin, which is off-topic here.

Raystonn

_______________________________________________
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org<mailto:bitcoin-dev@lists.linuxfoundat=
ion.org>
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

--_000_DM6PR02MB6187F5E2A74950211F3934C9CD289DM6PR02MB6187namp_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body>
<div>None of these required a hard fork.&nbsp; I should rephrase my previou=
s email to clarify the intended topic as hard consensus changes, requiring =
a hard fork.&nbsp; &quot;Soft&quot; forks can be useful.</div>
<div><br>
</div>
<div>Raystonn</div>
<div><br>
</div>
<hr style=3D"display:inline-block;width:98%" tabindex=3D"-1">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" st=
yle=3D"font-size:11pt" color=3D"#000000"><b>From:</b> Jorge Tim=F3n &lt;jti=
mon@jtimon.cc&gt;<br>
<b>Sent:</b> Saturday, May 22, 2021 7:55 AM<br>
<b>To:</b> Raystonn . &lt;raystonn@hotmail.com&gt;; Bitcoin Protocol Discus=
sion &lt;bitcoin-dev@lists.linuxfoundation.org&gt;<br>
<b>Subject:</b> Re: [bitcoin-dev] Consensus protocol immutability is a feat=
ure</font>
<div>&nbsp;</div>
</div>
<div>
<div dir=3D"auto">That is clearly not true. People entretain making changes=
 to the protocol all the time. Bitcoin is far from perfect and not improvin=
g it would be stupid in my opinion.
<div dir=3D"auto">Some improvements require changes to the consensus rules.=
</div>
<div dir=3D"auto">Recent changes include relative lock time verify or segwi=
t. These are important changes that made things like lightning much easier =
and efficient than they could possibly be without them.</div>
<div dir=3D"auto">Taproot, which is a recent proposal, could help simplify =
the lightning protocol even further, and make it more efficient and its usa=
ge more private. And there are more use cases.</div>
<div dir=3D"auto"><br>
</div>
<div dir=3D"auto">There have been consensus rule changes since bitcoin star=
ted, and with good reason. As a user, you can always oppose new changes. An=
d if enough users agree with you, you will be able to maintain your own cha=
in with the old rules. At the same
 time, there's nothing you can do to stop other users who want those change=
s from coordinating with each other to adopt them.</div>
<div dir=3D"auto"><br>
</div>
<div dir=3D"auto">Perhaps you're interested in bip99, which discusses conse=
nsus rule changes in more detail.</div>
<div dir=3D"auto"><br>
</div>
<div dir=3D"auto"><br>
</div>
</div>
<br>
<div class=3D"x_gmail_quote">
<div dir=3D"ltr" class=3D"x_gmail_attr">On Sat, May 22, 2021, 13:09 Rayston=
n . via bitcoin-dev &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation=
.org">bitcoin-dev@lists.linuxfoundation.org</a>&gt; wrote:<br>
</div>
<blockquote class=3D"x_gmail_quote" style=3D"margin:0 0 0 .8ex; border-left=
:1px #ccc solid; padding-left:1ex">
<div dir=3D"ltr">
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
Suggestions to make changes to Bitcoin's consensus protocol will only ever =
be entertained if Bitcoin is completely dead without such a change.&nbsp;&n=
bsp;<span style=3D"background-color:rgb(255,255,255); display:inline!import=
ant">Any attempt to change consensus protocol
 without a clear and convincing demonstration to the entire network of part=
icipants that Bitcoin will die without that change is a waste of your own t=
ime.&nbsp;&nbsp;</span><span style=3D"color:rgb(0,0,0); font-family:Calibri=
,Helvetica,sans-serif; font-size:12pt">Bitcoin's
 resistance to consensus changes is a feature that makes it resistant to be=
ing coopted and corrupted.&nbsp; I recommend developers focus on making imp=
rovements that do not attempt to change the consensus protocol.&nbsp; Other=
wise, you are simply working on an altcoin,
 which is off-topic here.</span></div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
<span style=3D"color:rgb(0,0,0); font-family:Calibri,Helvetica,sans-serif; =
font-size:12pt"><br>
</span></div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
Raystonn</div>
<div style=3D"font-family:Calibri,Helvetica,sans-serif; font-size:12pt; col=
or:rgb(0,0,0)">
<br>
</div>
</div>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank" =
rel=3D"noreferrer">bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer noreferrer" target=3D"_blank">https://lists.linuxfoundati=
on.org/mailman/listinfo/bitcoin-dev</a><br>
</blockquote>
</div>
</div>
</body>
</html>

--_000_DM6PR02MB6187F5E2A74950211F3934C9CD289DM6PR02MB6187namp_--