Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Johnson Lau <jl2012@xbt.hk>
In-Reply-To: <CY4PR1801MB181557B7331133954A3098DD809E0@CY4PR1801MB1815.namprd18.prod.outlook.com>
Date: Tue, 29 Aug 2017 11:30:07 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <740F886F-6471-4418-A018-1A1B185744C3@xbt.hk>
References: <CY4PR1801MB181583C344B0993205D4B6C8809E0@CY4PR1801MB1815.namprd18.prod.outlook.com>
	<CAAS2fgT+HHg_xuuWuGrYcX0ALcBowmY-1Kt6-dzSBOwdcr08HQ@mail.gmail.com>
	<CY4PR1801MB181557B7331133954A3098DD809E0@CY4PR1801MB1815.namprd18.prod.outlook.com>
To: Alex Nagy <optimiz3@hotmail.com>,
	bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
Cc: Gregory Maxwell <gmaxwell@gmail.com>
Subject: Re: [bitcoin-dev] P2WPKH Scripts, P2PKH Addresses,
 and Uncompressed Public Keys
Precedence: list

Yes it is allowed in TxOuts. And yes it is designed to save space. But =
the problem is Bob can=E2=80=99t 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 BIP173 address without the consent of the =
recipient.
=20

> On 29 Aug 2017, at 4:55 AM, Alex Nagy via bitcoin-dev =
<bitcoin-dev@lists.linuxfoundation.org> wrote:
>=20
> Thanks Gregory - to be clear should Native P2WPKH scripts only appear =
in redeem scripts?  =46rom reading the various BIPs it had seemed like =
Native P2WPKH and Native P2WSH were also valid and identifiable if they =
were encoded in TxOuts.  The theoretical use case for this would be =
saving bytes in Txes with many outputs.
>=20