MIME-Version: 1.0
References: <20181214104839.ur4lde3dzncadmr4@erisian.com.au>
	<CAMZUoKnSi+8W7znTNv4BcjrrTDJubDeWeJ8ynUtzs04ES2z6AQ@mail.gmail.com>
	<E07C0182-1656-44B0-AD2E-8EAF9552ECC1@xbt.hk>
In-Reply-To: <E07C0182-1656-44B0-AD2E-8EAF9552ECC1@xbt.hk>
From: "Russell O'Connor" <roconnor@blockstream.io>
Date: Mon, 17 Dec 2018 22:18:40 -0500
Message-ID: <CAMZUoKnc+0pBCP84RoezKrNMrsm2oK4XX=U9-B0Oyo4ELdiEJA@mail.gmail.com>
To: Johnson Lau <jl2012@xbt.hk>
Content-Type: multipart/alternative; boundary="0000000000005ed228057d435b29"
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Schnorr and taproot (etc) upgrade
Precedence: list

--0000000000005ed228057d435b29
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Dec 17, 2018 at 3:16 PM Johnson Lau <jl2012@xbt.hk> wrote:

>
> I proposed the same in BIP114. I wish Satoshi had designed that way.
>

Thanks.  I probably read that and internalized it and forgot you wrote it.


> But I=E2=80=99m not sure if that would do more harm than good. For exampl=
e, people
> might lose money by copying an existing script template. But they might
> also lose money in the same way as CHECKMULTISIG is disabled. So I=E2=80=
=99m not
> sure.
>
> Another related thing I=E2=80=99d like to bikeshed is to pop the stack af=
ter
> OP_CLTV and OP_CSV. The same pros and cons apply.
>

This one is almost a no-brainer I think.  Nearly every instance of OP_CSV
is followed by an OP_DROP and we'd save 1 WU per OP_CSV if we pop the stack
afterwards.

--0000000000005ed228057d435b29
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Mon=
, Dec 17, 2018 at 3:16 PM Johnson Lau &lt;<a href=3D"mailto:jl2012@xbt.hk">=
jl2012@xbt.hk</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex"><div style=3D"overflow-wrap: break-word;"><br><div>I proposed =
the same in BIP114. I wish Satoshi had designed that way. </div></div></blo=
ckquote><div><br></div><div>Thanks.=C2=A0 I probably read that and internal=
ized it and forgot you wrote it.<br></div><div>=C2=A0</div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex"><div style=3D"overflow-wrap: break-word;"=
><div>But I=E2=80=99m not sure if that would do more harm than good. For ex=
ample, people might lose money by copying an existing script template. But =
they might also lose money in the same way as CHECKMULTISIG is disabled. So=
 I=E2=80=99m not sure.</div><div><br></div><div>Another related thing I=E2=
=80=99d like to bikeshed is to pop the stack after OP_CLTV and OP_CSV. The =
same pros and cons apply.</div></div></blockquote><div><br></div><div>This =
one is almost a no-brainer I think.=C2=A0 Nearly every instance of OP_CSV i=
s followed by an OP_DROP and we&#39;d save 1 WU per OP_CSV if we pop the st=
ack afterwards. <br></div></div></div>

--0000000000005ed228057d435b29--