summaryrefslogtreecommitdiff
path: root/9c/47a146967bcf7f8c8e1dce4d4d6ef9cdfe73b9
blob: d038304a22ee94b57b55a6d14d0a7ef8fe6bc9e8 (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
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <thomasv@electrum.org>) id 1YVyvR-0006I8-BT
	for bitcoin-development@lists.sourceforge.net;
	Thu, 12 Mar 2015 08:57:05 +0000
X-ACL-Warn: 
Received: from relay4-d.mail.gandi.net ([217.70.183.196])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.76) id 1YVyvP-0002W6-D0
	for bitcoin-development@lists.sourceforge.net;
	Thu, 12 Mar 2015 08:57:05 +0000
Received: from mfilter30-d.gandi.net (mfilter30-d.gandi.net [217.70.178.161])
	by relay4-d.mail.gandi.net (Postfix) with ESMTP id 3FC571720BA
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 12 Mar 2015 09:56:57 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at mfilter30-d.gandi.net
Received: from relay4-d.mail.gandi.net ([217.70.183.196])
	by mfilter30-d.gandi.net (mfilter30-d.gandi.net [10.0.15.180])
	(amavisd-new, port 10024) with ESMTP id QORE8CnJkIKo
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 12 Mar 2015 09:56:55 +0100 (CET)
X-Originating-IP: 78.53.2.206
Received: from [192.168.1.45] (f053002206.adsl.alicedsl.de [78.53.2.206])
	(Authenticated sender: thomasv@electrum.org)
	by relay4-d.mail.gandi.net (Postfix) with ESMTPSA id C134A1720BF
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 12 Mar 2015 09:56:55 +0100 (CET)
Message-ID: <550154D7.6090900@electrum.org>
Date: Thu, 12 Mar 2015 09:56:55 +0100
From: Thomas Voegtlin <thomasv@electrum.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
References: <54F32EED.6040103@electrum.org>	<CANEZrP23buJF0ENfrKGRuzpQ3Uod09s-kRcb3CBw1-OmUxEyZg@mail.gmail.com>	<550057FD.6030402@electrum.org>
	<mdpn3q$bhd$1@ger.gmane.org>
In-Reply-To: <mdpn3q$bhd$1@ger.gmane.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
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: 1YVyvP-0002W6-D0
Subject: Re: [Bitcoin-development] Electrum 2.0 has been tagged
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: Thu, 12 Mar 2015 08:57:05 -0000

Hi Andreas,

I don't think it's a problem that BIP43 is tied to BIP32.

What I don't like is that you have to explore branches of the derivation
tree, in order to know if there is a wallet. As a result, it is not
possible for the software to give a negative answer, like "this wallet
is empty", because you do not know if you have explored all the possible
derivations; a new one may have been added after the software was written=
.

With a version number, you can answer "sorry this seed is not recognized
by me", and you do not need to be online to do that.
If you are online, you can answer "this wallet is empty" after exploring =
it.




Le 11/03/2015 16:31, Andreas Schildbach a =E9crit :
> Thanks Thomas, for sharing your experience!
>=20
> I'd like know why you think it's a problem that BIP43 is tied to BIP32?
> I understand we all agreed at least on the BIP32-derivation spec
> (excluding the BIP32-hierarchy spec)?
>=20
>=20
>=20
> -----------------------------------------------------------------------=
-------
> Dive into the World of Parallel Programming The Go Parallel Website, sp=
onsored
> by Intel and developed in partnership with Slashdot Media, is your hub =
for all
> things parallel software development, from weekly thought leadership bl=
ogs to
> news, videos, case studies, tutorials and more. Take a look and join th=
e=20
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>=20
>=20