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
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
|
Return-Path: <aymeric@peersm.com>
Received: from smtp4.osuosl.org (smtp4.osuosl.org [IPv6:2605:bc80:3010::137])
by lists.linuxfoundation.org (Postfix) with ESMTP id 91EAFC002B
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 4 Feb 2023 20:55:59 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp4.osuosl.org (Postfix) with ESMTP id 668AE41CB8
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 4 Feb 2023 20:55:59 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 668AE41CB8
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001,
RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001]
autolearn=ham autolearn_force=no
Received: from smtp4.osuosl.org ([127.0.0.1])
by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id ft4dvivLnEuI
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 4 Feb 2023 20:55:56 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 90CEB41CB4
Received: from smtpout2.mo529.mail-out.ovh.net
(smtpout2.mo529.mail-out.ovh.net [79.137.123.220])
by smtp4.osuosl.org (Postfix) with ESMTPS id 90CEB41CB4
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 4 Feb 2023 20:55:56 +0000 (UTC)
Received: from mxplan6.mail.ovh.net (unknown [10.109.156.206])
by mo529.mail-out.ovh.net (Postfix) with ESMTPS id 23EB920ACF;
Sat, 4 Feb 2023 20:55:54 +0000 (UTC)
Received: from peersm.com (37.59.142.103) by DAG6EX2.mxp6.local (172.16.2.52)
with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.17; Sat, 4 Feb
2023 21:55:47 +0100
Authentication-Results: garm.ovh; auth=pass
(GARM-103G0053e88a075-391f-44e2-b0f4-9026ae562407,
83B9442A37C74570B8CB15ECCD3A86C2760700E6) smtp.auth=aymeric@peersm.com
X-OVh-ClientIp: 92.184.100.83
To: Christopher Allen <ChristopherA@lifewithalacrity.com>
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>
<CACrqygB_FbsRGWYPSUEFTnP15y94Hmo4JtAuv6bH1D3YtbAw9Q@mail.gmail.com>
From: Aymeric Vitte <aymeric@peersm.com>
Message-ID: <b292d887-cbd5-165c-de01-793df2b5e8f3@peersm.com>
Date: Sat, 4 Feb 2023 21:55:47 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <CACrqygB_FbsRGWYPSUEFTnP15y94Hmo4JtAuv6bH1D3YtbAw9Q@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="------------B76D54563ACD6B327BA734D1"
X-Originating-IP: [37.59.142.103]
X-ClientProxiedBy: DAG9EX2.mxp6.local (172.16.2.82) To DAG6EX2.mxp6.local
(172.16.2.52)
X-Ovh-Tracer-GUID: 73eac680-7b40-4e30-b9da-442716ab266b
X-Ovh-Tracer-Id: 14291047519313617885
X-VR-SPAMSTATE: OK
X-VR-SPAMSCORE: -51
X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedvhedrudegvddgudegudcutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfqggfjpdevjffgvefmvefgnecuuegrihhlohhuthemucehtddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenogfuuhhsphgvtghtffhomhgrihhnucdlgeelmdenucfjughrpefuvfhfvefhkffffgggjggtihesrgdtreertdefjeenucfhrhhomhepteihmhgvrhhitgcugghithhtvgcuoegrhihmvghrihgtsehpvggvrhhsmhdrtghomheqnecuggftrfgrthhtvghrnhepgfetteevieetvefhfeevuddtgeffvdejhfdtueeitdegleevffefkeeuieejhedunecuffhomhgrihhnpehunhgthhgrihhnvggurdgtohhmpdhgihhthhhusgdrihhopdhmvgguihhumhdrtghomhdpphgvvghrshhmrdgtohhmpdhlihhnkhgvughinhdrtghomhdpghhithhhuhgsrdgtohhmnecukfhppeduvdejrddtrddtrddupdefjedrheelrddugedvrddutdefnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehinhgvthepuddvjedrtddrtddruddpmhgrihhlfhhrohhmpeeorgihmhgvrhhitgesphgvvghrshhmrdgtohhmqedpnhgspghrtghpthhtohepuddprhgtphhtthhopehkkhgrrhgrshgrvhhvrghssehgmhgrihhlrdgtohhmpdgsihhttghoihhnqdguvghvsehlihhsthhsrdhlihhnuhigfhhouhhnuggrthhiohhnrdhorhhgpdevhhhrihhsthhophhhvghrteeslh
hifhgvfihithhhrghlrggtrhhithihrdgtohhmpdfovfetjfhoshhtpehmohehvdelpdhmohguvgepshhmthhpohhuth
X-Mailman-Approved-At: Sat, 04 Feb 2023 20:59:51 +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 20:55:59 -0000
--------------B76D54563ACD6B327BA734D1
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Thanks Christopher, then I understand the process:
- I must issue a PR where I switch 80 to another number, even if I am
not a C/C++ expert it looks easy
- I must stay calm and answer all outstanding concerns about this
trivial change
- Since I am not as clever as the bitcoin devs I must be ready to revise
my PR at any time
- This could lead for the change to be from 80B to 82.xB where x comes
from a non understandable crypto formula
- I must evangelize the change worldwide
- Once accepted, I must collude (pay) with the nodes/miners so they
update at a subtile block height decided by the community
And then I must pray that the PR does not survive myself
Looks like a pretty straight forward process
I am on this list since quite some time, so, seriously, this change is
needed, or, as I said before, deviant behaviours will happen, because
the "witness trick" or others do not work at all, and are clearly
similar to ethereum messy stuff
Le 04/02/2023 =C3=A0 19:54, Christopher Allen a =C3=A9crit :
> On Sat, Feb 4, 2023 at 9:01 AM Aymeric Vitte <aymeric@peersm.com
> <mailto: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.=20
>
> 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.=20
>
> 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 go=
od
> proposal. The maintainers, based on their sense of the community=E2=80=99=
s
> interest and consensus, must 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:=20
>
> *
>
> https://unchained.com/blog/contributing-bitcoin-core-patience/
>
> *
>
> https://jonatack.github.io/articles/how-to-contribute-pull-requests=
-to-bitcoin-core
>
> *
>
> https://medium.com/@amitiu/onboarding-to-bitcoin-core-7c1a83b20365
>
> =E2=80=94 Christopher Allen=20
>
>
--=20
Sophia-Antipolis, France
CV: https://www.peersm.com/CVAV.pdf
LinkedIn: https://fr.linkedin.com/in/aymeric-vitte-05855b26
GitHub : https://www.github.com/Ayms
A Universal Coin Swap system based on Bitcoin: https://gist.github.com/Ay=
ms/029125db2583e1cf9c3209769eb2cdd7
A bitcoin NFT system: https://gist.github.com/Ayms/01dbfebf219965054b4a3b=
eed1bfeba7
Move your coins by yourself (browser version): https://peersm.com/wallet
Bitcoin transactions made simple: https://github.com/Ayms/bitcoin-transac=
tions
torrent-live: https://github.com/Ayms/torrent-live
node-Tor : https://www.github.com/Ayms/node-Tor
Anti-spies and private torrents, dynamic blocklist: http://torrent-live.p=
eersm.com
Peersm : http://www.peersm.com
--------------B76D54563ACD6B327BA734D1
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Thanks Christopher, then I understand the process:</p>
<p>- I must issue a PR where I switch 80 to another number, even if
I am not a C/C++ expert it looks easy</p>
<p>- I must stay calm and answer all outstanding concerns about
this trivial change</p>
<p>- Since I am not as clever as the bitcoin devs I must be ready to
revise my PR at any time</p>
<p>- This could lead for the change to be from 80B to 82.xB where x
comes from a non understandable crypto formula<br>
</p>
<p>- I must evangelize the change worldwide</p>
<p>- Once accepted, I must collude (pay) with the nodes/miners so
they update at a subtile block height decided by the community<br>
</p>
<p>And then I must pray that the PR does not survive myself</p>
<p>Looks like a pretty straight forward process<br>
</p>
<p>I am on this list since quite some time, so, seriously, this
change is needed, or, as I said before, deviant behaviours will
happen, because the "witness trick" or others do not work at all,
and are clearly similar to ethereum messy stuff<br>
</p>
<br>
<div class="moz-cite-prefix">Le 04/02/2023 à 19:54, Christopher
Allen a écrit :<br>
</div>
<blockquote
cite="mid:CACrqygB_FbsRGWYPSUEFTnP15y94Hmo4JtAuv6bH1D3YtbAw9Q@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div><span style="border-color:rgb(0,0,0)">On Sat, Feb 4, 2023 at
9:01 AM Aymeric Vitte <</span><a moz-do-not-send="true"
href="mailto:aymeric@peersm.com" target="_blank"
style="border-color:rgb(66,133,244)">aymeric@peersm.com</a><span
style="border-color:rgb(0,0,0)">> wrote:</span><br>
</div>
<div dir="auto">
<div class="gmail_quote"
style="width:396px;border-color:rgb(0,0,0);color:rgb(0,0,0)"
dir="auto">
<div style="border-color:rgb(0,0,0)">
<div class="gmail_quote"
style="width:396px;border-color:rgb(0,0,0)">
<blockquote class="gmail_quote"
style="width:396px;margin:0px 0px 0px
0.8ex;border-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="#FFFFFF" text="#000000"
style="border-color:rgb(0,0,0)">
<p dir="auto" style="border-color:rgb(0,0,0)">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.</p>
</div>
</blockquote>
<div dir="auto" style="border-color:rgb(0,0,0)">
<p dir="auto" style="border-color:rgb(0,0,0)">Here is
the simplified version:</p>
<p style="border-color:rgb(0,0,0)">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. </p>
<p style="border-color:rgb(0,0,0)">The conversation will
also move to the PR itself. Part of the challenge now
is getting review of your PRs - you’ll 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. </p>
<p style="border-color:rgb(0,0,0)">At some point
hopefully there looks like all reasonable objections
have been addressed.</p>
<p style="border-color:rgb(0,0,0)">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’t very transparent, especially
for even a good proposal. The maintainers, based on
their sense of the community’s interest 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="border-color:rgb(0,0,0)">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.</p>
<p style="border-color:rgb(0,0,0)">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.</p>
<p style="border-color:rgb(0,0,0)">These articles offers
more perspective: </p>
<ul style="border-color:rgb(0,0,0)">
<li style="border-color:rgb(0,0,0)">
<p style="border-color:rgb(0,0,0)"><a
moz-do-not-send="true"
href="https://unchained.com/blog/contributing-bitcoin-core-patience/"
target="_blank"
style="border-color:rgb(66,133,244)">https://unchained.com/blog/contributing-bitcoin-core-patience/</a></p>
</li>
<li style="border-color:rgb(0,0,0)">
<p style="border-color:rgb(0,0,0)"><a
moz-do-not-send="true"
href="https://jonatack.github.io/articles/how-to-contribute-pull-requests-to-bitcoin-core"
target="_blank"
style="border-color:rgb(66,133,244)">https://jonatack.github.io/articles/how-to-contribute-pull-requests-to-bitcoin-core</a></p>
</li>
<li style="border-color:rgb(0,0,0)">
<p style="border-color:rgb(0,0,0)"><a
moz-do-not-send="true"
href="https://medium.com/@amitiu/onboarding-to-bitcoin-core-7c1a83b20365"
target="_blank"
style="border-color:rgb(66,133,244)">https://medium.com/@amitiu/onboarding-to-bitcoin-core-7c1a83b20365</a></p>
</li>
</ul>
</div>
</div>
</div>
<div style="border-color:rgb(0,0,0)">
<div class="gmail_quote"
style="width:396px;border-color:rgb(0,0,0)">
<div dir="auto" style="border-color:rgb(0,0,0)">
<p dir="auto" style="border-color:rgb(0,0,0)">—
Christopher Allen </p>
</div>
</div>
</div>
</div>
<br class="Apple-interchange-newline" style="color:rgb(0,0,0)">
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Sophia-Antipolis, France
CV: <a class="moz-txt-link-freetext" href="https://www.peersm.com/CVAV.pdf">https://www.peersm.com/CVAV.pdf</a>
LinkedIn: <a class="moz-txt-link-freetext" href="https://fr.linkedin.com/in/aymeric-vitte-05855b26">https://fr.linkedin.com/in/aymeric-vitte-05855b26</a>
GitHub : <a class="moz-txt-link-freetext" href="https://www.github.com/Ayms">https://www.github.com/Ayms</a>
A Universal Coin Swap system based on Bitcoin: <a class="moz-txt-link-freetext" href="https://gist.github.com/Ayms/029125db2583e1cf9c3209769eb2cdd7">https://gist.github.com/Ayms/029125db2583e1cf9c3209769eb2cdd7</a>
A bitcoin NFT system: <a class="moz-txt-link-freetext" href="https://gist.github.com/Ayms/01dbfebf219965054b4a3beed1bfeba7">https://gist.github.com/Ayms/01dbfebf219965054b4a3beed1bfeba7</a>
Move your coins by yourself (browser version): <a class="moz-txt-link-freetext" href="https://peersm.com/wallet">https://peersm.com/wallet</a>
Bitcoin transactions made simple: <a class="moz-txt-link-freetext" href="https://github.com/Ayms/bitcoin-transactions">https://github.com/Ayms/bitcoin-transactions</a>
torrent-live: <a class="moz-txt-link-freetext" href="https://github.com/Ayms/torrent-live">https://github.com/Ayms/torrent-live</a>
node-Tor : <a class="moz-txt-link-freetext" href="https://www.github.com/Ayms/node-Tor">https://www.github.com/Ayms/node-Tor</a>
Anti-spies and private torrents, dynamic blocklist: <a class="moz-txt-link-freetext" href="http://torrent-live.peersm.com">http://torrent-live.peersm.com</a>
Peersm : <a class="moz-txt-link-freetext" href="http://www.peersm.com">http://www.peersm.com</a></pre>
</body>
</html>
--------------B76D54563ACD6B327BA734D1--
|