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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <marek@palatinus.cz>) id 1Wd4Or-0005LE-E6
for bitcoin-development@lists.sourceforge.net;
Wed, 23 Apr 2014 21:08:13 +0000
X-ACL-Warn:
Received: from mail-vc0-f178.google.com ([209.85.220.178])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Wd4Oq-00048Y-2j
for bitcoin-development@lists.sourceforge.net;
Wed, 23 Apr 2014 21:08:13 +0000
Received: by mail-vc0-f178.google.com with SMTP id hu19so1865743vcb.37
for <bitcoin-development@lists.sourceforge.net>;
Wed, 23 Apr 2014 14:08:06 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:sender:in-reply-to:references:from
:date:message-id:subject:to:cc:content-type;
bh=gJqEqbg15WVwreHNJMxHlhYXY92fy7q2JsUMmfbYNE4=;
b=fb0ZifnCiTiS8tV8kRWPW1MWQkCUZs6L+u/Hoy+Xo0Bw9UAWN5bQj3xxbo7rRWaokX
9sarEaACM89nOxIJqRg6OOfi8hlRuwJXR8g01ZAxOyUE40/TEM4sSK/Rq1qSuQqsIepi
MWgdJPHrWCinWDo3gFcZaZLFbTyCnmp+gC2YEPgtHpZyxHIT0g0r0DOYEomfMx8HsER9
g9/JAlW+2QZY4fKB38UVtlu+pXGPfDipfTw4Iy0KAoEkgrnzScgj4fNSnn7IbD8VbfX9
tS5G3yOxJ1r9zghsOqWIPmk9PN1cWSQdvBFrA5TVau4TsjeissoRTmna8nk8fcvZgL8K
z+dQ==
X-Gm-Message-State: ALoCoQl8wwkNNxZZqsQeiZCnV72jPq04Y7BrPBYFRPKD9prckNDuk/IdrplFaqHZ6Y96fbCMXr29
X-Received: by 10.52.173.165 with SMTP id bl5mr36892530vdc.13.1398287286515;
Wed, 23 Apr 2014 14:08:06 -0700 (PDT)
MIME-Version: 1.0
Sender: marek@palatinus.cz
Received: by 10.58.234.68 with HTTP; Wed, 23 Apr 2014 14:07:36 -0700 (PDT)
In-Reply-To: <CAPg+sBjk4M6+9R=McwWcWda0Pw4u9oGiBR5NDAwpq3dntG6vtg@mail.gmail.com>
References: <CANEZrP2hbBVGqytmXR1rAcVama4ONnR586Se-Ch=dsxOzy2O4w@mail.gmail.com>
<201404232032.08740.luke@dashjr.org> <53582426.4030601@gk2.sk>
<201404232041.14664.luke@dashjr.org> <5358260D.9040607@gk2.sk>
<CAPg+sBjk4M6+9R=McwWcWda0Pw4u9oGiBR5NDAwpq3dntG6vtg@mail.gmail.com>
From: slush <slush@centrum.cz>
Date: Wed, 23 Apr 2014 23:07:36 +0200
X-Google-Sender-Auth: lHRa8vTTsgzUEVp-mrb4paG-9ao
Message-ID: <CAJna-HhrTOzJiUj3FjhYftKyfA5MzE=O1w3jYxOg96c=JSr4sQ@mail.gmail.com>
To: Pieter Wuille <pieter.wuille@gmail.com>
Content-Type: multipart/alternative; boundary=bcaec51b9cfd01ce5b04f7bc21bd
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(slush[at]centrum.cz)
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1Wd4Oq-00048Y-2j
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] New BIP32 structure
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Wed, 23 Apr 2014 21:08:13 -0000
--bcaec51b9cfd01ce5b04f7bc21bd
Content-Type: text/plain; charset=ISO-8859-1
On Wed, Apr 23, 2014 at 10:54 PM, Pieter Wuille <pieter.wuille@gmail.com>wrote:
>
> Would you consider software which scans all accounts as specified by
> BIP64, but has no user interface option to distinguish them in any
> way, view them independently, and has no ability to keep the coins
> apart... compatible with BIP64?
>
>
No, because one of requirement of BIP64 is to do not mix addressess between
accounts. Without handling those accounts fully, it won't pass this
requirement.
("This level [accounts] splits the key space into independent user
identities, so the wallet never mixes the coins across different accounts.")
Marek
--bcaec51b9cfd01ce5b04f7bc21bd
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Apr 23, 2014 at 10:54 PM, Pieter Wuille <span dir=3D"ltr"><<a href=
=3D"mailto:pieter.wuille@gmail.com" target=3D"_blank">pieter.wuille@gmail.c=
om</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div class=3D""><br>
</div>Would you consider software which scans all accounts as specified by<=
br>
BIP64, but has no user interface option to distinguish them in any<br>
way, view them independently, and has no ability to keep the coins<br>
apart... compatible with BIP64?<br>
<br></blockquote><div><br></div><div>No, because one of requirement of BIP6=
4 is to do not mix addressess between accounts. Without handling those acco=
unts fully, it won't pass this requirement.</div><div><br></div><div>
("<span style=3D"color:rgb(51,51,51);font-family:Helvetica,arial,frees=
ans,clean,sans-serif;font-size:15px;line-height:25.5px">This level [account=
s] splits the key space into independent user identities, so the wallet nev=
er mixes the coins across different accounts.")</span></div>
<div>=A0</div><div><br></div><div>Marek</div></div><br></div></div>
--bcaec51b9cfd01ce5b04f7bc21bd--
|
