Return-Path: Received: from smtp1.osuosl.org (smtp1.osuosl.org [IPv6:2605:bc80:3010::138]) by lists.linuxfoundation.org (Postfix) with ESMTP id 2EA7DC000A for ; Wed, 14 Apr 2021 11:59:12 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id 110C5834F6 for ; Wed, 14 Apr 2021 11:59:12 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: 0.601 X-Spam-Level: X-Spam-Status: No, score=0.601 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: smtp1.osuosl.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from smtp1.osuosl.org ([127.0.0.1]) by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Q2VqGedO98Z for ; Wed, 14 Apr 2021 11:59:11 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 Received: from mail-oi1-x234.google.com (mail-oi1-x234.google.com [IPv6:2607:f8b0:4864:20::234]) by smtp1.osuosl.org (Postfix) with ESMTPS id 1D33E82A72 for ; Wed, 14 Apr 2021 11:59:11 +0000 (UTC) Received: by mail-oi1-x234.google.com with SMTP id x2so20314766oiv.2 for ; Wed, 14 Apr 2021 04:59:11 -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=KvBd9vl9ZxJ2qfaOHJcFzhBDx8Plwz1+0llQ+BBF2Ns=; b=YhbDdZ2lwjd9Egvy46QwVrHl84rwYpy1oGbvAk5jtBJQUR7omJ7X5bVsqxEdx5xR+7 0auxjY6cEAgvNUzGubVr8mnr1NhhiFXlpxd1UZqR4XEdtSWzQ3ULtbLyv+jWeQ5P+QQm H0IDzOtcrzBWdwvVPx801ckxO6EK2AXqlc6rZR1v0gM/GAwr7JCMAw3a6KkQb2NFrL6F 32aLLA6g/VKOe48/Nia0piITupsyyzax8Fb4UU9PG2TGhciuTHR6MzPTnAGRdNSud/Gb UJ6PS8h01Cx0gFHLXLz8meHpjv3bl5ElDlb9PbBVW+ojnfYdvKDyIJp8OM/rfIKYXVXV 6ZFg== 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=KvBd9vl9ZxJ2qfaOHJcFzhBDx8Plwz1+0llQ+BBF2Ns=; b=XLVM7SO4n+Fw64GFlzFiSnJyqNW7Njsl2K932dVTj47+4s1v2lLpKl+aNCe35KnL7i dYLSTuQ2cWLBjIMT9zT6iX5OOi7fX7su8X0SjbeM5lQE9dSJg2yXHTUZdJZ2HdF14Sa8 jLEeli1bB2e5eybvSuykBHOQAQdzOOYzNaxYyg7el/Nc5fsNKFypK+rlPxkUl6bsAb6q XeF+CY9aPCx0RN7DQMKHJUp7WaRjCVa8opmzx5HYR4FfH/GNWT/f10V9LWhKPBjO2dDA 7zwEky04dNbhRSDhgxKEY+xZ7eR7jEs/jPMySPV+ykOJM8U/3DUp0NI3sCcUh9YgbX62 lWHA== X-Gm-Message-State: AOAM532mIKmPH1vTxWTdE6tMykM+rkJbJMsLCXffZy667i9VZ9HUTx+N ISvuAmOyLiUKROYoe+YjHKMjVGH+ffV2e69IeuaUsDFdj8U= X-Google-Smtp-Source: ABdhPJzPgUwMPrHgotege4EvJGOpOu7N8y+2zKYH1QHxd256HLms3OqxBpeIQiM3dh/pVSBCxniyzQiLF6WaXW4Wr4k= X-Received: by 2002:aca:d16:: with SMTP id 22mr1971474oin.163.1618401549857; Wed, 14 Apr 2021 04:59:09 -0700 (PDT) MIME-Version: 1.0 From: Michael Folkson Date: Wed, 14 Apr 2021 12:58:58 +0100 Message-ID: To: Bitcoin Protocol Discussion Content-Type: text/plain; charset="UTF-8" X-Mailman-Approved-At: Wed, 14 Apr 2021 12:04:28 +0000 Subject: [bitcoin-dev] Yesterday's Taproot activation meeting on IRC 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: Wed, 14 Apr 2021 11:59:12 -0000 Yesterday there was a Taproot activation meeting on the ##taproot-activation Freenode channel. The agenda was posted in advance to the mailing list by BitcoinMechanic. https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-April/018769.html The conversation log is here: http://gnusha.org/taproot-activation/2021-04-13.log Discussion focused on an alternative release to Bitcoin Core with the naming of the release not yet finalized. Some participants expressed concern of having "Bitcoin Core" in the name e.g. "Bitcoin Core + Taproot" as it would be confusing to users and give them the mistaken impression that it had been signed off by Bitcoin Core maintainers. The activation mechanism(s) for this alternative release is Speedy Trial (BIP 8, consistent use of block height) followed by BIP 8 (1 year, LOT=true). The BIP 8 (1 year, LOT=true) is only started assuming Taproot hasn't activated during the Speedy Trial deployment. Draft release notes for this alternative release are here: https://docs.google.com/document/d/1Uhn1SEDMAqQkzkPZ4B5lPTSjUFEXKPndt_oBI4eUm7A/edit?usp=sharing The GitHub repo for this alternative release is here: https://github.com/BitcoinActivation/bitcoin To compare this to the most likely activation mechanism(s) in Bitcoin Core at this point. If the Core PR #21377 is merged in its current form then the activation mechanism in Bitcoin Core will be Speedy Trial (BIP to be decided, mix of block height and MTP). The starttime and timeout will use MTP and the activation point will use block height. The Core PR #21377 is here: https://github.com/bitcoin/bitcoin/pull/21377 In addition a BIP PR for the Core release has been opened here with suggested finalized parameters: https://github.com/bitcoin/bips/pull/1104 If these plans continue as is Bitcoin Core and this alternative release won't be entirely compatible due to startheight and timeout being defined according to MTP and block height respectively. In the majority of cases they should both activate at the same block height (or not activate) but there are unlikely edge cases where one activates and one doesn't (in addition to a possible timewarp attack on MTP). The use of MTP in Speedy Trial for Bitcoin Core has been discussed extensively and reviewers' opinions are summarized here: https://github.com/bitcoin/bitcoin/pull/21377#issuecomment-818758277 From this point on I will try to stay as neutral as I can and just summarize the facts to keep this list informed but anyone can review my past mailing list posts to get my personal views if you are interested. As a reminder anyone can host a meeting on the ##taproot-activation channel. All they need to do is contact me to book a time slot and ideally post an agenda to this mailing list in advance of the meeting. That meeting host will have the ability to issue warnings and if necessary kick participants if the meeting host feels they are disrupting the meeting or diverting conversation from the agenda. -- Michael Folkson Email: michaelfolkson@gmail.com Keybase: michaelfolkson PGP: 43ED C999 9F85 1D40 EAF4 9835 92D6 0159 214C FEE3