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 ) 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 ; 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: <1354650998.21742.140661161849669.1371855A@webmail.messagingengine.com> From: slush Date: Tue, 4 Dec 2012 22:23:59 +0000 X-Google-Sender-Auth: OxfWnmtD7F7qtju3RMFwAgt9lg8 Message-ID: To: Jim 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" 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 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
Jim, perfect idea with some logo indicating = wallet compatibility! This should cover BIP32 + some mnemonic algorithm for= easy transferring of wallets across various clients.
=A0
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.

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--