summaryrefslogtreecommitdiff
path: root/f9/ae42a827550442fc9cf549567d9deb7819d772
blob: 486a651f6d65ae0aa9afa92c5739e919e702f8fa (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
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <stick@gk2.sk>) id 1We2hn-0007LS-D9
	for bitcoin-development@lists.sourceforge.net;
	Sat, 26 Apr 2014 13:31:47 +0000
X-ACL-Warn: 
Received: from mail-oa0-f42.google.com ([209.85.219.42])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1We2hl-0007oj-CA
	for bitcoin-development@lists.sourceforge.net;
	Sat, 26 Apr 2014 13:31:47 +0000
Received: by mail-oa0-f42.google.com with SMTP id i4so5468633oah.29
	for <bitcoin-development@lists.sourceforge.net>;
	Sat, 26 Apr 2014 06:31:39 -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=xE7B3War3LTD591s4uJOf3OmFrD241p5Uzp1QSz9/rM=;
	b=T/1hmDWZAxkcexbdpnQoZZFAMm8eI7O5yBqg/KjOUHQc/aZtu8QGCBnIa4YImlK0Ld
	uyK6ZaifnL3kduUipDyZN0g5t08rGAZxWaGvjU1T+jNEE9OWeTW04FVIDrrjVB1FX4nC
	BbgE0QqC9KFAlvzLxkshJ0wSe39BwA+iLjjJPcA2MXI5UYK+Q5ua2tns+W8R034lvsi8
	0Bnntq8lv9f37PN4KHG3qLhb25ybx4XPJvbxpyc1GQR1M+mlCjnpRZHeyDqVzSPO8KBy
	fhxwJlwlV+msfNILvytmoNm+OGnNote5wEAp72oxcelfqpA6CizECXKiqk6umtbJdhpB
	Gc5Q==
X-Gm-Message-State: ALoCoQnQJge4vy4GmT5DnriSYk0AiO4cpeTB4dmhZHX7UOOytdTFwwmGuNha/MXswf3SJSxI4jVP
X-Received: by 10.182.248.131 with SMTP id ym3mr1541340obc.58.1398515098991;
	Sat, 26 Apr 2014 05:24:58 -0700 (PDT)
Received: from tetra.site ([91.239.236.56])
	by mx.google.com with ESMTPSA id h1sm22350956obr.15.2014.04.26.05.24.57
	for <bitcoin-development@lists.sourceforge.net>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Sat, 26 Apr 2014 05:24:58 -0700 (PDT)
Message-ID: <535BA597.70708@gk2.sk>
Date: Sat, 26 Apr 2014 14:24:55 +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 Dev <bitcoin-development@lists.sourceforge.net>
References: <ljdd29$522$1@ger.gmane.org>	<1398437607.23028.110362141.03111A2A@webmail.messagingengine.com>	<CAAS2fgRiXdOBN2gVZ0Xh4kBeOKiS80AjD5+VxJEut9nWt-0WUg@mail.gmail.com>	<535B8C43.8030502@gmx.de>
	<CAE-z3OWcZdQ0J3vNYQ7whGHOZZzMh=wYKxCKtrf1i8VSseZArQ@mail.gmail.com>
In-Reply-To: <CAE-z3OWcZdQ0J3vNYQ7whGHOZZzMh=wYKxCKtrf1i8VSseZArQ@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=windows-1252
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: 1We2hl-0007oj-CA
Subject: Re: [Bitcoin-development] BIP32 "wallet structure" in use? Remove
 it?
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: Sat, 26 Apr 2014 13:31:47 -0000

On 04/26/2014 12:48 PM, Tier Nolan wrote:
> Maybe the solution is to have a defined way to import an unknown wallet?

That is nonsense. There is no way how to import the wallet if you don't
know its structure.

> Given a blockchain and a root seed, it should be possible to find all the
> addresses for that root seed.

Unless the keyspace is almost infinite because:

> The hierarchy that the wallet actually uses could be anything.

-- 
Best Regards / S pozdravom,

Pavol Rusnak <stick@gk2.sk>