Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of me.com
	designates 17.172.220.236 as permitted sender)
	client-ip=17.172.220.236; envelope-from=jeanpaulkogelman@me.com;
	helo=st11p02mm-asmtp001.mac.com; 
MIME-version: 1.0
Content-type: multipart/alternative;
	boundary="Boundary_(ID_8Tr4drEudGhoHcC13OkNTA)"
To: Gary Rowe <g.rowe@froot.co.uk>
From: Jean-Paul Kogelman <jeanpaulkogelman@me.com>
Date: Wed, 12 Mar 2014 19:35:23 +0000 (GMT)
Message-id: <8349e85f-838a-4d93-9302-48b12af03940@me.com>
In-reply-to: <CAKm8k+3bbhN=Kf2thvtakA7EGcTHDn1ssQm-+Fwf3hAAQmndTQ@mail.gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] [RFC] Proposal: Base58 encoded HD Wallet
 root key with optional encryption
Precedence: list


--Boundary_(ID_8Tr4drEudGhoHcC13OkNTA)
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: quoted-printable

=0A=0AOn Mar 12, 2014, at 09:49 AM, Gary Rowe <g.rowe@froot.co.uk> wrote:=0A=
=0AJean-Paul, it may be worth noting that the BIP39 word list is integrate=
d into Bitcoinj so will likely become the de facto standard for Android, T=
rezor web and several desktop wallets. Anyone deviating from that word lis=
t would likely find themselves in an isolated pocket.=0A=0ARegarding the t=
imestamp, MultiBit HD uses a simple timestamp of "number of days since mid=
night of Bitcoin genesis block in UTC with modulo 97 checksum appended". T=
hus a new seed generated on 27 January 2014 would have "1850/01" as its ch=
ecksum.=0A=A0=0AI'm a bit confused, are you changing the way the checksum =
is calculated, or fudging the input seed to produce a specific checksum? O=
r is checksum in this case another value calculated over the mnemonic list=
?=0A=0A=0AWhen creating a new wallet the users are tested that they have w=
ritten the timestamp down along with the associated 12/18/24 words.=0A=0AS=
o this is specific to MultiBit HD? Wouldn't it be better to include this i=
nto the BIP?=A0=0A=0A=

--Boundary_(ID_8Tr4drEudGhoHcC13OkNTA)
Content-type: multipart/related;
	boundary="Boundary_(ID_5/EzsZMLDUlc8+Y9jmAMoA)"; type="text/html"


--Boundary_(ID_5/EzsZMLDUlc8+Y9jmAMoA)
Content-type: text/html; CHARSET=US-ASCII
Content-transfer-encoding: quoted-printable

<html><body><div><br><br>On Mar 12, 2014, at 09:49 AM, Gary Rowe &lt;g.rowe@froot.co.u=
k&gt; wrote:<br><br></div><div><blockquote type=3D"cite"><div class=3D"msg=
-quote"><div dir=3D"ltr">Jean-Paul, it may be worth noting that the BIP39 =
word list is integrated into Bitcoinj so will likely become the de facto s=
tandard for Android, Trezor web and several desktop wallets. Anyone deviat=
ing from that word list would likely find themselves in an isolated pocket=
.<div><br></div><div>Regarding the timestamp, MultiBit HD uses a simple ti=
mestamp of "number of days since midnight of Bitcoin genesis block in UTC =
with modulo 97 checksum appended". Thus a new seed generated on 27 January=
 2014 would have "1850/01" as its checksum. </div></div></div></blockquote=
><span>&nbsp;</span></div><div>I'm a bit confused, are you changing the wa=
y the checksum is calculated, or fudging the input seed to produce a speci=
fic checksum? Or is checksum in this case another value calculated over th=
e mnemonic list?</div><div><br></div><div><br><blockquote type=3D"cite"><d=
iv class=3D"msg-quote"><div dir=3D"ltr"><div>When creating a new wallet th=
e users are tested that they have written the timestamp down along with th=
e associated 12/18/24 words.</div><div></div></div></div></blockquote><spa=
n><div><span><br></span></div>So this is specific to MultiBit HD? Wouldn't=
 it be better to include this into the BIP?&nbsp;</span></div><div><br></d=
iv></body></html>=

--Boundary_(ID_5/EzsZMLDUlc8+Y9jmAMoA)--

--Boundary_(ID_8Tr4drEudGhoHcC13OkNTA)--