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"
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
Precedence: list

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