From: "Russell O'Connor" <roconnor@blockstream.io>
To: Anthony Towns <aj@erisian.com.au>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Schnorr and taproot (etc) upgrade
Date: Sat, 15 Dec 2018 18:38:46 -0500 [thread overview]
Message-ID: <CAMZUoKnSi+8W7znTNv4BcjrrTDJubDeWeJ8ynUtzs04ES2z6AQ@mail.gmail.com> (raw)
In-Reply-To: <20181214104839.ur4lde3dzncadmr4@erisian.com.au>
[-- Attachment #1: Type: text/plain, Size: 422 bytes --]
On Fri, Dec 14, 2018 at 8:39 AM Anthony Towns via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> 5. if there's exactly one, non-zero item on the stack; succeed
>
Unless it is too much bikeshedding, I'd like to propose that to succeed the
stack must be exactly empty. Script is more composable that way, removing
the need for special logic to handle top-level CHECKSIG, vs mid-level
CHECKSIGVERIFY.
[-- Attachment #2: Type: text/html, Size: 736 bytes --]
next prev parent reply other threads:[~2018-12-15 23:39 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 [this message]
2018-12-17 20:16 ` Johnson Lau
2018-12-18 3:18 ` Russell O'Connor
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=CAMZUoKnSi+8W7znTNv4BcjrrTDJubDeWeJ8ynUtzs04ES2z6AQ@mail.gmail.com \
--to=roconnor@blockstream.io \
--cc=aj@erisian.com.au \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/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