From: <eric@voskuil.org>
To: "'Claus Ehrenberg'" <aubergemediale@gmail.com>,
 "'Bitcoin Protocol Discussion'" <bitcoin-dev@lists.linuxfoundation.org>
References: <CAD5xwhiXE=yJFi+9aZQqMOCaiUrJ_UEvcESR3E0j2SA1RnbqmA@mail.gmail.com>
 <874kgkkpji.fsf@rustcorp.com.au>
 <CAMnpzfopMNO=73wqvXpOn9u8X4MwJArqGxODJAS4-9iFiZOd6A@mail.gmail.com>
 <87pmz6it7q.fsf@rustcorp.com.au>
 <CANPykMr_pyz7XxrXo2FfkNPmBwzMkmnL2SPw8-TmVhOtxkz=-A@mail.gmail.com>
In-Reply-To: <CANPykMr_pyz7XxrXo2FfkNPmBwzMkmnL2SPw8-TmVhOtxkz=-A@mail.gmail.com>
Date: Wed, 7 Apr 2021 08:25:22 -0700
Message-ID: <0a4c01d72bc2$39ff9560$adfec020$@voskuil.org>
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="----=_NextPart_000_0A4D_01D72B87.8DA32E60"
Thread-Index: AQJzPe3qKuVrNaRG1VQLu7l2ZCNK/AJMPCRMAVGGpXUBfKOcdQGAVwEcqTwydlA=
Content-Language: en-us
Subject: Re: [bitcoin-dev] March 23rd 2021 Taproot Activation Meeting Notes
Precedence: list

This is a multipart message in MIME format.

------=_NextPart_000_0A4D_01D72B87.8DA32E60
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

You may activate any time you want.

=20

e

=20

From: bitcoin-dev <bitcoin-dev-bounces@lists.linuxfoundation.org> On =
Behalf Of Claus Ehrenberg via bitcoin-dev
Sent: Wednesday, April 7, 2021 6:42 AM
To: Rusty Russell <rusty@rustcorp.com.au>; Bitcoin Protocol Discussion =
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] March 23rd 2021 Taproot Activation Meeting =
Notes

=20

As a user, I think it's very important for me to know if Taproot is =
eventually coming or not. So why not make it so that if _either_ miners =
_or_ users decide for Taproot, it will activate no matter what. =
Accepting a chain split is imo the fairest way to 'resolve the conflict' =
(it can't be resolved anyway).

=20

That would probably mean running ST and and UASF concurrently.

=20

The upside would be that we've got a safe date for Taproot, except =
neither users nor miners want it.

=20

Cheers,

Claus


------=_NextPart_000_0A4D_01D72B87.8DA32E60
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 15 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple style=3D'word-wrap:break-word'><div =
class=3DWordSection1><p class=3DMsoNormal>You may activate any time you =
want.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>e<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div =
style=3D'border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b>From:</b> bitcoin-dev =
&lt;bitcoin-dev-bounces@lists.linuxfoundation.org&gt; <b>On Behalf Of =
</b>Claus Ehrenberg via bitcoin-dev<br><b>Sent:</b> Wednesday, April 7, =
2021 6:42 AM<br><b>To:</b> Rusty Russell &lt;rusty@rustcorp.com.au&gt;; =
Bitcoin Protocol Discussion =
&lt;bitcoin-dev@lists.linuxfoundation.org&gt;<br><b>Subject:</b> Re: =
[bitcoin-dev] March 23rd 2021 Taproot Activation Meeting =
Notes<o:p></o:p></p></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>As a =
user, I think it's very important for me to know if Taproot is =
eventually coming or not. So why not make it so that if _either_ miners =
_or_ users decide for Taproot, it will activate no matter what. =
Accepting a chain split is imo the fairest way to 'resolve the conflict' =
(it can't be resolved anyway).<o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>That would probably mean running ST and and UASF =
concurrently.<o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>The upside would be that we've got a safe date for =
Taproot, except neither users nor miners want =
it.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Cheers,<o:p></o:p></p></div><div><p =
class=3DMsoNormal>Claus<o:p></o:p></p></div></div></div></div></body></ht=
ml>
------=_NextPart_000_0A4D_01D72B87.8DA32E60--