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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <stick@gk2.sk>) id 1Wd4NI-0005UM-MA
for bitcoin-development@lists.sourceforge.net;
Wed, 23 Apr 2014 21:06:36 +0000
X-ACL-Warn:
Received: from mail-ee0-f54.google.com ([74.125.83.54])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Wd4NH-0006U2-9x
for bitcoin-development@lists.sourceforge.net;
Wed, 23 Apr 2014 21:06:36 +0000
Received: by mail-ee0-f54.google.com with SMTP id d49so1194165eek.13
for <bitcoin-development@lists.sourceforge.net>;
Wed, 23 Apr 2014 14:06:28 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:message-id:date:from:user-agent:mime-version:cc
:subject:references:in-reply-to:content-type
:content-transfer-encoding;
bh=CRDW4qvFVp9RcgoUEcTNsnWVmFCvnEMDOjZAfT1SABk=;
b=L5n4UvuUX+I/8aDOODdYhPpszEV2G0GV8kWK1fhA6eaSNYuVQPcMCSTc2WVaeEr0a2
qCNc96PtNGV7uyHvji8XUphrfrd1T0KcAU72RIaLTJn0PCNm+cyyS5RgmArrrXsZAX4b
ayeB+FflkiEMzwxa9XcBLTvhMqxAEULnUpeIrNCP7bwBf4AHhGtOdPFKWyAu6iFz/HFx
WfZuNVjo+XzpieMHrsBBexo8PMFoF58Y1caIp3NdAE9ImSESrOItJrTzl8wSH9CRFqEL
MQ9P8E3ETs8N58VrYslKzitei00AQQa3FGtrKs+5I9KMMeNqCTE8n8tU/c4thBodGgjI
glsQ==
X-Gm-Message-State: ALoCoQlbdIoGWCkcxJAjV1VyWYi7RwaD5xWVL9wQRW0ws9swhY1ZhzVLkEo23dmDS/Ed7kmH0YEW
X-Received: by 10.14.99.68 with SMTP id w44mr20005818eef.82.1398287188728;
Wed, 23 Apr 2014 14:06:28 -0700 (PDT)
Received: from tetra.site (nat-0-15.lam.cz. [80.92.242.254])
by mx.google.com with ESMTPSA id 48sm9561480eei.24.2014.04.23.14.06.26
for <bitcoin-development@lists.sourceforge.net>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Wed, 23 Apr 2014 14:06:27 -0700 (PDT)
Message-ID: <53582B52.70205@gk2.sk>
Date: Wed, 23 Apr 2014 23:06:26 +0200
From: Pavol Rusnak <stick@gk2.sk>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
CC: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
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>
In-Reply-To: <CAPg+sBjk4M6+9R=McwWcWda0Pw4u9oGiBR5NDAwpq3dntG6vtg@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 1.2 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
1.2 MISSING_HEADERS Missing To: header
X-Headers-End: 1Wd4NH-0006U2-9x
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:06:36 -0000
On 04/23/2014 10:54 PM, Pieter Wuille 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?
This is not a desired behavior. Do you have any idea how to make it even
more explicit in the spec? Currently we just have (in Account sectrion):
"This level splits the key space into independent user identities, so
the wallet never mixes the coins across different accounts."
I would like to make it obvious from the spec that if you mix funds
accross the accounts you are not doing a right thing and you are not
compliant to the spec.
--
Best Regards / S pozdravom,
Pavol Rusnak <stick@gk2.sk>
|
