On Mon, Aug 28, 2017 at 08:55:47PM +, Alex Nagy via bitcoin-dev wrote:
> Thanks Gregory - to be clear should Native P2WPKH scripts only appear in
> redeem scripts? From reading the various BIPs it had seemed like Native
> P2WPKH and Native P2WSH were also valid and identifiable if they were
Yes it is allowed in TxOuts. And yes it is designed to save space. But the
problem is Bob can’t assume Alice understands the new TxOuts format. If Bob
really wants to save space this way, he should first ask for a new BIP173
address from Alice. Never try to convert a P2PKH address to a P2SH or
> On Aug 28, 2017, at 8:29 AM, Alex Nagy via bitcoin-dev
> wrote:
>
> If Alice gives Bob 1MsHWS1BnwMc3tLE8G35UXsS58fKipzB7a, is there any way Bob
> can safely issue Native P2WPKH outputs to Alice?
>
No, and the whole issue of compressed vs uncompressed
in Txes with many
outputs.
-Original Message-
From: Gregory Maxwell [mailto:gmaxw...@gmail.com]
Sent: Monday, August 28, 2017 10:04 AM
To: Alex Nagy <optim...@hotmail.com>; Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] P2WPKH Sc
Let's say Alice has a P2PKH address derived from an uncompressed public key,
1MsHWS1BnwMc3tLE8G35UXsS58fKipzB7a (from
https://bitcoin.stackexchange.com/questions/3059/what-is-a-compressed-bitcoin-key).
If Alice gives Bob 1MsHWS1BnwMc3tLE8G35UXsS58fKipzB7a, is there any way Bob can
safely issue