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
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <marek@palatinus.cz>) id 1Tg0uq-0001uc-Jo
for bitcoin-development@lists.sourceforge.net;
Tue, 04 Dec 2012 22:24:36 +0000
X-ACL-Warn:
Received: from mail-ie0-f175.google.com ([209.85.223.175])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Tg0up-0008U4-8y
for bitcoin-development@lists.sourceforge.net;
Tue, 04 Dec 2012 22:24:36 +0000
Received: by mail-ie0-f175.google.com with SMTP id qd14so7225141ieb.34
for <bitcoin-development@lists.sourceforge.net>;
Tue, 04 Dec 2012 14:24:30 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=20120113;
h=mime-version:sender:in-reply-to:references:from:date
:x-google-sender-auth:message-id:subject:to:cc:content-type
:x-gm-message-state;
bh=Y30AGOoFEXMrBc2TWATDgdOdClvqfTKqo26rplpBwZ4=;
b=MmTjhm5h69iGn8y4wj5Nrydorf7ET5wXUExcFkO5ZM2Q9HbN9Kf5hzvNZz3mvj7sD1
L+6cyqnUJNASLfqZVuSFMn4mX9qaZi15D6aNpge8dUlXtRz7EVLm6l4uQSoK4wKI3k+G
WOPCZ6NM3rs5iAOopp+TbNvrPbmhOJPnu3fuObrZvlkihHTvCmhn6ALIzdKqnTSCJvQE
n2wJ/MEFt4+2qM10E+WL9c6zt+1lJ0mqPnrqoD1yHykQe04XnGktsmCnyyc+51dtaTmO
j/oNnjxPZhvaGsdNngeX4OzZoqJ9CUR75vc+O7D+YP6KE3nEWhxivVuflowyRZxcgXdV
dlPg==
Received: by 10.50.150.176 with SMTP id uj16mr4380943igb.38.1354659869852;
Tue, 04 Dec 2012 14:24:29 -0800 (PST)
MIME-Version: 1.0
Sender: marek@palatinus.cz
Received: by 10.64.51.103 with HTTP; Tue, 4 Dec 2012 14:23:59 -0800 (PST)
In-Reply-To: <1354650998.21742.140661161849669.1371855A@webmail.messagingengine.com>
References: <mailman.70419.1354648162.2176.bitcoin-development@lists.sourceforge.net>
<1354650998.21742.140661161849669.1371855A@webmail.messagingengine.com>
From: slush <slush@centrum.cz>
Date: Tue, 4 Dec 2012 22:23:59 +0000
X-Google-Sender-Auth: OxfWnmtD7F7qtju3RMFwAgt9lg8
Message-ID: <CAJna-HjuHMDr4sO7FRGGfhncvQsUXygRp6v1D_BVbbZ+3zmcSQ@mail.gmail.com>
To: Jim <jim618@fastmail.co.uk>
Content-Type: multipart/alternative; boundary=f46d04339d1a55857b04d00e54e2
X-Gm-Message-State: ALoCoQlNue8pcqaD++W6UPL4UShEGBuZET3fBWNYWEaH9RyhQnyrQdVCubrG5JTloNOHtGAZYMra
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: 1Tg0up-0008U4-8y
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Roadmap to getting users onto SPV clients
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, 04 Dec 2012 22:24:36 -0000
--f46d04339d1a55857b04d00e54e2
Content-Type: text/plain; charset=ISO-8859-1
Jim, perfect idea with some logo indicating wallet compatibility! This
should cover BIP32 + some mnemonic algorithm for easy transferring of
wallets across various clients.
Btw I asked ThomasV for making BIP from his mnemonic algorithm and he
agreed, so I believe some proposal will be here pretty soon.
slush
On Tue, Dec 4, 2012 at 7:56 PM, Jim <jim618@fastmail.co.uk> wrote:
>
> Also, as BIP32 support is added to clients and codebases then the actual
> variant of software to use to access your wallet will become relatively
> less important. Combined with a standardised seed -> passphrase
> algorithm the user can just type in their long passphrase into any BIP32
> compliant software and click/ buzz/ whirr : there is their wallet. We
> should have a little logo for HD wallet compliance ! :-)
>
>
--f46d04339d1a55857b04d00e54e2
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<br><div class=3D"gmail_extra">Jim, perfect idea with some logo indicating =
wallet compatibility! This should cover BIP32 + some mnemonic algorithm for=
easy transferring of wallets across various clients.</div><div class=3D"gm=
ail_extra">
=A0</div><div class=3D"gmail_extra">Btw I asked ThomasV for making BIP from=
his mnemonic algorithm and he agreed, so I believe some proposal will be h=
ere pretty soon.</div><div class=3D"gmail_extra"><br></div><div class=3D"gm=
ail_extra">
slush<br><br><div class=3D"gmail_quote">On Tue, Dec 4, 2012 at 7:56 PM, Jim=
<span dir=3D"ltr"><<a href=3D"mailto:jim618@fastmail.co.uk" target=3D"_=
blank">jim618@fastmail.co.uk</a>></span> wrote:<blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex">
Also, as BIP32 support is added to clients and codebases then the actual<br=
>
variant of software to use to access your wallet will become relatively<br>
less important. Combined with a standardised seed -> passphrase<br>
algorithm the user can just type in their long passphrase into any BIP32<br=
>
compliant software and click/ buzz/ whirr : there is their wallet. We<br>
should have a little logo for HD wallet compliance ! :-)<br><br></blockquot=
e></div></div>
--f46d04339d1a55857b04d00e54e2--
|
