From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133]) by lists.linuxfoundation.org (Postfix) with ESMTP id 0E7B3C000A for ; Fri, 16 Apr 2021 12:17:12 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id E931340294 for ; Fri, 16 Apr 2021 12:17:11 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.1 X-Spam-Level: X-Spam-Status: No, score=-2.1 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, 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 iwdJsXslHM2O for ; Fri, 16 Apr 2021 12:17:11 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 Received: from mail-ot1-x32b.google.com (mail-ot1-x32b.google.com [IPv6:2607:f8b0:4864:20::32b]) by smtp2.osuosl.org (Postfix) with ESMTPS id DA8C04012F for ; Fri, 16 Apr 2021 12:17:10 +0000 (UTC) Received: by mail-ot1-x32b.google.com with SMTP id w21-20020a9d63950000b02901ce7b8c45b4so25525574otk.5 for ; Fri, 16 Apr 2021 05:17:10 -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=+K7sWNml2phlN6+3Jbm0euUJAdiw7QAW7rvs9KVzdmQ=; b=B6PVrWU/9gOF8ypVI7rNkTb6Npw1AkpfvY7/zo/Mc9KoS+FQEcfYXc9STUdhyIz3CD kE59eT9gcX+VRh4uaz9iFzM9+qAj63+Tj04ISUny8tz88Rd4p8U+Q3hs/3uzGv5d5W06 Z9MiZ6cnWIw9DFxxQfZe6IxwkSLbahZPN9UuvlFd7bTz6hnEfKS7+8BhkayQ7ELRnohf uS8u31VMNlnYmqlKuw3NzTmDVMjTn+1JV7iUwrBKunuDDsMSbUY3tUD1fHhBuovJ1sPM ZqdRPb2fP1XG7sHWHnFqDqEv9uBtYgYG6EBs0GYMNEXB6JurmqUM8rSIfjOQtextsg2v RhtA== 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=+K7sWNml2phlN6+3Jbm0euUJAdiw7QAW7rvs9KVzdmQ=; b=FAU9mkP4HFs0QEFBY1y6FrRNZ6Ah7oCR0M74DIyW87/LzqiDi+lgHb2FUV8hYNZfZD uRyIHQn4IKokvXCx3YvZYUXaZ5DberxB1U2HN1ZyU73E7Ec1Fq3mmV78bflaV/OoQu1i fG++wbbL5xnS28yhQfJ/zHlWAQTnORbDjj9phXW+fAhDV+J0py7LgQcwp6JMs6PCFPyv 2tERbYVjnb5FlZVBNB5qkJRYF3PoKsiv0eJ7MUMXVQK3287ujqztropxsmuVb5aePNn2 /YKEBlVUyvn5vUhc7smy1EthXKxnw7cT143S9aoINSchQXzBONwwkMfB7VHWC05onSPD eTFw== X-Gm-Message-State: AOAM53024ASRWKuzzSralzRQun+NjvkzBBYlSj/hdLiOaGAuD5frinRn 2tPdA09q2o7IFMG4Mc6MT+cvBBDeQblGAXi4tHYTqFCR7xU= X-Google-Smtp-Source: ABdhPJyqIcFo76I+N7puZ2rPSWuiM7W10v0d74CFZC7Jwfe84qbCiFljFeSs3NCrFjCZJVG/oLal5zO4TsQQ5SqnlGY= X-Received: by 2002:a9d:4d0d:: with SMTP id n13mr3609784otf.294.1618575429512; Fri, 16 Apr 2021 05:17:09 -0700 (PDT) MIME-Version: 1.0 From: Michael Folkson Date: Fri, 16 Apr 2021 13:16:58 +0100 Message-ID: To: Bitcoin Protocol Discussion Content-Type: text/plain; charset="UTF-8" X-Mailman-Approved-At: Fri, 16 Apr 2021 13:32:16 +0000 Subject: [bitcoin-dev] Update on Taproot activation releases 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: Fri, 16 Apr 2021 12:17:12 -0000 I discussed in the last Taproot activation meeting notes the plans for an alternative release to Bitcoin Core with the Speedy Trial activation mechanism (BIP 8, consistent use of block height) followed by a BIP 8(1 year, LOT=true). This has now been released (version 0.1) under the name "Bitcoin Core 0.21.0-based Taproot Client". The build is available from https://bitcointaproot.cc/ and the GitHub repo is here: https://github.com/BitcoinActivation/bitcoin Luke Dashjr (Bitcoin Core contributor, Bitcoin Knots, UASF) is contributing to this release but there are a number of other pseudonymous individuals contributing to it too. In my attempted neutral stance I would say that it is not as thoroughly reviewed as an upcoming Bitcoin Core release will be but if you support a consistent use of block height (BIP 8 Speedy Trial) followed by a BIP 8 (1 year, LOT=true) I would encourage you to review and test it. Of course there may well be future version releases of "Bitcoin Core 0.21.0-based Taproot Client". If you are unable to review the code yourself but you support this effort it may be worth waiting for a future version before running it or ensuring you update to the latest version when it is released. Moving onto Bitcoin Core and other alternative Bitcoin implementations. As expected Bitcoin Core is proceeding with Speedy Trial (mix of MTP and block height, BIP to be decided). If Speedy Trial fails to activate on this Core release there is no follow up activation mechanism. That is not to say there will never be one in a Core release later in the year but as it stands there is no follow up. Bitcoin Core PR 21377 has been merged and the activation parameters (Bitcoin Core PR 21686) have also been merged. As discussed in my previous email you would expect Speedy Trial to activate (or not activate) on both Bitcoin Core and Bitcoin Core 0.21.0-based Taproot Client. However, there is a small possibility it activates on one but not the other. This is due to Bitcoin Core going with a mix of MTP and block height and Bitcoin Core 0.21.0-based Taproot Client going with consistent block height. Assuming they both activate due to Speedy Trial they share the same activation block height of 709632 (approximately November 12th 2021). If Speedy Trial fails to activate Bitcoin Core 0.21.0-based Taproot Client will attempt to enforce miner signaling in November 2022 (approximately, it is defined by block height). To be clear that is November **2022**. There are of course alternative Bitcoin implementations to Bitcoin Core. Jeremy Rubin has attempted to inform the maintainers of some alternative Bitcoin implementations of the finalized activation parameters in Core: https://github.com/bitcoin/bips/pull/1104#issuecomment-820011540 At the time of writing Laolu Osuntokun (roasbeef, maintainer of btcd) has ACKed the parameters and stated "I think we'll be able to get everything reviewed+tested (likely adding signet support along the way) by November." Piotr Narewski (maintainer of Gocoin) has also notified that he's seen the parameters. In terms of future meetings on the ##taproot-activation Freenode channel there is only one meeting currently booked. That is on Tuesday April 20th at 19:00 UTC and the meeting host will be Jeremy Rubin. The mailing list has yet to receive an agenda but I suspect it will be sent at some point in advance of the meeting. As always if there are any errors or perceived bias in my attempts to inform please respond. Ideally I would like all users to be informed of the facts so they can make up their mind on what to run and what they spend time reviewing and testing. Of course tensions are running higher than normal but that is not an excuse to spread factual inaccuracies. -- Michael Folkson Email: michaelfolkson@gmail.com Keybase: michaelfolkson PGP: 43ED C999 9F85 1D40 EAF4 9835 92D6 0159 214C FEE3