Return-Path: Received: from smtp3.osuosl.org (smtp3.osuosl.org [IPv6:2605:bc80:3010::136]) by lists.linuxfoundation.org (Postfix) with ESMTP id 1EEC4C002B for ; 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 ; 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 ; 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 ; Sat, 4 Feb 2023 18:54:54 +0000 (UTC) Received: by mail-lf1-x136.google.com with SMTP id w11so12283550lfu.11 for ; 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: <57f780b1-f262-9394-036c-70084320e9cf@peersm.com> <3d00aacb-585d-f875-784d-34352860d725@peersm.com> In-Reply-To: <3d00aacb-585d-f875-784d-34352860d725@peersm.com> From: Christopher Allen Date: Sat, 4 Feb 2023 10:54:41 -0800 Message-ID: To: Aymeric Vitte Content-Type: multipart/alternative; boundary="0000000000004b285b05f3e4554b" X-Mailman-Approved-At: Sat, 04 Feb 2023 19:04:22 +0000 Cc: Bitcoin Protocol Discussion 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 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
On Sat, Feb 4, 2023 at 9:01 AM= Aymeric Vitte <aymeric@peersm.com> wrote:

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.

Here is the simplified version:

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

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

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

If there is enough interest and few objections there will be di= scussions by the community & 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.

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.

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.

These articles offers = more perspective:=C2=A0

=E2=80=94 Christopher Allen=C2=A0


--0000000000004b285b05f3e4554b--