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
|
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 <stick@gk2.sk>) id 1WXX7q-000307-4x
for bitcoin-development@lists.sourceforge.net;
Tue, 08 Apr 2014 14:35:46 +0000
X-ACL-Warn:
Received: from mail-ee0-f53.google.com ([74.125.83.53])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WXX7o-0006QY-M6
for bitcoin-development@lists.sourceforge.net;
Tue, 08 Apr 2014 14:35:46 +0000
Received: by mail-ee0-f53.google.com with SMTP id b57so771013eek.12
for <bitcoin-development@lists.sourceforge.net>;
Tue, 08 Apr 2014 07:35:38 -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
:cc:subject:references:in-reply-to:content-type
:content-transfer-encoding;
bh=kuOq2tXcw/tojmu9kmmyspMoe7B7hJbloNqm2Be78Hw=;
b=VK5APT2a8qBVPC06QgyCpLuPMDjuuRGUwLwhxOs30VKGLhmDfnhrayNsStEAdKZkyN
CcA7FWQBgGdM4rvE7aPtCjm1jwlcXY7ninVagy7a+IQ70mMQERTknrklFriBp+aOLP+J
zf9NNh9rJcJDf926Khz0e3m4v02shPaMsE/Q0Fj9irjB/Ynnq3V4AMTrZpPNrDy8D+QM
KFBZo2VRkqW0nb7fXh89aayHmezCpk7V+h0Sg81WHFBaYjeClCKxO1V5mY4PuPEGxd6F
eL4STgCd4Rhc00RjrcJlb9GoG0gwR4OgAwc1VzsIcG2LXKjQavFOq/7P2AUtqCuiNHWq
jzDA==
X-Gm-Message-State: ALoCoQkqNpRRECkoQnejuw7BUWuW2dFe8kz+y962TI071JSf5eBvmVNqlac5/nVK4JrYu8qkcc4e
X-Received: by 10.15.21.2 with SMTP id c2mr2820871eeu.78.1396967737971;
Tue, 08 Apr 2014 07:35:37 -0700 (PDT)
Received: from tetra.site (nat-0-15.lam.cz. [80.92.242.254])
by mx.google.com with ESMTPSA id m44sm5000658eep.14.2014.04.08.07.35.36
for <multiple recipients>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Tue, 08 Apr 2014 07:35:36 -0700 (PDT)
Message-ID: <53440937.1010501@gk2.sk>
Date: Tue, 08 Apr 2014 16:35:35 +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: Pieter Wuille <pieter.wuille@gmail.com>, slush <slush@centrum.cz>
References: <CANEZrP2hbBVGqytmXR1rAcVama4ONnR586Se-Ch=dsxOzy2O4w@mail.gmail.com> <F2C8C044-EF92-4CCE-9235-28CA7FCE3526@bitsofproof.com> <CAJHLa0PPAsBLgsy0vgPpUp=UzeR_fWUEzFb5+xtmODEk4MGPVQ@mail.gmail.com> <CAJfRnm7V6fgcj=TMfa2ZTYWOKtE5aoUT1xnVtKUSyriB=6cagQ@mail.gmail.com> <CAPg+sBjwf1TcK1CGKVKFzYbV-78j8t-pav7=PEgG7Yqi6-yE7A@mail.gmail.com> <53344FF8.7030204@gk2.sk> <CAPg+sBhbx5vy_hewAkFPaiXHzSMNH0qLhEYGjPmQMjR5StP-tw@mail.gmail.com> <CAJna-Hi0JnrF2_rUx0rGkdnsuCoaD01e3Gobpn+QqbL=D1Uivg@mail.gmail.com> <CAJna-HirtsGLfAhfUf9dAYEGWo6g=o=eAU187c2pdW8vDFGkPw@mail.gmail.com> <CAPg+sBg8wDH9yTUoyhRbuzVtbD8hGxya8tOnV4pMToHy3gLrzw@mail.gmail.com> <CAJna-HiN_1KQmpDJFFX6mGvM63RC0xwXxvfuorpihnzYf4=fsQ@mail.gmail.com> <CAJna-HgfpyHX_0AHwt1Hkj0qhD_-xOcpxsZ9KXq=7CPgwse1hA@mail.gmail.com>
<CAPg+sBguSQ8dk1xXKinX+ez4BmdM3sz-huruuhD6NCTsp0kRBQ@mail.gmail.com>
In-Reply-To: <CAPg+sBguSQ8dk1xXKinX+ez4BmdM3sz-huruuhD6NCTsp0kRBQ@mail.gmail.com>
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: 1WXX7o-0006QY-M6
Cc: Bitcoin Dev <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: Tue, 08 Apr 2014 14:35:46 -0000
On 04/08/2014 03:53 PM, Pieter Wuille wrote:
> Let me offer an alternative suggestion, which is compatible with the
> original default BIP32 structure:
> * You can use one seed across different chains, but the master nodes
> are separate.
> * To derive the master node from the seed, the key string "Bitcoin
> seed" is replaced by something chain-specific.
> * Every encoded node (including master nodes) has a chain-specific
> serialization magic.
This is possible, but I find it much more practical to use just one list
(assignment of coins to indexes) than to use two lists (assignment of
coins to key strings and to serialization magic).
Keeping two lists is harder and adds unnecessary friction. (Also I am
not very happy for the possibility we'll have to deal with key strings
"sCAMCo1N RULEZZZZ!!!! bRoUghT TO YoU bY M4rty" and serialization magic
that leads to prefix "lulz").
Also from wallet's implementer perspective it is a little easier to use
just one root node and then descend in tree as needed than to use method
you described.
--
Best Regards / S pozdravom,
Pavol Rusnak <stick@gk2.sk>
|
