From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133]) by lists.linuxfoundation.org (Postfix) with ESMTP id 8EFAAC0001 for ; Mon, 22 Mar 2021 12:10:16 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id 8BF0D40216 for ; Mon, 22 Mar 2021 12:10:16 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.099 X-Spam-Level: X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: smtp2.osuosl.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from smtp2.osuosl.org ([127.0.0.1]) by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HFXJFOlhBH-6 for ; Mon, 22 Mar 2021 12:10:15 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 Received: from mail-oi1-x22b.google.com (mail-oi1-x22b.google.com [IPv6:2607:f8b0:4864:20::22b]) by smtp2.osuosl.org (Postfix) with ESMTPS id A19744020B for ; Mon, 22 Mar 2021 12:10:15 +0000 (UTC) Received: by mail-oi1-x22b.google.com with SMTP id f9so12781260oiw.5 for ; Mon, 22 Mar 2021 05:10:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=Em6iqLUJYqzF9e6YBXq3j+ETgCwwOBwQMTzVfU2eV9M=; b=ZiXCZkqjsmseTFGJ8mC+rPO/fP6JR3axk/Fwq30Tzp/s2x0Kl4VJ1fxJ7KfUS0L36v M+qXte53pbUI3TUXJqcW/pZZU2IcHkfRD+1eYwxbfAJd45z9tVUyuCYQNwpvxytzLneF 6cvgC9VpNubgXi2w17GSoXkaqeT86UhjfU0v6QgeokMJFcKLg75EkfhT/zgN0DkdGD2W RZ6MbxLxXPUmy54z9ERWUGRF16DXscum+PHtn1e4JaZGr4v3kNW5WDW2MsjT1hqHjSPJ E1qK2N5C8lHBZZKX3f4uH0eenPgRCrAGZJywvMrY9X26ysOrmo24jbXHhfEmFrGTP4RA WI9g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Em6iqLUJYqzF9e6YBXq3j+ETgCwwOBwQMTzVfU2eV9M=; b=spFREmTlxPRtRIKGb7w11fOETBMpU1HKbTLJVtROdF3rLucdzgYXPlNoMQMob7G19h bVNpqLOkZE/vBhN3c1/RZo1CNM0iuAhFUdP3+RLAM168RlkzqLBofRJ1a8mm5LE51iZD P4QRPfiblt/yQZmbp88fjupmR5GNOjto1A2M6ZnNjvVBFqjtTjud8BGmSBdqvA9IaC7U yPVu3xaazCIOWkuFFuk0Pn+OBtCk7wfg+6VkyiwzgFGIziN6bBN+lFCiJoi2ay+UMsQh 2sTGhMzcYpKc7pDD6coi4cm08L2o+OXD0JGK4aMiwN0Ohv8PpwOrYeO2Gyrpx1AoBlj/ pqjw== X-Gm-Message-State: AOAM533v9HsbuiIMtTO4OszMZB4bgWLHtoKljCtBuokqqeov3I0MzvkN zDbvof3liw6iswZYVE7NFEH7CuNoUcS8IrBTwzM= X-Google-Smtp-Source: ABdhPJwWa6dtanZxT0yJhhN9GHMWhQrHo3MoHTrrc/ElzmKMtBZar58dIAMwFWNI47Zh0mcgIr9cLLsHJ8ZkUrG35ns= X-Received: by 2002:a05:6808:2d5:: with SMTP id a21mr9905715oid.88.1616415014694; Mon, 22 Mar 2021 05:10:14 -0700 (PDT) MIME-Version: 1.0 From: Michael Folkson Date: Mon, 22 Mar 2021 12:10:03 +0000 Message-ID: To: jlrubin@mit.edu, Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="000000000000c2b39205be1ef20b" X-Mailman-Approved-At: Mon, 22 Mar 2021 12:30:52 +0000 Subject: Re: [bitcoin-dev] (Recurring) Taproot activation meeting on IRC - Tuesday 23rd March 19:00 UTC + every fortnight 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: Mon, 22 Mar 2021 12:10:16 -0000 --000000000000c2b39205be1ef20b Content-Type: text/plain; charset="UTF-8" Thanks for organizing this Jeremy, agenda looks great. I do think we are now at the time where Taproot activation becomes a priority for all those with a stake in Taproot activation. Although these parameters haven't yet been finalized the proposed (approximate) startheight is May 1st which is less than 6 weeks away. https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-March/018594.html Therefore I encourage everyone with a stake in Taproot activation to attend this meeting tomorrow (Tuesday 19:00 UTC) and raise any specific concerns with block height vs MTP and proposed timetables as Jeremy suggests before the meeting. Personally I think we should avoid the min activation height dragging into December. November (current proposed is November 13th) seems ideal as to avoid (admittedly Western) holidays in December and January. Other than that I think we have some (limited) wiggle room with regards to the exact timetable to ensure the optimal code is merged. -- Michael Folkson Email: michaelfolkson@gmail.com Keybase: michaelfolkson PGP: 43ED C999 9F85 1D40 EAF4 9835 92D6 0159 214C FEE3 --000000000000c2b39205be1ef20b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks for organizing this Jeremy, agenda looks great. I d= o think we are now at the time where Taproot activation becomes a priority = for all those with a stake in Taproot activation.

Although these par= ameters haven't yet been finalized the proposed (approximate) startheig= ht is May 1st which is less than 6 weeks away.

http= s://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-March/018594.html<= /a>

Therefore I encourage everyone with a stake in Taproot activatio= n to attend this meeting tomorrow (Tuesday 19:00 UTC) and raise any specifi= c concerns with block height vs MTP and proposed timetables as Jeremy sugge= sts before the meeting.

--000000000000c2b39205be1ef20b--