Return-Path: Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136]) by lists.linuxfoundation.org (Postfix) with ESMTP id 4461EC000A for ; Sat, 10 Apr 2021 17:00:02 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp3.osuosl.org (Postfix) with ESMTP id 2B47C6085D for ; Sat, 10 Apr 2021 17:00:02 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -4.199 X-Spam-Level: X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 7Xy11idXX24q for ; Sat, 10 Apr 2021 17:00:01 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0 Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by smtp3.osuosl.org (Postfix) with ESMTPS id D37BA6085C for ; Sat, 10 Apr 2021 17:00:00 +0000 (UTC) Received: from mail-io1-f47.google.com (mail-io1-f47.google.com [209.85.166.47]) (authenticated bits=0) (User authenticated as jlrubin@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 13AGxwKt000559 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT) for ; Sat, 10 Apr 2021 12:59:59 -0400 Received: by mail-io1-f47.google.com with SMTP id v123so2279809ioe.10 for ; Sat, 10 Apr 2021 09:59:59 -0700 (PDT) X-Gm-Message-State: AOAM532hV4lNdnOh8YoVk5+k/bn+ApvDTBoZC90bsswKHXJqd4USvrfv hlmVF41A3KQan3jNYgO7G169pWhp9PQpcKkpkGc= X-Google-Smtp-Source: ABdhPJx3+9m8w2VzgG/C+aCQb3Trl2HQD7BnHBnRt1BGUWe5rCrGlkH+hsgRPfdNS9pp5W4Fdg4NIOyhvSQAVm1og7k= X-Received: by 2002:a02:9408:: with SMTP id a8mr20906025jai.73.1618073998366; Sat, 10 Apr 2021 09:59:58 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Jeremy Date: Sat, 10 Apr 2021 09:59:46 -0700 X-Gmail-Original-Message-ID: Message-ID: To: Michael Folkson , Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="000000000000e49ec605bfa13518" Cc: bitcoinmechanicca@protonmail.com Subject: Re: [bitcoin-dev] Taproot activation meeting on IRC - Tuesday 13th April 19:00 UTC 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, 10 Apr 2021 17:00:02 -0000 --000000000000e49ec605bfa13518 Content-Type: text/plain; charset="UTF-8" I concur that reviewing #21377 is the best path at this time. However, I want to draw attention to the middle road here: If Core chooses to not release activation params (which has been discussed as a general concept previously), #21377 can also be used to safely issue a community release. It's a false dichotomy between ST released by Core and a BIP8 UASF. -- @JeremyRubin On Sat, Apr 10, 2021 at 9:48 AM Michael Folkson via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > Hi Bitcoin Mechanic > > I will attend but I will be looking at Core PR #21377 over the next > couple of days and I would encourage other reviewers to review that PR > too. If that PR is merged into Core I would strongly recommend any > alternative release be fully compatible with the activation parameters > in Core. > > We can discuss in the meeting what we think the cut off date should be > for when Core should no longer be a consideration. Personally I think > (and hope) we will see progress on #21377 in the coming days. > > For the sake of the mailing list Bitcoin Mechanic has set up a meeting > to discuss an alternative release to Core with Taproot activation > code. > > Thanks > Michael > > > Taproot activation meeting on IRC - Tuesday 13th April 19:00 UTC > > > The focus of the meeting will be ratifying the Taproot activation plan > previously discussed at the March 16th meeting (aka 2021-03 Plan Y as > summarized here): > > > https://docs.google.com/spreadsheets/d/1K3pmH09yXLTHGV3wqFZGR3ei7QVwtdEwo0PjI2NHD3w/edit#gid=0 > > > While there was never any consensus reached on the LOT parameter, there > appears to be consensus on BIP8 and the remaining parameters, and more than > sufficient support for LOT=True to proceed safely. > > > Miners will have 18 months in which to signal and accelerate activation. > If not, taproot will activate regardless. > > > With a majority of the economy running this it will guarantee eventual > lock-in of taproot with the smallest chance of a chain split. > > > As a reminder, the channel is also open for ongoing discussion 24/7, and > there is a web chat client here: > > > https://webchat.freenode.net/?channel=##taproot-activation > > > Best, > > > Bitcoin Mechanic > > > Sent with [ProtonMail](https://protonmail.com/) Secure Email. > > > -- > Michael Folkson > Email: michaelfolkson@gmail.com > Keybase: michaelfolkson > PGP: 43ED C999 9F85 1D40 EAF4 9835 92D6 0159 214C FEE3 > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > --000000000000e49ec605bfa13518 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I concur that reviewing #= 21377 is the best path at this time.

However, I want to draw atte= ntion to the middle road here:

If Core chooses to not release activat= ion params (which has been discussed as a general concept previously), #213= 77 can also be used to safely issue a community release.

It's= a false dichotomy between ST released by Core and a BIP8 UASF.


On Sat, Apr 10,= 2021 at 9:48 AM Michael Folkson via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote:
Hi = Bitcoin Mechanic

I will attend but I will be looking at Core PR #21377 over the next
couple of days and I would encourage other reviewers to review that PR
too. If that PR is merged into Core I would strongly recommend any
alternative release be fully compatible with the activation parameters
in Core.

We can discuss in the meeting what we think the cut off date should be
for when Core should no longer be a consideration. Personally I think
(and hope) we will see progress on #21377 in the coming days.

For the sake of the mailing list Bitcoin Mechanic has set up a meeting
to discuss an alternative release to Core with Taproot activation
code.

Thanks
Michael

> Taproot activation meeting on IRC - Tuesday 13th April 19:00 UTC

> The focus of the meeting will be ratifying the Taproot activation plan= previously discussed at the March 16th meeting (aka 2021-03 Plan Y as summ= arized here):

http= s://docs.google.com/spreadsheets/d/1K3pmH09yXLTHGV3wqFZGR3ei7QVwtdEwo0PjI2N= HD3w/edit#gid=3D0

> While there was never any consensus reached on the LOT parameter, ther= e appears to be consensus on BIP8 and the remaining parameters, and more th= an sufficient support for LOT=3DTrue to proceed safely.

> Miners will have 18 months in which to signal and accelerate activatio= n. If not, taproot will activate regardless.

> With a majority of the economy running this it will guarantee eventual= lock-in of taproot with the smallest chance of a chain split.

> As a reminder, the channel is also open for ongoing discussion 24/7, a= nd there is a web chat client here:

> https://webchat.freenode.net/?cha= nnel=3D##taproot-activation

> Best,

> Bitcoin Mechanic

> Sent with [ProtonMail](https://protonmail.com/) Secure Email.


--
Michael Folkson
Email: michae= lfolkson@gmail.com
Keybase: michaelfolkson
PGP: 43ED C999 9F85 1D40 EAF4 9835 92D6 0159 214C FEE3
_______________________________________________
bitcoin-dev mailing list
= bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mail= man/listinfo/bitcoin-dev
--000000000000e49ec605bfa13518--