blob: 65a2a8a230824850aae4598c3e3b673fe4d31230 (
plain)
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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <stick@gk2.sk>) id 1Wd41X-0003zX-JH
for bitcoin-development@lists.sourceforge.net;
Wed, 23 Apr 2014 20:44:07 +0000
X-ACL-Warn:
Received: from mail-ee0-f41.google.com ([74.125.83.41])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Wd41W-0005Yq-BW
for bitcoin-development@lists.sourceforge.net;
Wed, 23 Apr 2014 20:44:07 +0000
Received: by mail-ee0-f41.google.com with SMTP id t10so1187318eei.14
for <bitcoin-development@lists.sourceforge.net>;
Wed, 23 Apr 2014 13:44:00 -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:to
:subject:references:in-reply-to:content-type
:content-transfer-encoding;
bh=8P/eVIwAMYI+7DvpMsemCEnteU8FSXlvaEgTNPl3haY=;
b=MDJjhxrgccAZxONvDfD04V551olNzR2swdACCGB6kbhTGXODdqwLeGl/YupyZiemet
o9L2NbfVluyIw4zJG89N9h5PIwnFLw/np+sadr8VfYTrrKYKp+bVBlNwxCOd5Qt7H5xK
WCwj6n+6wlRYjzdLuutaBw3miljEH1EqEWcthwrQexhJv1ZGMFGAZVA3WbfBR9ZsrOOf
Aqa60yfT2LGaXjjZ3+MjKcZDWZGwZS+jMlZDZEVYOoDHI3XOVuVel6YU1MW+l9H0a2y6
u31fKFtHI/iqjSYUWucYOF9mF5bXuHd+5CRPsCDR5fzNTLyeRRD/v3U5jNT24E/WjLt2
JAxg==
X-Gm-Message-State: ALoCoQmIXM5uuSVZMR4WUreo4oTaUfF3dNGhwoDfxnlKqxJ3cZPfUXt3UzLttCR6rLuZJQSC3Jm6
X-Received: by 10.14.113.194 with SMTP id a42mr6113117eeh.115.1398285840026;
Wed, 23 Apr 2014 13:44:00 -0700 (PDT)
Received: from tetra.site (nat-0-15.lam.cz. [80.92.242.254])
by mx.google.com with ESMTPSA id t50sm9406822eev.28.2014.04.23.13.43.58
for <bitcoin-development@lists.sourceforge.net>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Wed, 23 Apr 2014 13:43:59 -0700 (PDT)
Message-ID: <5358260D.9040607@gk2.sk>
Date: Wed, 23 Apr 2014 22:43:57 +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
To: 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>
In-Reply-To: <201404232041.14664.luke@dashjr.org>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1Wd41W-0005Yq-BW
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 20:44:07 -0000
On 04/23/2014 10:41 PM, Luke-Jr wrote:
> I don't see how. The user knows he has money in different subwallets. As long
> as he has a way to specify which subwallet he is accessing in single-subwallet
> clients, there shouldn't be a problem.
Right. But these clients have no right to call themselves BIP64
compatible then.
--
Best Regards / S pozdravom,
Pavol Rusnak <stick@gk2.sk>
|
