Return-Path: Received: from smtp4.osuosl.org (smtp4.osuosl.org [IPv6:2605:bc80:3010::137]) by lists.linuxfoundation.org (Postfix) with ESMTP id D60B3C000A for ; Sun, 4 Apr 2021 04:39:26 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp4.osuosl.org (Postfix) with ESMTP id B56EE405FC for ; Sun, 4 Apr 2021 04:39:26 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 OvsxFq_kDVko for ; Sun, 4 Apr 2021 04:39:25 +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 smtp4.osuosl.org (Postfix) with ESMTPS id 0F2E8405E6 for ; Sun, 4 Apr 2021 04:39:24 +0000 (UTC) Received: from mail-io1-f52.google.com (mail-io1-f52.google.com [209.85.166.52]) (authenticated bits=0) (User authenticated as jlrubin@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 1344dMog010326 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT) for ; Sun, 4 Apr 2021 00:39:23 -0400 Received: by mail-io1-f52.google.com with SMTP id x16so9110949iob.1 for ; Sat, 03 Apr 2021 21:39:23 -0700 (PDT) X-Gm-Message-State: AOAM533+Gx8ps2AsQwjafy1e2YuBS+ydJ3sVM+LRfCXrvPQqqFatTJxu K8IFLvYa/DX0ASvuz1BSkvgR9ju0Yf1nQ/uYDPQ= X-Google-Smtp-Source: ABdhPJwwHKBLQQEpcWdrCX4Sgf5OqfpX0sclaXH5HoAQ+gaSzK+vOI9My6ljEuzaNtlVrIwEjt+FQ2kAhhLYVn9jZXs= X-Received: by 2002:a05:6602:1da:: with SMTP id w26mr15857849iot.170.1617511162775; Sat, 03 Apr 2021 21:39:22 -0700 (PDT) MIME-Version: 1.0 From: Jeremy Date: Sat, 3 Apr 2021 21:39:11 -0700 X-Gmail-Original-Message-ID: Message-ID: To: Bitcoin development mailing list Content-Type: multipart/alternative; boundary="000000000000470c6605bf1e2a2f" Subject: [bitcoin-dev] Taproot Activation Meeting Reminder: April 6th 19:00 UTC bitcoin/bitcoin-dev 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: Sun, 04 Apr 2021 04:39:26 -0000 --000000000000470c6605bf1e2a2f Content-Type: text/plain; charset="UTF-8" We'll be having another meeting this Tuesday, as per https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-March/018699.html. If you can't make it feel free to leave a comment on any agenda item below, or if you think there are other things to be discussed. Agenda: 1. AJ's update to MTP time. Please review https://github.com/bitcoin/bitcoin/pull/21377 as AJ updated it substantially. The PR is now purely MTP based, and the state machine has been simplified. This approach is intended to be compatible with a mandatory signaling period (via a LAST_CHANCE change) and makes it easier to deploy ST on signets (irrelevant for Taproot, because it is already active on all signets). 2. Selecting between MTP and Height In the previous meeting, there was no substantial publicly discussed benefit to using MTPs over height. Since agenda item 1, there is now a tangible benefit to using MTP. The changes AJ promulgated for MTP neutralizes the argument, mostly, that MTP was easier to review. As such, the main conversation in this agenda item is around the pros/cons of height or MTP and determining if we can reach consensus on either approach. 3. Timeline Discussion In all hope, we will reach consensus around item 2. Should that occur, we can use this time to discuss a final selection on parameters, mindful of Core's process. If the meeting doesn't reach rough consensus around item 2, it seems that we may fall short on the proposed schedule from last time. In this section, we can discuss realities around scheduling. Best, Jeremy -- @JeremyRubin --000000000000470c6605bf1e2a2f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
We'll be having another meeting this Tuesda= y, as per https://lists.linuxfoundation.o= rg/pipermail/bitcoin-dev/2021-March/018699.html. If you can't make it feel free to leave a comment on any agenda item= =20 below, or if you think there are other things to be discussed.

Agenda:

1. AJ's update to MTP time.

Ple= ase review https://github.com/bitcoin/bitcoin/pull/21377 as AJ updated= it substantially.

The PR is now purely MTP based, and the state machine has been simplified.=20 This approach is intended to be compatible with a mandatory signaling=20 period (via a LAST_CHANCE change) and makes it easier to deploy ST on=20 signets (irrelevant for Taproot, because it is already active on all=20 signets).

2. Selecting between MTP and Height

In the previous meeting, there was no substantial publicly discussed=20 benefit to using MTPs over height. Since agenda item 1, there is now a=20 tangible benefit to using MTP.
The changes AJ promulgated for MTP neutralizes the argument, mostly, that=20 MTP was easier to review. As such, the main conversation in this agenda=20 item is around the pros/cons of height or MTP and determining if we can=20 reach consensus on either approach.

3. Timeline Discussion
In all hope, we will reach consensus around item 2. Should that occur, we=20 can use this time to discuss a final selection on parameters, mindful of Core's process.

If the meeting doesn't reach rough consensus around item 2, it seems that= =20 we may fall short on the proposed schedule from last time. In this=20 section, we can discuss realities around scheduling.


=
Best,

Jeremy



--000000000000470c6605bf1e2a2f--