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
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
|
Return-Path: <kabuto@samouraiwallet.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 899C19B9
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 7 Sep 2017 16:33:52 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-lf0-f53.google.com (mail-lf0-f53.google.com
[209.85.215.53])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id CD663101
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 7 Sep 2017 16:33:51 +0000 (UTC)
Received: by mail-lf0-f53.google.com with SMTP id q132so352725lfe.5
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 07 Sep 2017 09:33:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=samouraiwallet-com.20150623.gappssmtp.com; s=20150623;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to;
bh=jQKQCWtZUsMkAl91kCOKHL5sdombaceAibEXdMFdlRE=;
b=b630Dcb2okrVhf3kl8Qg/rFJPJnr3v6HPz3+n4vFvC/AgSVxEN7BQ9V8TbwDuoCFSU
5YedNilRzDaPZ6tx9O2cPpF4OHIjZeO6VOukX39Oq3mTJWtvWgTtBJHe5QVaJiN2d0Rm
XkbM74Nw3yvxRz7uSIV+LGIIWOF4Lw8Rj00fRtCLP7Y7yiN/n3ALHZ3T0sah7YrNSTVr
RXAfIPtwHLfVyV5oskc0/Ey/F2M5A8F0/KsluabF77DljUIaykSa3vAydBplG6Iu6et2
zwsMtQ4o2+2fPTV1bWcuYu2/L+rBdpmRqEEExJhmshJa9cYRhuq4mo+WWlEYb2Fh41ie
U7Vg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to;
bh=jQKQCWtZUsMkAl91kCOKHL5sdombaceAibEXdMFdlRE=;
b=gwKmAlOL4s/mPTTdp0cgw1E4gMTFJorGk2uL4as8fphJ72H95NEN06C6czultmap7s
gbW+FcNU7+qiNkv/uJjvsd9vnM0oSTS2sPiCIO1oE65bb6x2wKJ+lrCcPEB0guvPrkOO
PIvGNyUHaI180GbDKp1BJ3u6r98z9DZL3hcJS6gEct70iXh4vZLyvOLr78ZZti5vAxjz
3F2v+uWmp12mEJnD+vSWW+T+o594md+O0OioZ0v8lDvMsbKWLrEsQTUo6OsO+/SknPsK
j9mz9D8vypJMLlBtzQJWeHy2LzA42ek3LEeg46viap3jCX601V164yPWbD/YWmPRCB9+
YqUQ==
X-Gm-Message-State: AHPjjUhPLcnQ9VGcioBwnifzMJW0YgULc7M/0/YyCovMIShdVCr0yEsK
ZfqtW4x63lO/dmT62gNhk1a/bddMttbsRe4=
X-Google-Smtp-Source: ADKCNb4spx/tI1Hbnw/ngnmFLKDHz+CN3zrdRwtLjobBEyUxZhMzbua8ix+8IZuslResajJqgYbxlVlGMmrhDUEtUb8=
X-Received: by 10.46.7.67 with SMTP id i3mr1372924ljd.160.1504802030286; Thu,
07 Sep 2017 09:33:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.148.23 with HTTP; Thu, 7 Sep 2017 09:33:09 -0700 (PDT)
In-Reply-To: <84f4a4b8-fcbd-433b-9556-174ec5475f61@satoshilabs.com>
References: <0d405f5d-c0a4-bad7-b6c3-08ba4424bf17@satoshilabs.com>
<8b4831a4-791e-c03e-baa4-16d9e5ead442@electrum.org>
<84f4a4b8-fcbd-433b-9556-174ec5475f61@satoshilabs.com>
From: Kabuto Samourai <kabuto@samouraiwallet.com>
Date: Thu, 7 Sep 2017 11:33:09 -0500
Message-ID: <CA+_kfXLjeQJbJGy5=ssynGOTaGkzvzWQ2RMdhcqCG1DNjqvFWA@mail.gmail.com>
To: Pavol Rusnak <stick@satoshilabs.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="f403045f78e0790a8b05589c063e"
X-Spam-Status: No, score=0.5 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM autolearn=disabled
version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Thu, 07 Sep 2017 16:39:05 +0000
Subject: Re: [bitcoin-dev] Proposal: Extended serialization format for
BIP-32 wallets
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: Thu, 07 Sep 2017 16:33:52 -0000
--f403045f78e0790a8b05589c063e
Content-Type: text/plain; charset="UTF-8"
OutputType byte solution is nearly equivalent to {x,y,z} and adds redundant
data. Implementations could erroneously (maliciously) assign the wrong
output type for the given purpose field.
We could reduce the scope of this improvement to BIP43, as suggested by
Thomas. BIP32-generic wallets may implement something else.
On Thu, Sep 7, 2017 at 11:23 AM, Pavol Rusnak via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> On 07/09/17 06:29, Thomas Voegtlin via bitcoin-dev wrote:
> > A solution is still needed to wallets who do not wish to use BIP43
>
> What if we added another byte field OutputType for wallets that do not
> follow BIP43?
>
> 0x00 - P2PKH output type
> 0x01 - P2WPKH-in-P2SH output type
> 0x02 - native Segwit output type
>
> Would that work for you?
>
> The question is whether this field should be present only if depth==0x00
> or at all times. What is your suggestion, Thomas?
>
> --
> Best Regards / S pozdravom,
>
> Pavol "stick" Rusnak
> CTO, SatoshiLabs
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--
-Kabuto
PGP Fingerprint: 1A83 4A96 EDE7 E286 2C5A B065 320F B934 A79B 6A99
--f403045f78e0790a8b05589c063e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">OutputType byte solution is nearly equivalent to {x,y,z} a=
nd adds redundant data. Implementations could erroneously (maliciously) ass=
ign the wrong output type for the given purpose field.<div><br></div><div>W=
e could reduce the scope of this improvement to BIP43, as suggested by Thom=
as. BIP32-generic wallets may implement something else.</div></div><div cla=
ss=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Sep 7, 2017 at 11=
:23 AM, Pavol Rusnak via bitcoin-dev <span dir=3D"ltr"><<a href=3D"mailt=
o:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">bitcoin-dev@list=
s.linuxfoundation.org</a>></span> wrote:<br><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x"><span class=3D"">On 07/09/17 06:29, Thomas Voegtlin via bitcoin-dev wrot=
e:<br>
> A solution is still needed to wallets who do not wish to use BIP43<br>
<br>
</span>What if we added another byte field OutputType for wallets that do n=
ot<br>
follow BIP43?<br>
<br>
0x00 - P2PKH output type<br>
0x01 - P2WPKH-in-P2SH output type<br>
0x02 - native Segwit output type<br>
<br>
Would that work for you?<br>
<br>
The question is whether this field should be present only if depth=3D=3D0x0=
0<br>
or at all times. What is your suggestion, Thomas?<br>
<span class=3D"im HOEnZb"><br>
--<br>
Best Regards / S pozdravom,<br>
<br>
Pavol "stick" Rusnak<br>
CTO, SatoshiLabs<br>
</span><div class=3D"HOEnZb"><div class=3D"h5">____________________________=
__<wbr>_________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
<wbr>linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.<wbr>org=
/mailman/listinfo/bitcoin-<wbr>dev</a><br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
<div class=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=
=3D"ltr"><div><div dir=3D"ltr">-Kabuto</div><div dir=3D"ltr"><br></div><div=
><font size=3D"1">PGP Fingerprint:=C2=A01A83 4A96 EDE7 E286 2C5A =C2=A0B065=
320F B934 A79B 6A99</font></div></div></div></div>
</div>
--f403045f78e0790a8b05589c063e--
|
