summaryrefslogtreecommitdiff
path: root/33/5fa9e317a0685c683a0e3eb541f60ab8028e37
blob: d94cda48310f52ca57284446cfc0603fb686371d (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
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
Return-Path: <christophera@gmail.com>
Received: from smtp3.osuosl.org (smtp3.osuosl.org [IPv6:2605:bc80:3010::136])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 1EEC4C002B
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat,  4 Feb 2023 18:54:56 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp3.osuosl.org (Postfix) with ESMTP id E07C660DA0
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat,  4 Feb 2023 18:54:55 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org E07C660DA0
Authentication-Results: smtp3.osuosl.org;
 dkim=pass (2048-bit key) header.d=lifewithalacrity-com.20210112.gappssmtp.com
 header.i=@lifewithalacrity-com.20210112.gappssmtp.com header.a=rsa-sha256
 header.s=20210112 header.b=YBwvpKfp
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level: 
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001,
 HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001,
 RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001]
 autolearn=no autolearn_force=no
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 0hb9lZt8wC9x
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat,  4 Feb 2023 18:54:55 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp3.osuosl.org A102B60A47
Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com
 [IPv6:2a00:1450:4864:20::136])
 by smtp3.osuosl.org (Postfix) with ESMTPS id A102B60A47
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat,  4 Feb 2023 18:54:54 +0000 (UTC)
Received: by mail-lf1-x136.google.com with SMTP id w11so12283550lfu.11
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Sat, 04 Feb 2023 10:54:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=lifewithalacrity-com.20210112.gappssmtp.com; s=20210112;
 h=cc:to:subject:message-id:date:from:in-reply-to:references
 :mime-version:from:to:cc:subject:date:message-id:reply-to;
 bh=1lJ4z6sTwAOokuVqOJgvT9ahLErgtAvSkKL8hNgmrBI=;
 b=YBwvpKfpP1azPfOzNG1lZuLvjgsKDbYSDbkz9asc6BYjh1IRLH4QRJwQMw5xtGazaS
 7N0Bgmshynf9sjigOx/OyPr3QuhBNXG/nVkJYQMWGiOAZ5T0sMdyZfXKyZj5sOqaPqjq
 Zf5poAv9ugdWHew5ZFpcU7qPOe6i8Oz1e5FfPFCg/oyIkAJdNCRaGnHT918ipqSeNNZN
 kMh+j3FR1wp2R0l+RYkhC7/bYFvVc7+bNZbCecp9ZNzHwZUxhh1F0GHYlQNeO4IbVz9D
 DLFdAUEbrDsviMGUHNpCJdUPv2lUNaD3ieuPztg3bqKXlDRGa2gwo4SqvgRzyUcZuRA8
 T1uw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=cc:to:subject:message-id:date:from:in-reply-to:references
 :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id
 :reply-to;
 bh=1lJ4z6sTwAOokuVqOJgvT9ahLErgtAvSkKL8hNgmrBI=;
 b=5/5WN7AifIlk0aqFP26UXxm/LpIPx3su3RLdn8OgdN8nL9AMAPpHqUTxej0PQZ6h3Z
 L66AFlJ8wzm24P8WhIKkz7D1JHG1R1Wfv76J2Bk1B37/1d0lW/LElDWhP4HHOM9BE580
 /mhZ/sSfQuEDWoVMzPYmhsbYPYwSW4aCFlEbfCzVg56SeZ4bkK0tx2R/CtnOZlaisveM
 HV2aMOhchpsv6v8ca464Gpsbvah+kk64UGUJh0XnJ6R2dQScXnAAKDjbI5mkpKgJGGr5
 DvHE1vTluccz2olJuOgBFG9/+qdmD38ypu2ibWKthxsXB+ni4M2kFmAJpEcxCoCV2+SI
 aB5w==
X-Gm-Message-State: AO0yUKVnbSD6s8lV9qHBl0r+COrfQlw2SrvPSwEzd0uTR0j1hwdc4kmF
 M6/o70tmihqoLSlEKgPEGYuqewtB9CguEv7GqWo=
X-Google-Smtp-Source: AK7set9EbxfRe9xbzgCReLJjQXEuht3pvDT4NSzg5OhBrA+CShWdQ5TNmAjPKP32HiEzQeZZzf8XLzBsTJXMwFQMNZw=
X-Received: by 2002:a05:6512:793:b0:4cc:9fa6:aba7 with SMTP id
 x19-20020a056512079300b004cc9fa6aba7mr2692033lfr.201.1675536892634; Sat, 04
 Feb 2023 10:54:52 -0800 (PST)
MIME-Version: 1.0
References: <CACrqygAMsO1giYuxm=DZUqfeRjEqGM7msmEnZ-AHws3oA2=aqw@mail.gmail.com>
 <ca8622cb-445e-4258-bbac-b3ee1ce95f4c@protonmail.com>
 <57f780b1-f262-9394-036c-70084320e9cf@peersm.com>
 <CACrqygCNf3Gv8+VjhyqS4GTb3Epo8qXEKGtQB6sqyR6ib44-fA@mail.gmail.com>
 <CABE6yHtM2Dqc63_eURSr7dMirJti5sYnqvHj7vQ_Ab9FC_d04g@mail.gmail.com>
 <3d00aacb-585d-f875-784d-34352860d725@peersm.com>
In-Reply-To: <3d00aacb-585d-f875-784d-34352860d725@peersm.com>
From: Christopher Allen <ChristopherA@lifewithalacrity.com>
Date: Sat, 4 Feb 2023 10:54:41 -0800
Message-ID: <CACrqygB_FbsRGWYPSUEFTnP15y94Hmo4JtAuv6bH1D3YtbAw9Q@mail.gmail.com>
To: Aymeric Vitte <aymeric@peersm.com>
Content-Type: multipart/alternative; boundary="0000000000004b285b05f3e4554b"
X-Mailman-Approved-At: Sat, 04 Feb 2023 19:04:22 +0000
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE
 OP_IF OP_PUSH
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, 04 Feb 2023 18:54:56 -0000

--0000000000004b285b05f3e4554b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sat, Feb 4, 2023 at 9:01 AM Aymeric Vitte <aymeric@peersm.com> wrote:

> What is the official bitcoin channel to request the OP_RETURN size change=
?
> (press often mentions that ethereum is good to manage changes and bitcoin=
 a
> complete zero.
>
Here is the simplified version:

Most of these changes start with discussions like these, but then are moved
concretely to a PR to bitcoin-core with the code changes (in this case
there is no fork so pretty easy) and an introductory comment pointing to
discussions elsewhere.

The conversation will also move to the PR itself. Part of the challenge now
is getting review of your PRs - you=E2=80=99ll need to evangelize some and/=
or have
social capital in the bitcoin community to get sufficient ACKs to your PR
(and some NACKs which you will calmly addres), and someone will likely
point something out you missed, so you revise the PR.

At some point hopefully there looks like all reasonable objections have
been addressed.

If there is enough interest and few objections there will be discussions by
the community & maintainers to merge it. It is this last part that isn=E2=
=80=99t
very transparent, especially for even a good proposal. The maintainers,
based on their sense of the community=E2=80=99s interest and consensus, mus=
t choose
when to say it is ready, and then decide when and to which release they
wish to merge it.

They often start by requesting you to revise your changes to be off by
default, and be turned on as an option for a specific release. Often PR
contributors know this is coming and include it.

Even once it is released, this type of change can only happen after
sufficient miners and nodes update to the release and turn it on. If
sufficient do, then the maintainers evaluate when to have the feature on by
default.

These articles offers more perspective:

   -

   https://unchained.com/blog/contributing-bitcoin-core-patience/
   -


   https://jonatack.github.io/articles/how-to-contribute-pull-requests-to-b=
itcoin-core
   -

   https://medium.com/@amitiu/onboarding-to-bitcoin-core-7c1a83b20365

=E2=80=94 Christopher Allen

>

--0000000000004b285b05f3e4554b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div><span style=3D"border-color:rgb(0,0,0)">On Sat, Feb 4, 2023 at 9:01 AM=
 Aymeric Vitte &lt;</span><a href=3D"mailto:aymeric@peersm.com" target=3D"_=
blank" style=3D"border-color:rgb(66,133,244)">aymeric@peersm.com</a><span s=
tyle=3D"border-color:rgb(0,0,0)">&gt; wrote:</span><br></div><div dir=3D"au=
to"><div class=3D"gmail_quote" style=3D"width:396px;border-color:rgb(0,0,0)=
;color:rgb(0,0,0)" dir=3D"auto"><div style=3D"border-color:rgb(0,0,0)"><div=
 class=3D"gmail_quote" style=3D"width:396px;border-color:rgb(0,0,0)"><block=
quote class=3D"gmail_quote" style=3D"width:396px;margin:0px 0px 0px 0.8ex;b=
order-left-width:1px;border-left-style:solid;padding-left:1ex;border-color:=
rgb(0,0,0) rgb(0,0,0) rgb(0,0,0) rgb(204,204,204)"><div bgcolor=3D"#FFFFFF"=
 text=3D"#000000" style=3D"border-color:rgb(0,0,0)"><p dir=3D"auto" style=
=3D"border-color:rgb(0,0,0)">What is the official bitcoin channel to reques=
t the OP_RETURN size change? (press often mentions that ethereum is good to=
 manage changes and bitcoin a complete zero.</p></div></blockquote><div dir=
=3D"auto" style=3D"border-color:rgb(0,0,0)"><p dir=3D"auto" style=3D"border=
-color:rgb(0,0,0)">Here is the simplified version:</p><p style=3D"border-co=
lor:rgb(0,0,0)">Most of these changes start with discussions like these, bu=
t then are moved concretely to a PR to bitcoin-core with the code changes (=
in this case there is no fork so pretty easy) and an introductory comment p=
ointing to discussions elsewhere.=C2=A0</p><p style=3D"border-color:rgb(0,0=
,0)">The conversation will also move to the PR itself. Part of the challeng=
e now is getting review of your PRs - you=E2=80=99ll need to evangelize som=
e and/or have social capital in the bitcoin community to get sufficient ACK=
s to your PR (and some NACKs which you will calmly addres), and someone wil=
l likely point something out you missed, so you revise the PR.=C2=A0</p><p =
style=3D"border-color:rgb(0,0,0)">At some point hopefully there looks like =
all reasonable objections have been addressed.</p><p style=3D"border-color:=
rgb(0,0,0)">If there is enough interest and few objections there will be di=
scussions by the community &amp; maintainers to merge it. It is this last p=
art that isn=E2=80=99t very transparent, especially for even a good proposa=
l. The maintainers, based on their sense of the community=E2=80=99s interes=
t and consensus, must choose when to say it is ready, and then decide when =
and to which release they wish to merge it.</p><p style=3D"border-color:rgb=
(0,0,0)">They often start by requesting you to revise your changes to be of=
f by default, and be turned on as an option for a specific release. Often P=
R contributors know this is coming and include it.</p><p style=3D"border-co=
lor:rgb(0,0,0)">Even once it is released, this type of change can only happ=
en after sufficient miners and nodes update to the release and turn it on. =
If sufficient do, then the maintainers evaluate when to have the feature on=
 by default.</p><p style=3D"border-color:rgb(0,0,0)">These articles offers =
more perspective:=C2=A0</p><ul style=3D"border-color:rgb(0,0,0)"><li style=
=3D"border-color:rgb(0,0,0)"><p style=3D"border-color:rgb(0,0,0)"><a href=
=3D"https://unchained.com/blog/contributing-bitcoin-core-patience/" target=
=3D"_blank" style=3D"border-color:rgb(66,133,244)">https://unchained.com/bl=
og/contributing-bitcoin-core-patience/</a></p></li><li style=3D"border-colo=
r:rgb(0,0,0)"><p style=3D"border-color:rgb(0,0,0)"><a href=3D"https://jonat=
ack.github.io/articles/how-to-contribute-pull-requests-to-bitcoin-core" tar=
get=3D"_blank" style=3D"border-color:rgb(66,133,244)">https://jonatack.gith=
ub.io/articles/how-to-contribute-pull-requests-to-bitcoin-core</a></p></li>=
<li style=3D"border-color:rgb(0,0,0)"><p style=3D"border-color:rgb(0,0,0)">=
<a href=3D"https://medium.com/@amitiu/onboarding-to-bitcoin-core-7c1a83b203=
65" target=3D"_blank" style=3D"border-color:rgb(66,133,244)">https://medium=
.com/@amitiu/onboarding-to-bitcoin-core-7c1a83b20365</a></p></li></ul></div=
></div></div><div style=3D"border-color:rgb(0,0,0)"><div class=3D"gmail_quo=
te" style=3D"width:396px;border-color:rgb(0,0,0)"><div dir=3D"auto" style=
=3D"border-color:rgb(0,0,0)"><p dir=3D"auto" style=3D"border-color:rgb(0,0,=
0)">=E2=80=94 Christopher Allen=C2=A0</p></div><blockquote class=3D"gmail_q=
uote" style=3D"width:396px;margin:0px 0px 0px 0.8ex;border-left-width:1px;b=
order-left-style:solid;padding-left:1ex;border-color:rgb(0,0,0) rgb(0,0,0) =
rgb(0,0,0) rgb(204,204,204)"><div bgcolor=3D"#FFFFFF" text=3D"#000000" styl=
e=3D"border-color:rgb(0,0,0)"><p dir=3D"auto" style=3D"border-color:rgb(0,0=
,0)"></p></div></blockquote></div></div></div><br class=3D"Apple-interchang=
e-newline" style=3D"color:rgb(0,0,0)"></div>

--0000000000004b285b05f3e4554b--