1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
|
Return-Path: <jl2012@xbt.hk>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 885BC596
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 29 Aug 2017 03:45:23 +0000 (UTC)
X-Greylist: delayed 00:15:04 by SQLgrey-1.7.6
Received: from sender-of-o52.zoho.com (sender-of-o52.zoho.com [135.84.80.217])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id DDD661AC
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 29 Aug 2017 03:45:22 +0000 (UTC)
Received: from [192.168.1.139] (137.189.135.167 [137.189.135.167]) by
mx.zohomail.com with SMTPS id 1503977413683277.9043810718821;
Mon, 28 Aug 2017 20:30:13 -0700 (PDT)
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>
X-Mailer: Apple Mail (2.3273)
X-ZohoMailClient: External
X-Spam-Status: No, score=0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE
autolearn=disabled version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Cc: Gregory Maxwell <gmaxwell@gmail.com>
Subject: Re: [bitcoin-dev] P2WPKH Scripts, P2PKH Addresses,
and Uncompressed Public Keys
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Aug 2017 03:45:23 -0000
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
|
