From: "Russell O'Connor" <roconnor@blockstream.io>
To: Johnson Lau <jl2012@xbt.hk>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Schnorr and taproot (etc) upgrade
Date: Mon, 17 Dec 2018 22:18:40 -0500 [thread overview]
Message-ID: <CAMZUoKnc+0pBCP84RoezKrNMrsm2oK4XX=U9-B0Oyo4ELdiEJA@mail.gmail.com> (raw)
In-Reply-To: <E07C0182-1656-44B0-AD2E-8EAF9552ECC1@xbt.hk>
[-- Attachment #1: Type: text/plain, Size: 772 bytes --]
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’m not sure if that would do more harm than good. For example, 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’m not
> sure.
>
> Another related thing I’d like to bikeshed is to pop the stack after
> 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.
[-- Attachment #2: Type: text/html, Size: 1339 bytes --]
next prev parent reply other threads:[~2018-12-18 3:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 10:48 [bitcoin-dev] Schnorr and taproot (etc) upgrade Anthony Towns
2018-12-15 23:38 ` Russell O'Connor
2018-12-17 20:16 ` Johnson Lau
2018-12-18 3:18 ` Russell O'Connor [this message]
2018-12-18 4:58 ` Anthony Towns
2018-12-18 10:00 ` Johnson Lau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMZUoKnc+0pBCP84RoezKrNMrsm2oK4XX=U9-B0Oyo4ELdiEJA@mail.gmail.com' \
--to=roconnor@blockstream.io \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=jl2012@xbt.hk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox