From: "Russell O'Connor" <roconnor@blockstream.io>
To: Luke Dashjr <luke@dashjr.org>
Cc: bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Segwit v2
Date: Wed, 26 Apr 2017 17:34:29 -0400 [thread overview]
Message-ID: <CAMZUoKksBu65Ln8YunvfpJOr7VTLpR148-3KxifKcLt6DX4JZg@mail.gmail.com> (raw)
In-Reply-To: <201704262001.10933.luke@dashjr.org>
[-- Attachment #1: Type: text/plain, Size: 516 bytes --]
On Wed, Apr 26, 2017 at 4:01 PM, Luke Dashjr via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> There are things scriptSig can do that witness cannot today - specifically
> add
> additional conditions under the signature. We can always obsolete scriptSig
> later, after segwit has provided an alternative way to do this.
>
I'm not sure what you are referring to here. The data in the scriptSigs
are never signed. The scriptSigs are always stripped from the transaction
before the sigHash is made.
[-- Attachment #2: Type: text/html, Size: 932 bytes --]
next prev parent reply other threads:[~2017-04-26 21:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 20:28 [bitcoin-dev] Segwit v2 Luke Dashjr
2017-04-26 8:51 ` praxeology_guy
2017-04-26 19:31 ` Johnson Lau
2017-04-26 20:01 ` Luke Dashjr
2017-04-26 20:09 ` Johnson Lau
2017-04-26 21:34 ` Russell O'Connor [this message]
2017-04-27 2:18 ` praxeology_guy
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=CAMZUoKksBu65Ln8YunvfpJOr7VTLpR148-3KxifKcLt6DX4JZg@mail.gmail.com \
--to=roconnor@blockstream.io \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=luke@dashjr.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