diff options
| author | Jeremy <jlrubin@mit.edu> | 2021-03-15 12:14:02 -0700 |
|---|---|---|
| committer | bitcoindev <bitcoindev@gnusha.org> | 2021-03-15 19:14:17 +0000 |
| commit | 9276668ffa3abdf604c04817e21f32da6159fec5 (patch) | |
| tree | 2d1ddcf8a783fe1b330ae4f69e2c789893d6b428 | |
| parent | 1fa3dd8476b0f5afcce722aa46eb5f73dbc9d5ef (diff) | |
| download | pi-bitcoindev-9276668ffa3abdf604c04817e21f32da6159fec5.tar.gz pi-bitcoindev-9276668ffa3abdf604c04817e21f32da6159fec5.zip | |
Re: [bitcoin-dev] Taproot activation meeting on IRC - Tuesday 16th March 19:00 UTC
| -rw-r--r-- | eb/7a5d25ed1286f42e2f6668405ae49bc6e44013 | 256 |
1 files changed, 256 insertions, 0 deletions
diff --git a/eb/7a5d25ed1286f42e2f6668405ae49bc6e44013 b/eb/7a5d25ed1286f42e2f6668405ae49bc6e44013 new file mode 100644 index 000000000..23be3df63 --- /dev/null +++ b/eb/7a5d25ed1286f42e2f6668405ae49bc6e44013 @@ -0,0 +1,256 @@ +Return-Path: <jlrubin@mit.edu> +Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137]) + by lists.linuxfoundation.org (Postfix) with ESMTP id 294FEC0001 + for <bitcoin-dev@lists.linuxfoundation.org>; + Mon, 15 Mar 2021 19:14:17 +0000 (UTC) +Received: from localhost (localhost [127.0.0.1]) + by smtp4.osuosl.org (Postfix) with ESMTP id 0406645AEB + for <bitcoin-dev@lists.linuxfoundation.org>; + Mon, 15 Mar 2021 19:14:17 +0000 (UTC) +X-Virus-Scanned: amavisd-new at osuosl.org +X-Spam-Flag: NO +X-Spam-Score: -4.198 +X-Spam-Level: +X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 + tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, + RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 5vVQNRw6JeeR + for <bitcoin-dev@lists.linuxfoundation.org>; + Mon, 15 Mar 2021 19:14:15 +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 39F644571A + for <bitcoin-dev@lists.linuxfoundation.org>; + Mon, 15 Mar 2021 19:14:15 +0000 (UTC) +Received: from mail-il1-f179.google.com (mail-il1-f179.google.com + [209.85.166.179]) (authenticated bits=0) + (User authenticated as jlrubin@ATHENA.MIT.EDU) + by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 12FJEDNa031726 + (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT) + for <bitcoin-dev@lists.linuxfoundation.org>; Mon, 15 Mar 2021 15:14:13 -0400 +Received: by mail-il1-f179.google.com with SMTP id e7so10414223ile.7 + for <bitcoin-dev@lists.linuxfoundation.org>; + Mon, 15 Mar 2021 12:14:13 -0700 (PDT) +X-Gm-Message-State: AOAM530YGv0dBLNvI46gy2gHjh3yPOBnoHULI8ARCa+tYz+TuJc5KEJz + cfkVhwtHUjekbjK2CgnkbbV0SSqTqSl8TYU7yUA= +X-Google-Smtp-Source: ABdhPJxZ+7AO62+wh94/daDTOBcrMYNQRUNQUkCj5EX4lTfWFKlTLhQGSBCIm+VTzMsCACBmhQ+mcBP8saihNrg1wVM= +X-Received: by 2002:a05:6e02:58b:: with SMTP id + c11mr855473ils.49.1615835652851; + Mon, 15 Mar 2021 12:14:12 -0700 (PDT) +MIME-Version: 1.0 +References: <202103151720.04687.luke@dashjr.org> +In-Reply-To: <202103151720.04687.luke@dashjr.org> +From: Jeremy <jlrubin@mit.edu> +Date: Mon, 15 Mar 2021 12:14:02 -0700 +X-Gmail-Original-Message-ID: <CAD5xwhginOaKomLnFML77JpGyd3hMRe2+Ep=ZGbVaa2yRj_eKw@mail.gmail.com> +Message-ID: <CAD5xwhginOaKomLnFML77JpGyd3hMRe2+Ep=ZGbVaa2yRj_eKw@mail.gmail.com> +To: Luke Dashjr <luke@dashjr.org>, + Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org> +Content-Type: multipart/alternative; boundary="0000000000001a8d9d05bd980ed5" +Subject: Re: [bitcoin-dev] Taproot activation meeting on IRC - Tuesday 16th + March 19:00 UTC +X-BeenThere: bitcoin-dev@lists.linuxfoundation.org +X-Mailman-Version: 2.1.15 +Precedence: list +List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org> +List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, + <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe> +List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/> +List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org> +List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help> +List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, + <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe> +X-List-Received-Date: Mon, 15 Mar 2021 19:14:17 -0000 + +--0000000000001a8d9d05bd980ed5 +Content-Type: text/plain; charset="UTF-8" + +Please announce such meetings with more than ~24 hours notice -- this has +happened several times and while I recognize the pace of development on +this issue I think that slotting a consensus meeting with less than 24 +hours is inappropriate. + +I think we should proactively postpone it a week so that there isn't an +arbitrary "too low turnout" measure and instead anyone who really wants to +be present for the meeting can plan to be. + +So as not to lose momentum on having a discussion, I propose to plan to +hold a general discussion tomorrow at that time and a meeting (with the +intent of resolving issues in a more binding way) next week. It may be a +good idea to hold the time slot every other week for the next while so that +we can avoid this 24 hour thing altogether. + +It sucks to lose another week but a precedent of 24 hour notice meetings +for non urgent changes is very negative. + +(This isn't any comment on if ST is OK or not -- the schedules proposed for +ST thus far seem acceptable to me) + +Best, + +Jeremy +-- +@JeremyRubin <https://twitter.com/JeremyRubin> +<https://twitter.com/JeremyRubin> + + +On Mon, Mar 15, 2021 at 10:20 AM Luke Dashjr via bitcoin-dev < +bitcoin-dev@lists.linuxfoundation.org> wrote: + +> At the previous meeting, there was consensus for BIP8 activation +> parameters +> except for LOT, assuming a release around this time. Since then, a release +> has not occurred, and the new idea of Speedy Trial has been proposed to +> preempt the original/main activation plan. +> +> It's probably a good idea to meet up again to discuss these things and +> adjust +> accordingly. +> +> Agenda: +> +> - Speedy Trial: Can we get a comparable consensus on the proposal? +> (Note: current draft conflicts with original plan timeline) +> +> - Main activation, post ST: Moving startheight (and timeoutheight?) later +> is probably a good idea at this point, both because too little progress +> has +> been made on it, and to avoid the conflict with the current ST draft. +> +> - Making progress: To date, too few people have been involved in +> materialising +> the main activation plan. If it's going to move forward, more people +> need to +> get actively involved. This should not wait for ST to complete, unless we +> want another 4-5 month slip of the timeline. +> +> This meeting is tentatively scheduled for *tomorrow*, March 16th at the +> usual +> time of 19:00 UTC, in freenode's ##Taproot-activation IRC channel. If +> turnout +> is too low, we can postpone it a week, but it'd be nice to get things +> resolved and moving sooner. +> +> As a reminder, the channel is also open for ongoing discussion 24/7, and +> there +> is a web chat client here: +> +> https://webchat.freenode.net/?channel=##taproot-activation +> +> Luke +> _______________________________________________ +> bitcoin-dev mailing list +> bitcoin-dev@lists.linuxfoundation.org +> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev +> + +--0000000000001a8d9d05bd980ed5 +Content-Type: text/html; charset="UTF-8" +Content-Transfer-Encoding: quoted-printable + +<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:arial,he= +lvetica,sans-serif;font-size:small;color:#000000">Please announce such meet= +ings with more than ~24 hours notice -- this has happened several times and= + while I recognize the pace of development on this issue I think that slott= +ing a consensus meeting with less than 24 hours is inappropriate.</div><div= + class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;fo= +nt-size:small;color:#000000"><br></div><div class=3D"gmail_default" style= +=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:#000000">I= + think we should proactively postpone it a week so that there isn't an = +arbitrary "too low turnout" measure and instead anyone who really= + wants to be present for the meeting can plan to be.</div><div class=3D"gma= +il_default" style=3D"font-family:arial,helvetica,sans-serif;font-size:small= +;color:#000000"><br></div><div class=3D"gmail_default" style=3D"font-family= +:arial,helvetica,sans-serif;font-size:small;color:#000000">So as not to los= +e momentum on having a discussion, I propose to plan to hold a general disc= +ussion tomorrow at that time and a meeting (with the intent of resolving is= +sues in a more binding way) next week. It may be a good idea to hold the ti= +me slot every other week for the next while so that we can avoid this 24 ho= +ur thing altogether.</div><div class=3D"gmail_default" style=3D"font-family= +:arial,helvetica,sans-serif;font-size:small;color:#000000"><br></div><div c= +lass=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;font= +-size:small;color:#000000">It sucks to lose another week but a precedent of= + 24 hour notice meetings for non urgent changes is very negative.<br></div>= +<div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-seri= +f;font-size:small;color:#000000"><br></div><div class=3D"gmail_default" sty= +le=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:#000000"= +>(This isn't any comment on if ST is OK or not -- the schedules propose= +d for ST thus far seem acceptable to me)<br></div><div class=3D"gmail_defau= +lt" style=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:#= +000000"><br></div><div class=3D"gmail_default" style=3D"font-family:arial,h= +elvetica,sans-serif;font-size:small;color:#000000">Best,</div><div class=3D= +"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;font-size:s= +mall;color:#000000"><br></div><div class=3D"gmail_default" style=3D"font-fa= +mily:arial,helvetica,sans-serif;font-size:small;color:#000000">Jeremy<br cl= +ear=3D"all"></div><div><div dir=3D"ltr" class=3D"gmail_signature" data-smar= +tmail=3D"gmail_signature"><div dir=3D"ltr">--<br><a href=3D"https://twitter= +.com/JeremyRubin" target=3D"_blank">@JeremyRubin</a><a href=3D"https://twit= +ter.com/JeremyRubin" target=3D"_blank"></a></div></div></div><br></div><br>= +<div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Ma= +r 15, 2021 at 10:20 AM Luke Dashjr via bitcoin-dev <<a href=3D"mailto:bi= +tcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org<= +/a>> wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0= +px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">A= +t the previous meeting, there was consensus for BIP8 activation parameters = +<br> +except for LOT, assuming a release around this time. Since then, a release = +<br> +has not occurred, and the new idea of Speedy Trial has been proposed to <br= +> +preempt the original/main activation plan.<br> +<br> +It's probably a good idea to meet up again to discuss these things and = +adjust <br> +accordingly.<br> +<br> +Agenda:<br> +<br> +- Speedy Trial: Can we get a comparable consensus on the proposal?<br> +=C2=A0 (Note: current draft conflicts with original plan timeline)<br> +<br> +- Main activation, post ST: Moving startheight (and timeoutheight?) later<b= +r> +=C2=A0 is probably a good idea at this point, both because too little progr= +ess has<br> +=C2=A0 been made on it, and to avoid the conflict with the current ST draft= +.<br> +<br> +- Making progress: To date, too few people have been involved in materialis= +ing<br> +=C2=A0 the main activation plan. If it's going to move forward, more pe= +ople need to<br> +=C2=A0 get actively involved. This should not wait for ST to complete, unle= +ss we<br> +=C2=A0 want another 4-5 month slip of the timeline.<br> +<br> +This meeting is tentatively scheduled for *tomorrow*, March 16th at the usu= +al <br> +time of 19:00 UTC, in freenode's ##Taproot-activation IRC channel. If t= +urnout <br> +is too low, we can postpone it a week, but it'd be nice to get things <= +br> +resolved and moving sooner.<br> +<br> +As a reminder, the channel is also open for ongoing discussion 24/7, and th= +ere <br> +is a web chat client here:<br> +<br> +<a href=3D"https://webchat.freenode.net/?channel=3D#%23taproot-activation" = +rel=3D"noreferrer" target=3D"_blank">https://webchat.freenode.net/?channel= +=3D##taproot-activation</a><br> +<br> +Luke<br> +_______________________________________________<br> +bitcoin-dev mailing list<br> +<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">= +bitcoin-dev@lists.linuxfoundation.org</a><br> +<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" = +rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail= +man/listinfo/bitcoin-dev</a><br> +</blockquote></div> + +--0000000000001a8d9d05bd980ed5-- + |