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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <marek@palatinus.cz>) id 1Wd3JH-0006Fg-KZ
for bitcoin-development@lists.sourceforge.net;
Wed, 23 Apr 2014 19:58:23 +0000
X-ACL-Warn:
Received: from mail-ve0-f173.google.com ([209.85.128.173])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Wd3JG-0003Nb-H2
for bitcoin-development@lists.sourceforge.net;
Wed, 23 Apr 2014 19:58:23 +0000
Received: by mail-ve0-f173.google.com with SMTP id oy12so1751955veb.4
for <bitcoin-development@lists.sourceforge.net>;
Wed, 23 Apr 2014 12:58:17 -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=SzmuWomjPjnJHXUk+I7ytgO5kX4mtH8pdONPYzIxjdQ=;
b=agEhKagaynyzaLrjofrXen8UC2RFXdmWPKKcdRgb/++L/6xY+Adc7Y9bYSeGPakMSw
ijSPTwCzrh6Y4XBLKACm2QhTaNTjNeF/WagFHzBu2RHSzAIKXFO4x3ZJicO4P2j4pcMc
6iBqZ2g1Inw12b0DxZL8AGXLt5seqAgHmi6ocIzaj2px6yuKxxpdrHu1u7FRCKFWo0fa
OL1w2XfSW/uaNC3UHnd46GMrtHO2b07emMCJhVY1WQpljo0cJUv6ZoGWsiIXdHWTB/HL
dfo1cZ3pXZ2H2YrpWK1w6ToTj2qAdwe+cAgZeOkHDMQ7Eix+UMTSBcp94sPoCsDJ/cts
qDZQ==
X-Gm-Message-State: ALoCoQlPy3INZbec4XSxHMzjyRBMaXfpybEjM/6ZYIVGG00kNZpHDbcok3n8kx6GLVwu84IlXIl8
X-Received: by 10.52.6.162 with SMTP id c2mr36776868vda.6.1398283096977; Wed,
23 Apr 2014 12:58:16 -0700 (PDT)
MIME-Version: 1.0
Sender: marek@palatinus.cz
Received: by 10.58.234.68 with HTTP; Wed, 23 Apr 2014 12:57:46 -0700 (PDT)
In-Reply-To: <201404231955.09287.luke@dashjr.org>
References: <CANEZrP2hbBVGqytmXR1rAcVama4ONnR586Se-Ch=dsxOzy2O4w@mail.gmail.com>
<201404231944.14256.luke@dashjr.org> <53581952.1050602@gk2.sk>
<201404231955.09287.luke@dashjr.org>
From: slush <slush@centrum.cz>
Date: Wed, 23 Apr 2014 21:57:46 +0200
X-Google-Sender-Auth: wsLRTb0wUkcJNgYyEz_40OPVa48
Message-ID: <CAJna-Hhm-BDneR_qVzFtrGaMzs-7R-z5V49CVVv79mdOfBCD-w@mail.gmail.com>
To: Luke-Jr <luke@dashjr.org>
Content-Type: multipart/alternative; boundary=20cf303347394a896304f7bb273c
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: 1Wd3JG-0003Nb-H2
Cc: "bitcoin-development@lists.sourceforge.net"
<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 19:58:23 -0000
--20cf303347394a896304f7bb273c
Content-Type: text/plain; charset=ISO-8859-1
On Wed, Apr 23, 2014 at 9:55 PM, Luke-Jr <luke@dashjr.org> wrote:
> Any wallet should import all the coins just fine, it just wouldn't *use*
> any
> account other than 0. Remember addresses are used to receive bitcoins; once
> the UTXOs are in the wallet, they are no longer associated with the
> address or
> any other details of how they were received.
>
Wallet don't see UTXO until it scans all branches/accounts on HD node
import.
--20cf303347394a896304f7bb273c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Wed, Apr 23, 2014 at 9:55 PM, Luke-Jr <span dir=3D"ltr"><<a href=3D"m=
ailto:luke@dashjr.org" target=3D"_blank">luke@dashjr.org</a>></span> wro=
te:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex">
<div class=3D"">Any wallet should import all the coins just fine, it just w=
ouldn't *use* any<br></div>
account other than 0. Remember addresses are used to receive bitcoins; once=
<br>
the UTXOs are in the wallet, they are no longer associated with the address=
or<br>
any other details of how they were received.<br></blockquote><div><br></div=
><div>Wallet don't see UTXO until it scans all branches/accounts on HD =
node import.=A0</div></div></div></div>
--20cf303347394a896304f7bb273c--
|
