Return-Path: Received: from hemlock.osuosl.org (smtp2.osuosl.org [140.211.166.133]) by lists.linuxfoundation.org (Postfix) with ESMTP id 6FFD7C013A for ; Wed, 3 Feb 2021 14:25:12 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by hemlock.osuosl.org (Postfix) with ESMTP id 598C08708A for ; Wed, 3 Feb 2021 14:25:12 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from hemlock.osuosl.org ([127.0.0.1]) by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6Eka+Atqf9l6 for ; Wed, 3 Feb 2021 14:25:11 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-ot1-f52.google.com (mail-ot1-f52.google.com [209.85.210.52]) by hemlock.osuosl.org (Postfix) with ESMTPS id E7C8887035 for ; Wed, 3 Feb 2021 14:25:10 +0000 (UTC) Received: by mail-ot1-f52.google.com with SMTP id h14so17950otr.4 for ; Wed, 03 Feb 2021 06:25:10 -0800 (PST) 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=0+JanJ7Pcj46T6goNWrSt8wLsD3Vigyw9EPeiwllrM0=; b=FT08fmhTMVXH4pGOjWit/ohfIAXrJPNxu4aNhomvChBlThToZs1X1y9cuDq8YnUfP+ 3N0P/ibcXx5mTBUqRDye0vJO1qztVnNGGIeBLO5AVy5zrHxF/+yro/KyVDetmwB1razr q4cz4yPghxIkwcqUmfcfOaYL0tPlebwIS2B/9246FXSkDYAc/NslnoEGWvMRQ7cCoNwc 287eAGYUEAdxuBc8p47XRDD2fQLkwaUmJuAbcE5objHs1QiRDWP3cTqc0FKBreQeauk0 FGQZdYaOlS1T3PpWxQNlApYN7/a0uUqn7RnIqCPuQ4WkKDNoATjKG9HOwDCS7Xeo8KqS /4SQ== 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=0+JanJ7Pcj46T6goNWrSt8wLsD3Vigyw9EPeiwllrM0=; b=pJmEcCqDMVvQyLcPzUz7A3iHZvYBK7I/qJINToE7VvdFRnrJb85zLt7+EzCxrkNNeJ rjIIFmF6tf102og5sew9Uip5/OLLgGudHDaKls3Gr4RTZWZnyHxzUhQbz8RxlSEwuyz/ jyMyRCY1ujgpx9vxbie1ctnvU484uh8Gd7XJ5IpHrqSadZp9Zm2K7katEehFbt8rPc/K kBWUZQcBF8UsKLN6sk9RYjZeqhaC43+S5di93YmrfR4D7jRrp45X3Y/q4x3yFm5oHA7X eXCdeNDbXeCG66egWy8PNY3nH0+UsuXhD0cS0zjR78fO80fFM14rshPzSnOmeqQ/wQp8 W2hg== X-Gm-Message-State: AOAM533eM3t24jXDKTii86qmMbjzGfze57l+ZNzfI81pthjmCkYitycS iZXfKoltTvMdW7354W399zTknKfwp7bkdbpExMoUbUt/AaU= X-Google-Smtp-Source: ABdhPJzaM8CbJH5bNWo0Ft6SKVd2DYdTfVDM9HECP/R1GnQC1+drXeqEZ1ELE0hyNp6pt8nYOM2G7EHTGS2jAtLbuuM= X-Received: by 2002:a05:6830:139a:: with SMTP id d26mr2178200otq.305.1612362309790; Wed, 03 Feb 2021 06:25:09 -0800 (PST) MIME-Version: 1.0 From: Michael Folkson Date: Wed, 3 Feb 2021 14:24:59 +0000 Message-ID: To: bitcoin-dev@lists.linuxfoundation.org Content-Type: multipart/alternative; boundary="000000000000b96dd705ba6f5a72" X-Mailman-Approved-At: Wed, 03 Feb 2021 14:43:33 +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, 03 Feb 2021 14:25:12 -0000 --000000000000b96dd705ba6f5a72 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Yesterday (February 2nd) we held a relatively unstructured meeting on Taproot activation on IRC which was open to all. The conversation log is here: http://gnusha.org/taproot-activation/2021-02-02.log The meeting was previously announced here: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-January/018370= .html I will summarize what was discussed as best I can. Please revert to the conversation log if you have the time as any summary is going to be imperfect. Any errors or biases are my own and corrections will be gratefully accepted. I=E2=80=99ll start with Rusty Russell=E2=80=99s takeaways (many thanks to o= ur Asia Pacific representatives for joining in the middle of the night by the way) on Mastodon: 1. Unanimous support for BIP 8. RIP BIP 9. 2. Overwhelming consensus that 1 year is the correct timeout value (it=E2= =80=99s actually defined in blocks, so 26x2016 or maybe 87600). 3. Majority consensus for lockinontimeout false, though Luke Dashjr strongly opposed. 4. No decision I could see on start time, but 2 months was done for SegWit and that didn=E2=80=99t seem too objectionable. https://bitcoinhackers.org/@rusty/105664386728806153 I personally think this is a solid summary though I do want to point out it wasn=E2=80=99t only Luke that opposed lockinontimeout=3Dfalse. There were o= ther individuals who also opposed lockinontimeout=3Dfalse but at least from my reading that was the minority opinion. Luke concluded there wasn=E2=80=99t = clear consensus on it and that even if lockinontimeout=3Dfalse was eventually chosen as a Bitcoin Core default he would be running lockinontimeout=3Dtrue on his node. In terms of the PRs, the following BIP 8 PRs were merged following the meeting. https://github.com/bitcoin/bips/pull/1020 https://github.com/bitcoin/bips/pull/1021 The latter was merged due to an observation from Jonas Nick in the PR comments and during the meeting that without it nodes could end up on the wrong chain in a scenario where they run lockinontimeout=3Dtrue with most nodes running lockinontimeout=3Dfalse. The Bitcoin Core PR #19573 requires additional work from its author and further review before it can be considered for merging. I do want to thank the large number of participants for engaging in the discussion in the spirit of wanting to make progress on Taproot activation and for gracefully allowing me to interrupt them and keep the discussion on topic. The vast majority of the time this level of bluntness (and pushing away slightly off topic questions) is not desired or required in Bitcoin technical meetings. I hope those who were interrupted during this meeting will return and ask their questions now a meeting of that sheer size is over. We are in the process of attempting to organize a follow up more closely following the format of John Newbery=E2=80=99s Bitcoin Core PR review club = which will be lower level, technical and focused on the Bitcoin Core PR #19573. The Bitcoin Core PR review club is also open to all but given its more technical nature it shouldn=E2=80=99t present the same challenges as yester= day=E2=80=99s meeting. Thanks to Alejandro De La Torre for providing an update on his website ( taprootactivation.com) following the meeting. Chun Wang (co-founder of F2Pool, ~ 16 percent of global hash rate) has decided to support BIP 8(false,1 year). --=20 Michael Folkson Email: michaelfolkson@gmail.com Keybase: michaelfolkson PGP: 43ED C999 9F85 1D40 EAF4 9835 92D6 0159 214C FEE3 --000000000000b96dd705ba6f5a72 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Yesterday (February 2nd) we held a relatively u= nstructured meeting on Taproot activation on IRC which was open to all.


The conversation log is here: http://gnusha.org/taproot-ac= tivation/2021-02-02.log


The meeting was previously announced here: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-= January/018370.html


I will summarize what was discussed as best I c= an. Please revert to the conversation log if you have the time as any summa= ry is going to be imperfect. Any errors or biases are my own and correction= s will be gratefully accepted.


I=E2=80=99ll start with Rusty Russell=E2=80=99s= takeaways (many thanks to our Asia Pacific representatives for joining in = the middle of the night by the way) on Mastodon:


1. Unanimous support for BIP 8. RIP BIP 9.

2. Overwhelming consensus that 1 year is the co= rrect timeout value (it=E2=80=99s actually defined in blocks, so 26x2016 or= maybe 87600).

3. Majority consensus for lockinontimeout false= , though Luke Dashjr strongly opposed.

4. No decision I could see on start time, but 2= months was done for SegWit and that didn=E2=80=99t seem too objectionable.=


https://bitcoinhackers.org/@rusty/105664386728806153<= /p>


I personally think this is a solid summary thou= gh I do want to point out it wasn=E2=80=99t only Luke that opposed lockinon= timeout=3Dfalse. There were other individuals who also opposed lockinontime= out=3Dfalse but at least from my reading that was the minority opinion. Luk= e concluded there wasn=E2=80=99t clear consensus on it and that even if loc= kinontimeout=3Dfalse was eventually chosen as a Bitcoin Core default he wou= ld be running lockinontimeout=3Dtrue on his node.=C2=A0


In terms of the PRs, the following BIP 8 PRs we= re merged following the meeting.


https://github.com/bitcoin/bips/pull/1020


https://github.com/bitcoin/bips/pull/1021


The latter was merged due to an observation fro= m Jonas Nick in the PR comments and during the meeting that without it node= s could end up on the wrong chain in a scenario where they run lockinontime= out=3Dtrue with most nodes running lockinontimeout=3Dfalse.


The Bitcoin Core PR #19573 requires additional = work from its author and further review before it can be considered for mer= ging.


I do want to thank the large number of particip= ants for engaging in the discussion in the spirit of wanting to make progre= ss on Taproot activation and for gracefully allowing me to interrupt them a= nd keep the discussion on topic. The vast majority of the time this level o= f bluntness (and pushing away slightly off topic questions) is not desired = or required in Bitcoin technical meetings. I hope those who were interrupte= d during this meeting will return and ask their questions now a meeting of = that sheer size is over.


We are in the process of attempting to organize= a follow up more closely following the format of John Newbery=E2=80=99s Bi= tcoin Core PR review club which will be lower level, technical and focused = on the Bitcoin Core PR #19573. The Bitcoin Core PR review club is also open= to all but given its more technical nature it shouldn=E2=80=99t present th= e same challenges as yesterday=E2=80=99s meeting.


Thanks to Alejandro De La Torre for providing a= n update on his website (taprootac= tivation.com) following the meeting. Chun Wang (co-founder of F2Pool, ~= 16 percent of global hash rate) has decided to support BIP 8(false,1 year)= .


--
<= div dir=3D"ltr">
Mich= ael Folkson
Keybase: michaelfolkson
PGP: = 43ED C999 9F85 1D40 EAF4 9835 92D6 0159 214C FEE3
<= /div>
--000000000000b96dd705ba6f5a72--