From: Gregory Maxwell <greg@xiph.org>
To: Aymeric Vitte <vitteaymeric@gmail.com>
Cc: "Bitcoin Protocol Discussion"
<bitcoin-dev@lists.linuxfoundation.org>,
"Артём Литвинович" <theartlav@gmail.com>
Subject: Re: [bitcoin-dev] Why is deriving public key from the signature not used in Segwit?
Date: Wed, 24 Jan 2018 10:31:35 +0000 [thread overview]
Message-ID: <CAAS2fgTT+9DydafDfA3S1_KSDO+hDkA4sNiBmUn+2kHpf5cFag@mail.gmail.com> (raw)
In-Reply-To: <41d8ff42-106f-45b9-cc70-507982c7336b@gmail.com>
On Wed, Jan 24, 2018 at 10:24 AM, Aymeric Vitte <vitteaymeric@gmail.com> wrote:
> out the fact that pubkey is there now even for standard p2pkh
> transactions and it was not the case some time ago
>
> But I never got any answer regarding what motivated this change
> (compared to the previous behavior) and when, so whether I am missing
> something obvious, whether nobody wants to answer
No such behaviour ever existed, you are simply mistaken.
next prev parent reply other threads:[~2018-01-24 10:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 3:50 [bitcoin-dev] Why is deriving public key from the signature not used in Segwit? Артём Литвинович
2018-01-24 4:25 ` Gregory Maxwell
2018-01-24 10:24 ` Aymeric Vitte
2018-01-24 10:31 ` Gregory Maxwell [this message]
2018-01-24 11:16 ` Aymeric Vitte
2018-01-24 11:35 ` Gregory Maxwell
2018-01-24 12:03 ` Aymeric Vitte
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=CAAS2fgTT+9DydafDfA3S1_KSDO+hDkA4sNiBmUn+2kHpf5cFag@mail.gmail.com \
--to=greg@xiph.org \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=theartlav@gmail.com \
--cc=vitteaymeric@gmail.com \
/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