path: root/11/24bb32fde54aecb87bb7486cb1e8afc8119b77

Return-Path: <jlrubin@mit.edu>
Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 56D9CC000A
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed,  7 Apr 2021 00:02:51 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp3.osuosl.org (Postfix) with ESMTP id 36EB660662
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed,  7 Apr 2021 00:02:51 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.2
X-Spam-Level: 
X-Spam-Status: No, score=-1.2 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_DOTEDU_SUSP_URI=2.999,
 RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001]
 autolearn=no autolearn_force=no
Received: from smtp3.osuosl.org ([127.0.0.1])
 by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id cAG6lRGhXQQD
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed,  7 Apr 2021 00:02:49 +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 smtp3.osuosl.org (Postfix) with ESMTPS id 5748B6062F
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed,  7 Apr 2021 00:02:49 +0000 (UTC)
Received: from mail-io1-f42.google.com (mail-io1-f42.google.com
 [209.85.166.42]) (authenticated bits=0)
 (User authenticated as jlrubin@ATHENA.MIT.EDU)
 by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 13702lOQ010413
 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT)
 for <bitcoin-dev@lists.linuxfoundation.org>; Tue, 6 Apr 2021 20:02:47 -0400
Received: by mail-io1-f42.google.com with SMTP id j26so12263270iog.13
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Tue, 06 Apr 2021 17:02:47 -0700 (PDT)
X-Gm-Message-State: AOAM5317QDOlxPTGDghuM5AbQPRRpaNDl5ousrxW/zbqY+ORd2y6GUkY
 kneofM0APFdwrg0V66deVLx+0IjqFxIvl2XB/lU=
X-Google-Smtp-Source: ABdhPJzhDvsm3zx5fyVzfl6oaVAW8au3qdtEL9WV/DMspEGeLdLAAabZGq637AspOtjDgwmURxkeKCRbi6RsfMORDhM=
X-Received: by 2002:a05:6638:391:: with SMTP id
 y17mr679864jap.21.1617753767056; 
 Tue, 06 Apr 2021 17:02:47 -0700 (PDT)
MIME-Version: 1.0
References: <CAD5xwhiofHqRkzgDKAW5yqecju0PLj9AUUn1FngwFVmLM5Jzfg@mail.gmail.com>
In-Reply-To: <CAD5xwhiofHqRkzgDKAW5yqecju0PLj9AUUn1FngwFVmLM5Jzfg@mail.gmail.com>
From: Jeremy <jlrubin@mit.edu>
Date: Tue, 6 Apr 2021 17:02:35 -0700
X-Gmail-Original-Message-ID: <CAD5xwhidWVKBDFAwiJfFh+vQj6maG6Rq3_oaSTJ9JW=OXvodzA@mail.gmail.com>
Message-ID: <CAD5xwhidWVKBDFAwiJfFh+vQj6maG6Rq3_oaSTJ9JW=OXvodzA@mail.gmail.com>
To: Jeremy <jlrubin@mit.edu>
Content-Type: multipart/alternative; boundary="0000000000009e98cb05bf56a6f5"
Cc: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Taproot Activation Meeting Notes,
	April 6th: The CoinFlip
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: Wed, 07 Apr 2021 00:02:51 -0000

--0000000000009e98cb05bf56a6f5
Content-Type: text/plain; charset="UTF-8"

Update: the coin has flipped in favor of MTP

https://blockstream.info/block/00000000000000000000a6bcbf09849fe895b5d18ed884e8d558a57fc4f5e95c


Further, there seems to be some agreement between Andrew and AJ w.r.t.
reverting one of the changes AJ made recently (
https://github.com/bitcoin/bitcoin/pull/21377#issuecomment-814494847),
resolving some of the contention between them for a MTP-based ST.

As such, I'm personally confident that if you want to spend your time
reviewing #21377, it has a very decent chance of accumulating sufficient
review and support from the community to be considered for a release in
accordance to the schedule from the last meeting. The changes in line with
Andrew and AJ's compromise are yet to be implemented, but they do not seem
to be complicated so you can probably expect AJ will implement and offer
them for review shortly (AJ if you're going on spring break let us know and
we can pick it up...).

Thanks to everyone and especially thanks to AJ and Andrew for all the hard
work they have put in preparing and evaluating these ideas. To outside
looking in, it might seem like there is contention between the two, but
they've been working together closely the whole time reviewing each other's
PRs and making tools and tests that make the whole thing safer anyways.
Let's all take a note from their book!

Best,

Jeremy

--
@JeremyRubin <https://twitter.com/JeremyRubin>
<https://twitter.com/JeremyRubin>


On Tue, Apr 6, 2021 at 2:31 PM Jeremy <jlrubin@mit.edu> wrote:

> Bitcoin Developers,
>
> The second fortnightly taproot activation meeting has just concluded.
> Below are my notes:
>
> 1) On AJ's mods to MTP
>    - luke-jr is still NACK any MTP related thing
>    - It is generally uncontested that the Mods are fine; that it should be
> LOT (via LAST_CHANCE) compatible
>    - it does make MTP a bit harder to review, but not unacceptably so
> 2) On selecting between MTP and Height
>    - There are some benefits to MTPs
>    - There are some benefits to Heights
>    - Both are technically probably OK to use for Taproot
>    - Both about as hard/easy to review (some think height has fewer edge
> conditions)
>    - AJ and Andrew Chow are going to see if they can unify approaches
> 3) Timeline + CoinFlip
>    - Many present at the meeting preferred to work together to compromise
> and reach consensus to stick to the timeline from the last meeting over
> either height or MTP.
>    - as such a coinflip is being run via `bitcoin-cli getblockhash
> $((678059+20)) | cut -b64 | grep -q '[02468ace]' && echo MTP || echo
> height` (that's about 13 blocks from writing).
>    - If it comes up MTP, contributors mentioned below will work towards
> moving MTP forwards.
>    - If it comes up height, contributors mentioned below will work towards
> moving height forwards.
>    - You can pre-commit to following this path by responding in the next
> hour or so, or also choose to abide by it async
>    - If in the next day or so, AJ and Andrew Chow reach a compromise
> between approaches that is compatible with the timeline of getting to a RC1
> with deployment, then that can be considered on its merits in preference of
> either of the existing approaches.
>     - If this approach fails at helping move towards consensus on an
> approach, then we will have to push back the timeline most likely for a
> core release (or an emergent group will have to offer a community release)
>
> The following folks in the meeting agreed to abide by the flip:
>
> - roasbeef
> - benthecarman
> - harding
> - jonatack
> - rgrant
> - copumpkin (in DM)
> - Emcy
> - jeremyrubin
>
> There were also several folks, anonymously, who said essentially that they
> don't want to commit to a flip but if it works it works and they'd roll
> with it.
>
> As noted, if you want to +1 on to coinflip before it settles, feel free to
> do in response here or IRC. It's also fine to just abide by it after the
> fact as well.
>
> ------------------
>
> Personal comment on coin flip: A coinflip seems like an odd choice for a
> technical decision. But let me excerpt some quotes from the meeting.
>
> [4/6/21 12:26] <jeremyrubin> We are super lucky that both achow101 and aj
> are such competent developers that we have not one but two fantastic PRs to
> look at
> [4/6/21 12:26] <jeremyrubin> At the same time, we have two PRs to look at
> [4/6/21 12:28] <jeremyrubin> In this section I'd like to remind people to
> check dug-in opinions at the door, what matters here is if we can agree on
> a plan of action and get the bulk of everyone on the same page. That said,
> there are nuanced technical points to examine that favour either approach
> [4/6/21 12:28] <jeremyrubin> I think the differences between MTP and
> height are less important than working towards a single PR to review
>
> [4/6/21 13:09] <harding> I think both MTP and heights are fine for
> mainnet, so one of them having an advantage for test networks seems worth
> considering.
>
> [4/6/21 13:09] <rgrant> This topic seems to be winding down.  I'm hearing:
> that signet configuration isn't a dealbreaker but there is technical debt
> incurred if we ignore it; MTP-based activation (read: celebration parties)
> can be known weeks in advance if parameters are chosen well; and that code
> reviews matter.  Coinflip seems to be winning.
>
> [4/6/21 13:45] <jeremyrubin> people selecting coinflip because they think
> the interest in timeline outweighs any individual perceived technical
> benefit
> [4/6/21 13:45] <jeremyrubin> it's not a don't care, it's a recognition
> there are two decent proposals with different tradeoffs
> [4/6/21 13:45] <jeremyrubin> and a desire to break stalemate on it
> mutually and voluntarily
>
> [4/6/21 13:49] <copumpkin> IMO coinflip is more of an acknowledgment that
> the two CRs differ largely in shed color and that we all want the shed, and
> don't care as much about its color
> [4/6/21 13:49] <BlueMatt> what copumpkin said
> [4/6/21 13:50] <copumpkin> (not to minimize the differences between them,
> but gotta keep the big picture in mind and not die on hills that don't need
> dead people on them)
>
> We have two good options, and coinflip is people agreeing to put aside
> minute preferences on two acceptable options for the big picture. As such,
> I think that a coinflip is appropriately used in this circumstance,
> although I recognize the sentiment that some may feel it's treating
> development a little too *flippantly*.
>
> Rough consensus and running code.
>
> Best,
>
> Jeremy
>
> --
> @JeremyRubin <https://twitter.com/JeremyRubin>
> <https://twitter.com/JeremyRubin>
>

--0000000000009e98cb05bf56a6f5
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">Update: the coin has flip=
ped in favor of MTP<br></div><div class=3D"gmail_default" style=3D"font-fam=
ily:arial,helvetica,sans-serif;font-size:small;color:#000000"><br></div><di=
v class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;f=
ont-size:small;color:#000000"><a href=3D"https://blockstream.info/block/000=
00000000000000000a6bcbf09849fe895b5d18ed884e8d558a57fc4f5e95c">https://bloc=
kstream.info/block/00000000000000000000a6bcbf09849fe895b5d18ed884e8d558a57f=
c4f5e95c</a></div><div><div dir=3D"ltr" class=3D"gmail_signature" data-smar=
tmail=3D"gmail_signature"><div dir=3D"ltr"><br></div><div dir=3D"ltr"><br><=
/div><div dir=3D"ltr"><div style=3D"font-family:arial,helvetica,sans-serif;=
font-size:small;color:rgb(0,0,0)" class=3D"gmail_default">Further, there se=
ems to be some agreement between Andrew and AJ w.r.t. reverting one of the =
changes AJ made recently (<a href=3D"https://github.com/bitcoin/bitcoin/pul=
l/21377#issuecomment-814494847">https://github.com/bitcoin/bitcoin/pull/213=
77#issuecomment-814494847</a>), resolving some of the contention between th=
em for a MTP-based ST.<br></div><div style=3D"font-family:arial,helvetica,s=
ans-serif;font-size:small;color:rgb(0,0,0)" class=3D"gmail_default"><br></d=
iv><div style=3D"font-family:arial,helvetica,sans-serif;font-size:small;col=
or:rgb(0,0,0)" class=3D"gmail_default">As such, I&#39;m personally confiden=
t that if you want to spend your time reviewing #21377, it has a very decen=
t chance of accumulating sufficient review and support from the community t=
o be considered for a release in accordance to the schedule from the last m=
eeting. The changes in line with Andrew and AJ&#39;s compromise are yet to =
be implemented, but they do not seem to be complicated so you can probably =
expect AJ will  implement and offer them for review shortly (AJ if you&#39;=
re going on spring break let us know and we can pick it up...).<br></div><d=
iv style=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:rg=
b(0,0,0)" class=3D"gmail_default"><br></div><div style=3D"font-family:arial=
,helvetica,sans-serif;font-size:small;color:rgb(0,0,0)" class=3D"gmail_defa=
ult">Thanks to everyone and especially thanks to AJ and Andrew for all the =
hard work they have put in preparing and evaluating these ideas. To outside=
 looking in, it might seem like there is contention between the two, but th=
ey&#39;ve been working together closely the whole time reviewing each other=
&#39;s PRs and making tools and tests that make the whole thing safer anywa=
ys. Let&#39;s all take a note from their book!</div><div style=3D"font-fami=
ly:arial,helvetica,sans-serif;font-size:small;color:rgb(0,0,0)" class=3D"gm=
ail_default"><br></div><div style=3D"font-family:arial,helvetica,sans-serif=
;font-size:small;color:rgb(0,0,0)" class=3D"gmail_default">Best,</div><div =
style=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(0=
,0,0)" class=3D"gmail_default"><br></div><div style=3D"font-family:arial,he=
lvetica,sans-serif;font-size:small;color:rgb(0,0,0)" class=3D"gmail_default=
">Jeremy<br></div><br></div><div dir=3D"ltr">--<br><a href=3D"https://twitt=
er.com/JeremyRubin" target=3D"_blank">@JeremyRubin</a><a href=3D"https://tw=
itter.com/JeremyRubin" target=3D"_blank"></a></div></div></div><br></div><b=
r><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, =
Apr 6, 2021 at 2:31 PM Jeremy &lt;<a href=3D"mailto:jlrubin@mit.edu">jlrubi=
n@mit.edu</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-fami=
ly:arial,helvetica,sans-serif;font-size:small;color:rgb(0,0,0)">Bitcoin Dev=
elopers,</div><div class=3D"gmail_default" style=3D"font-family:arial,helve=
tica,sans-serif;font-size:small;color:rgb(0,0,0)"><br></div><div class=3D"g=
mail_default" style=3D"font-family:arial,helvetica,sans-serif;font-size:sma=
ll;color:rgb(0,0,0)">The second fortnightly taproot activation meeting has =
just concluded. Below are my notes:<br></div><div class=3D"gmail_default" s=
tyle=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(0,=
0,0)"><br></div><div class=3D"gmail_default" style=3D"font-family:arial,hel=
vetica,sans-serif;font-size:small;color:rgb(0,0,0)">1) On AJ&#39;s mods to =
MTP</div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,=
sans-serif;font-size:small;color:rgb(0,0,0)">=C2=A0=C2=A0 - luke-jr is stil=
l NACK any MTP related thing</div><div class=3D"gmail_default" style=3D"fon=
t-family:arial,helvetica,sans-serif;font-size:small;color:rgb(0,0,0)">=C2=
=A0=C2=A0 - It is generally uncontested that the Mods are fine; that it sho=
uld be LOT (via LAST_CHANCE) compatible</div><div class=3D"gmail_default" s=
tyle=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(0,=
0,0)">=C2=A0=C2=A0 - it does make MTP a bit harder to review, but not unacc=
eptably so</div><div class=3D"gmail_default" style=3D"font-family:arial,hel=
vetica,sans-serif;font-size:small;color:rgb(0,0,0)">2) On selecting between=
 MTP and Height</div><div class=3D"gmail_default" style=3D"font-family:aria=
l,helvetica,sans-serif;font-size:small;color:rgb(0,0,0)">=C2=A0=C2=A0 - The=
re are some benefits to MTPs</div><div class=3D"gmail_default" style=3D"fon=
t-family:arial,helvetica,sans-serif;font-size:small;color:rgb(0,0,0)">=C2=
=A0=C2=A0 - There are some benefits to Heights</div><div class=3D"gmail_def=
ault" style=3D"font-family:arial,helvetica,sans-serif;font-size:small;color=
:rgb(0,0,0)">=C2=A0=C2=A0 - Both are technically probably OK to use for Tap=
root</div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica=
,sans-serif;font-size:small;color:rgb(0,0,0)">=C2=A0=C2=A0 - Both about as =
hard/easy to review (some think height has fewer edge conditions)<br></div>=
<div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-seri=
f;font-size:small;color:rgb(0,0,0)">=C2=A0=C2=A0 - AJ and Andrew Chow are g=
oing to see if they can unify approaches<br></div><div class=3D"gmail_defau=
lt" style=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:r=
gb(0,0,0)">3) Timeline + CoinFlip</div><div class=3D"gmail_default" style=
=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(0,0,0)=
">=C2=A0=C2=A0 - Many present at the meeting preferred to work together to =
compromise and reach consensus to stick to the timeline from the last meeti=
ng over either height or MTP.</div><div class=3D"gmail_default" style=3D"fo=
nt-family:arial,helvetica,sans-serif;font-size:small;color:rgb(0,0,0)">=C2=
=A0=C2=A0 - as such a coinflip is being run via `bitcoin-cli getblockhash $=
((678059+20)) | cut -b64 | grep -q &#39;[02468ace]&#39; &amp;&amp; echo MTP=
 || echo height` (that&#39;s about 13 blocks from writing).</div><div class=
=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;font-siz=
e:small;color:rgb(0,0,0)">=C2=A0=C2=A0 - If it comes up MTP, contributors m=
entioned below will work towards moving MTP forwards.</div><div class=3D"gm=
ail_default" style=3D"font-family:arial,helvetica,sans-serif;font-size:smal=
l;color:rgb(0,0,0)">=C2=A0=C2=A0 - If it comes up height, contributors ment=
ioned below will work towards moving height forwards.</div><div class=3D"gm=
ail_default" style=3D"font-family:arial,helvetica,sans-serif;font-size:smal=
l;color:rgb(0,0,0)">=C2=A0=C2=A0 - You can pre-commit to following this pat=
h by responding in the next hour or so, or also choose to abide by it async=
</div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,san=
s-serif;font-size:small;color:rgb(0,0,0)">=C2=A0=C2=A0 - If in the next day=
 or so, AJ and Andrew Chow reach a compromise between approaches that is co=
mpatible with the timeline of getting to a RC1 with deployment, then that c=
an be considered on its merits in preference of either of the existing appr=
oaches.</div><div class=3D"gmail_default" style=3D"font-family:arial,helvet=
ica,sans-serif;font-size:small;color:rgb(0,0,0)">=C2=A0=C2=A0=C2=A0 - If th=
is approach fails at helping move towards consensus on an approach, then we=
 will have to push back the timeline most likely for a core release (or an =
emergent group will have to offer a community release)</div><div class=3D"g=
mail_default" style=3D"font-family:arial,helvetica,sans-serif;font-size:sma=
ll;color:rgb(0,0,0)"><br></div><div class=3D"gmail_default" style=3D"font-f=
amily:arial,helvetica,sans-serif;font-size:small;color:rgb(0,0,0)">The foll=
owing folks in the meeting agreed to abide by the flip:</div><div class=3D"=
gmail_default" style=3D"font-family:arial,helvetica,sans-serif;font-size:sm=
all;color:rgb(0,0,0)"><br></div><div class=3D"gmail_default" style=3D"font-=
family:arial,helvetica,sans-serif;font-size:small;color:rgb(0,0,0)">- roasb=
eef</div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,=
sans-serif;font-size:small;color:rgb(0,0,0)">- benthecarman</div><div class=
=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;font-siz=
e:small;color:rgb(0,0,0)"></div><div class=3D"gmail_default" style=3D"font-=
family:arial,helvetica,sans-serif;font-size:small;color:rgb(0,0,0)">- hardi=
ng</div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,s=
ans-serif;font-size:small;color:rgb(0,0,0)">- jonatack</div><div class=3D"g=
mail_default" style=3D"font-family:arial,helvetica,sans-serif;font-size:sma=
ll;color:rgb(0,0,0)">- rgrant</div><div class=3D"gmail_default" style=3D"fo=
nt-family:arial,helvetica,sans-serif;font-size:small;color:rgb(0,0,0)">- co=
pumpkin (in DM)</div><div class=3D"gmail_default" style=3D"font-family:aria=
l,helvetica,sans-serif;font-size:small;color:rgb(0,0,0)">- Emcy<br></div><d=
iv class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;=
font-size:small;color:rgb(0,0,0)">- jeremyrubin</div><div class=3D"gmail_de=
fault" style=3D"font-family:arial,helvetica,sans-serif;font-size:small;colo=
r:rgb(0,0,0)"><br></div><div class=3D"gmail_default" style=3D"font-family:a=
rial,helvetica,sans-serif;font-size:small;color:rgb(0,0,0)">There were also=
 several folks, anonymously, who said essentially that they don&#39;t want =
to commit to a flip but if it works it works and they&#39;d roll with it.</=
div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-=
serif;font-size:small;color:rgb(0,0,0)"><br></div><div class=3D"gmail_defau=
lt" style=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:r=
gb(0,0,0)">As noted, if you want to +1 on to coinflip before it settles, fe=
el free to do in response here or IRC. It&#39;s also fine to just abide by =
it after the fact as well.<br></div><div class=3D"gmail_default" style=3D"f=
ont-family:arial,helvetica,sans-serif;font-size:small;color:rgb(0,0,0)"><br=
></div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sa=
ns-serif;font-size:small;color:rgb(0,0,0)">------------------</div><div cla=
ss=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;font-s=
ize:small;color:rgb(0,0,0)"><br></div><div class=3D"gmail_default" style=3D=
"font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(0,0,0)">P=
ersonal comment on coin flip: A coinflip seems like an odd choice for a tec=
hnical decision. But let me excerpt some quotes from the meeting.<br></div>=
<div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-seri=
f;font-size:small;color:rgb(0,0,0)"><br></div><div class=3D"gmail_default" =
style=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(0=
,0,0)">[4/6/21 12:26] &lt;jeremyrubin&gt; We are super lucky that both acho=
w101 and aj are such competent developers that we have not one but two fant=
astic PRs to look at</div><div class=3D"gmail_default" style=3D"font-family=
:arial,helvetica,sans-serif;font-size:small;color:rgb(0,0,0)">[4/6/21 12:26=
] &lt;jeremyrubin&gt; At the same time, we have two PRs to look at</div><di=
v class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;f=
ont-size:small;color:rgb(0,0,0)">[4/6/21 12:28] &lt;jeremyrubin&gt; In this=
 section I&#39;d like to remind people to check dug-in opinions at the door=
, what matters here is if we can agree on a plan of action and get the bulk=
 of everyone on the same page. That said, there are nuanced technical point=
s to examine that favour either approach<br>[4/6/21 12:28] &lt;jeremyrubin&=
gt; I think the differences between MTP and height are less important than =
working towards a single PR to review</div><div class=3D"gmail_default" sty=
le=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(0,0,=
0)"><br></div><div class=3D"gmail_default" style=3D"font-family:arial,helve=
tica,sans-serif;font-size:small;color:rgb(0,0,0)">[4/6/21 13:09] &lt;hardin=
g&gt; I think both MTP and heights are fine for mainnet, so one of them hav=
ing an advantage for test networks seems worth considering.</div><div class=
=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;font-siz=
e:small;color:rgb(0,0,0)"><br></div><div class=3D"gmail_default" style=3D"f=
ont-family:arial,helvetica,sans-serif;font-size:small;color:rgb(0,0,0)">[4/=
6/21 13:09] &lt;rgrant&gt; This topic seems to be winding down.=C2=A0 I&#39=
;m hearing: that signet configuration isn&#39;t a dealbreaker but there is =
technical debt incurred if we ignore it; MTP-based activation (read: celebr=
ation parties) can be known weeks in advance if parameters are chosen well;=
 and that code reviews matter.=C2=A0 Coinflip seems to be winning.<br></div=
><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-ser=
if;font-size:small;color:rgb(0,0,0)"><br></div><div class=3D"gmail_default"=
 style=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(=
0,0,0)">[4/6/21 13:45] &lt;jeremyrubin&gt; people selecting coinflip becaus=
e they think the interest in timeline outweighs any individual perceived te=
chnical benefit<br>[4/6/21 13:45] &lt;jeremyrubin&gt; it&#39;s not a don&#3=
9;t care, it&#39;s a recognition there are two decent proposals with differ=
ent tradeoffs<br>[4/6/21 13:45] &lt;jeremyrubin&gt; and a desire to break s=
talemate on it mutually and voluntarily </div><div class=3D"gmail_default" =
style=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(0=
,0,0)"><br></div><div class=3D"gmail_default" style=3D"font-family:arial,he=
lvetica,sans-serif;font-size:small;color:rgb(0,0,0)">[4/6/21 13:49] &lt;cop=
umpkin&gt; IMO coinflip is more of an acknowledgment that the two CRs diffe=
r largely in shed color and that we all want the shed, and don&#39;t care a=
s much about its color<br></div><div class=3D"gmail_default" style=3D"font-=
family:arial,helvetica,sans-serif;font-size:small;color:rgb(0,0,0)">[4/6/21=
 13:49] &lt;BlueMatt&gt; what copumpkin said<br></div><div class=3D"gmail_d=
efault" style=3D"font-family:arial,helvetica,sans-serif;font-size:small;col=
or:rgb(0,0,0)">[4/6/21 13:50] &lt;copumpkin&gt; (not to minimize the differ=
ences between them, but gotta keep the big picture in mind and not die on h=
ills that don&#39;t need dead people on them)</div><div class=3D"gmail_defa=
ult" style=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:=
rgb(0,0,0)"><br></div><div class=3D"gmail_default" style=3D"font-family:ari=
al,helvetica,sans-serif;font-size:small;color:rgb(0,0,0)">We have two good =
options, and coinflip is people agreeing to put aside minute preferences on=
 two acceptable options for the big picture. As such, I think that a coinfl=
ip is appropriately used in this circumstance, although I recognize the sen=
timent that some may feel it&#39;s treating development a little too <i>fli=
ppantly</i>.<br></div><div class=3D"gmail_default" style=3D"font-family:ari=
al,helvetica,sans-serif;font-size:small;color:rgb(0,0,0)"><br></div><div cl=
ass=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;font-=
size:small;color:rgb(0,0,0)">Rough consensus and running code.<br></div><di=
v class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif;f=
ont-size:small;color:rgb(0,0,0)"><br></div><div class=3D"gmail_default" sty=
le=3D"font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(0,0,=
0)">Best,</div><div class=3D"gmail_default" style=3D"font-family:arial,helv=
etica,sans-serif;font-size:small;color:rgb(0,0,0)"><br></div><div class=3D"=
gmail_default" style=3D"font-family:arial,helvetica,sans-serif;font-size:sm=
all;color:rgb(0,0,0)">Jeremy<br></div><br clear=3D"all"><div><div dir=3D"lt=
r"><div dir=3D"ltr">--<br><a href=3D"https://twitter.com/JeremyRubin" targe=
t=3D"_blank">@JeremyRubin</a><a href=3D"https://twitter.com/JeremyRubin" ta=
rget=3D"_blank"></a></div></div></div></div>
</blockquote></div>

--0000000000009e98cb05bf56a6f5--