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
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
|
Return-Path: <hoenicke@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id EE072955
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 15 Jun 2016 10:26:51 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wm0-f50.google.com (mail-wm0-f50.google.com [74.125.82.50])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 96F3A150
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 15 Jun 2016 10:26:50 +0000 (UTC)
Received: by mail-wm0-f50.google.com with SMTP id f126so15274080wma.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 15 Jun 2016 03:26:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=subject:to:references:from:message-id:date:user-agent:mime-version
:in-reply-to:content-transfer-encoding;
bh=V6bP5HzUckhnxAdkt+SnNA1Lg1VzQ50AoyIAqwv8kqQ=;
b=dljAqW3ba+LUoh3P/ofUiA5tYHizGxHqtSHPXy8uIA3JhK9wdZFM/DW4uDqefJTvHP
ixiq+BEGoMlg+DtO4wmbijqWE2MjBuR6v66ZwfGgkSYzf55rQ7Dtq2ZWlkKdplBqljUO
1JUJhaw6dlnB/uvfz1RmC2ron1j52WYunvEQQINKHDAS0QH487QqKPK/zR6j+20/5SNw
fPG2uJO/VRzlUdxOInhpjKfclOeJtq5dU0rcuU8tMETnlqgmFh4sRIIuqTMNDRxS2lzR
wdsi8ppYUsCT0R8DXDNS+HhuAAZb5moTGyg6yR9s6uJfCyFbk/9p7ZYKWc2TgYKCPguu
BNJQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:subject:to:references:from:message-id:date
:user-agent:mime-version:in-reply-to:content-transfer-encoding;
bh=V6bP5HzUckhnxAdkt+SnNA1Lg1VzQ50AoyIAqwv8kqQ=;
b=UUxTOTor/OG2yHsQs0PzxtYCUKOmoAfodgY22yih3lUUw03chA6lQQMavl81aGY6Yq
LnqW254MF4pmngYv6zq8o5WVUnMeK0XfkukdugT51vHChXM6RBSRocymwS4smhBeRQId
1TpzkbIYzYQajGGcLBh+BAwxjXFefM0hXyhk9DAN8lHIIR1vbt1q72oenLNwMWV5Isvn
CKKU8eFjO1sre7RwXUM8heZ4Yhxpfsw0s7R09kUE11Ay22KFeltrBxGU983o2gTFTcwt
oYLpOarz4cLOFBucCiuWe4t/a1iXhrlOTOMZz5hX4xjfNPD1Pb2P+pf3JLJfu2RfeMyl
+7Ag==
X-Gm-Message-State: ALyK8tJ+bAZ7LuFAS1UE/FPAMa1Wy/7IccItD3ooSgcDGv9xIuV3/xiyaVf+hOZXMdwRng==
X-Received: by 10.194.81.72 with SMTP id y8mr11302195wjx.83.1465986409077;
Wed, 15 Jun 2016 03:26:49 -0700 (PDT)
Received: from ?IPv6:2001:4dd0:ff00:8a0a:c68e:8fff:fef3:22ad?
([2001:4dd0:ff00:8a0a:c68e:8fff:fef3:22ad])
by smtp.googlemail.com with ESMTPSA id
e5sm37693217wjj.10.2016.06.15.03.26.48
(version=TLSv1/SSLv3 cipher=OTHER);
Wed, 15 Jun 2016 03:26:48 -0700 (PDT)
To: Daniel Weigl <Daniel.Weigl@mycelium.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
References: <5760259B.7040409@mycelium.com>
From: Jochen Hoenicke <hoenicke@gmail.com>
Message-ID: <57612D67.9080007@gmail.com>
Date: Wed, 15 Jun 2016 12:26:47 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
Thunderbird/38.8.0
MIME-Version: 1.0
In-Reply-To: <5760259B.7040409@mycelium.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM,
RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] RFC for BIP: Derivation scheme for
P2WPKH-nested-in-P2SH based accounts
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: Wed, 15 Jun 2016 10:26:52 -0000
Hello Daniel,
Am 14.06.2016 um 17:41 schrieb Daniel Weigl via bitcoin-dev:
> Hi List,
>
> Following up to the discussion last month ( https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-May/012695.html ), ive prepared a proposal for a BIP here:
>
> https://github.com/DanielWeigl/bips/blob/master/bip-p2sh-accounts.mediawiki
>
>
> Any comments on it? Does anyone working on a BIP44 compliant wallet implement something different?
> If there are no objection, id also like to request a number for it.
thank you for going forward with this. Should we keep the discussion on
the list, or should we make it on github?
I think we should already consider not only P2WPKH over P2SH addresses
but also "native" P2WPKH addresses. Instead of having one BIP for these
two kinds of segwit addresses and forcing the user to have several
different accounts for each BIP, the idea would be that every fully
BIP?? compatible wallet must support both of them. Since P2WPKH is
simpler than P2WPKH over P2SH, this is IMHO reasonable to require.
I would go with the suggestion from Aaron Voisine to use different chain
id's to distinguish between different address types. E.g., 0,1 for
P2WPKH over P2SH and 2,3 for native P2WPKH. I see no reason why a
wallet would want to use P2WPKH over P2SH for change addresses instead
of native P2WPKH, though.
Jochen
|
