Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of me.com
	designates 17.172.220.240 as permitted sender)
	client-ip=17.172.220.240; envelope-from=jeanpaulkogelman@me.com;
	helo=st11p02mm-asmtp005.mac.com; 
Content-type: multipart/signed;
	boundary="Apple-Mail=_6468106F-7B10-4AB8-821A-965DCCD1AC9E";
	protocol="application/pgp-signature"; micalg=pgp-sha512
MIME-version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Jean-Paul Kogelman <jeanpaulkogelman@me.com>
In-reply-to: <CAAS2fgSyegH8y1dYcijCSPLsC54mxeSNsN+3FQVDo5R9tWwAwQ@mail.gmail.com>
Date: Fri, 15 Nov 2013 19:09:07 -0800
Message-id: <BF62F0D0-1D13-4F19-A8F6-F588F3060A64@me.com>
References: <CANEZrP37a=EH+1P47opH0E-1TG9ozgw_1NzecJpRRJsMaZRLOw@mail.gmail.com>
	<81f77484-3ca9-40a7-a999-884260b26be5@me.com>
	<CAAS2fgSyegH8y1dYcijCSPLsC54mxeSNsN+3FQVDo5R9tWwAwQ@mail.gmail.com>
To: Gregory Maxwell <gmaxwell@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] [RFC] Proposal: Base58 encoded HD Wallet
 master seed with optional encryption
Precedence: list


--Apple-Mail=_6468106F-7B10-4AB8-821A-965DCCD1AC9E
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_A995914C-4047-4CD9-8AFC-104CEE1E35EF"


--Apple-Mail=_A995914C-4047-4CD9-8AFC-104CEE1E35EF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


I've made no changes since the last time I've mentioned it here on the =
list (when the BIP procedures were being discussed).

The last changes are:

01-10-2013 - Expanded the salt to be prefix + date + checksum and =
renamed 'master seed' to 'root key'.
24-07-2013 - Added user selectable KDF + parameters, encoded in the =
prefix.
22-07-2013 - Added 2 byte creation date field, as a result, the prefix =
is expanded to 3 bytes.

The biggest difference between this proposal and BIP38 is that BIP38 =
allows a 3rd party to generate the encrypted private key + confirmation =
code from a passphrase code. Since this proposal is about encrypting a =
random value that's fed into HMAC-SHA512 and the presence of a partial =
hash of the root address, that's not possible.


>> https://bitcointalk.org/index.php?topic=3D258678
>=20
> Greetings.  Any recent progress on this?
>=20
> Do we believe this proposal can replace BIP38?  If not, what are the
> limitations that would prevent it from doing so?


--Apple-Mail=_A995914C-4047-4CD9-8AFC-104CEE1E35EF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><div><br></div><div>I've made no changes since the =
last time I've mentioned it here on the list (when the BIP procedures =
were being discussed).</div><div><br></div><div>The last changes =
are:</div><div><br></div><div>01-10-2013 - Expanded the salt to be =
prefix + date + checksum and renamed 'master seed' to 'root =
key'.</div><div>24-07-2013 - Added user selectable KDF + parameters, =
encoded in the prefix.</div><div>22-07-2013 - Added 2 byte creation date =
field, as a result, the prefix is expanded to 3 =
bytes.</div><div><br></div><div>The biggest difference between this =
proposal and BIP38 is that BIP38 allows a 3rd party to generate the =
encrypted private key + confirmation code from a passphrase code. Since =
this proposal is about encrypting a random value that's fed into =
HMAC-SHA512 and the presence of a partial hash of the root address, =
that's not =
possible.</div><div><br></div><div><br></div><div><br></div><div><br></div=
><div><blockquote type=3D"cite"><blockquote type=3D"cite"><a =
href=3D"https://bitcointalk.org/index.php?topic=3D258678">https://bitcoint=
alk.org/index.php?topic=3D258678</a></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Greetings. =
&nbsp;Any recent progress on this?<br><br>Do we believe this proposal =
can replace BIP38? &nbsp;If not, what are the<br>limitations that would =
prevent it from doing so?<br></blockquote></div><br></body></html>=

--Apple-Mail=_A995914C-4047-4CD9-8AFC-104CEE1E35EF--

--Apple-Mail=_6468106F-7B10-4AB8-821A-965DCCD1AC9E
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJShuHTAAoJEG93Vo4Z7tpFMCUQALxtU61LKbTDS+pu3/fNaO6t
jmplwBh0oLAPRdD/GtNJa3LZG6W19dxKxm8g/jwHF+xIEwmpMk9dpXXqeDBmh9W+
05Gfu7RniIZrk8PNBiDUAUp6XorS/wYHAsdM5PkAv2CZ07lz+yzczPiHDoaW0JjJ
5wol6ORUqQHE9iC/maq6iHWux6CXAdJ6XxdFo/Pnd43lEecZ+ErFWwTEKXPBWOV6
ZD5KYv/JoR7YjPYwmWnwYdCvZOMu0d5PSFXup4l1PsZqWwSyWs3iu7m+CPXdUhMe
Tft+Zl0mGKDxqkDUj5xPK7NjGVLmTEXG9+nNrT+Y0mmRu+R8O+Od7m8bhFEWtcin
FW+mn45RNbJfVjQo1jX+dhFyLUEdqTWY37WRY2i1wHQALZJ3hzYg8aB2vcOo+nA8
r1CB7ANcgaFCsid+yV4RPOW8NMrLacrFNfaInsNCf6GFrYeJwm1rKCF8AZEqBB9B
pyBHJdIX9HI6Nb/ZWmXvmP9H/Z414+gEhJLUPNkFR9t4rd8gaWwxvROsmh+2QM01
k0Cn5iFrPZJIDbe3nJV3ONgZLr1qfdJEEakq/ezM2Oi7qDnY2uR11OvER1pEZ70r
x2IXXSXMmBpeaCaAyvTvWWpBcAnemIUMREIvZbktIPfdT3YMQOhXpJPM6y7SOqOj
Tgj4gKG3/SIYdeWUhfUw
=J8NA
-----END PGP SIGNATURE-----

--Apple-Mail=_6468106F-7B10-4AB8-821A-965DCCD1AC9E--