From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1W5MyB-0006qx-Up for bitcoin-development@lists.sourceforge.net; Mon, 20 Jan 2014 22:05:24 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of midnightdesign.ws designates 50.87.144.70 as permitted sender) client-ip=50.87.144.70; envelope-from=boydb@midnightdesign.ws; helo=gator3054.hostgator.com; Received: from gator3054.hostgator.com ([50.87.144.70]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1W5MyB-0001oC-1K for bitcoin-development@lists.sourceforge.net; Mon, 20 Jan 2014 22:05:23 +0000 Received: from [74.125.82.50] (port=56433 helo=mail-wg0-f50.google.com) by gator3054.hostgator.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.80) (envelope-from ) id 1W5My4-0000Sj-PF for bitcoin-development@lists.sourceforge.net; Mon, 20 Jan 2014 16:05:16 -0600 Received: by mail-wg0-f50.google.com with SMTP id l18so7417976wgh.29 for ; Mon, 20 Jan 2014 14:05:14 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=w8+KEEaC09HuSOLzlu8H/cNlm8xQRrZunKmMOKU+Roc=; b=SCw3op68TPcJrHahWGqhLMvGHeFlNvfwFXrneORyk6AnR3sE4ig8xyFxQH2jCI6c4i 7dJ8cozryX+6VX4eYbDzdGlvovdsVfkgBaQsuGrEWA73ymeM5FK2lR0i0LqkyZheqWMk oh9K1T1y+GUfENoXKFz6BUq4GBLKwe5cQUsp/nDaXMSRQbLQVFebc6PMqZSph5DqWNBJ pg5eLIR9yMAkvPhRicxl9PZN8gkYVtuTgog40sP5RQoirbMYFKMA6fU+s2+jP/mJiVje 2Uj7q1MBosoXcaNPe5/LF3cLhLwiVFLXXs/6yr1yWMPpncSH+5U+rz4wRob9TrKk/9i8 5zQQ== X-Gm-Message-State: ALoCoQnSshzK9Xk6vF6/2JPSCuOfNguz53MzbpGz0nCJyNtz2CEJQGzEAUQ+Q9SCBXzCV7XHUFRE MIME-Version: 1.0 X-Received: by 10.180.81.38 with SMTP id w6mr11542201wix.27.1390255514867; Mon, 20 Jan 2014 14:05:14 -0800 (PST) Received: by 10.227.12.193 with HTTP; Mon, 20 Jan 2014 14:05:14 -0800 (PST) In-Reply-To: References: Date: Mon, 20 Jan 2014 16:05:14 -0600 Message-ID: From: Brooks Boyd To: bitcoin-development@lists.sourceforge.net Content-Type: multipart/alternative; boundary=f46d044288c01c741c04f06e1631 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - gator3054.hostgator.com X-AntiAbuse: Original Domain - lists.sourceforge.net X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - midnightdesign.ws X-BWhitelist: no X-Source-IP: 74.125.82.50 X-Source: X-Source-Args: X-Source-Dir: X-Source-Sender: (mail-wg0-f50.google.com) [74.125.82.50]:56433 X-Source-Auth: midnight X-Email-Count: 1 X-Source-Cap: bWlkbmlnaHQ7bWlkbmlnaHQ7Z2F0b3IzMDU0Lmhvc3RnYXRvci5jb20= X-Spam-Score: -0.5 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 SPF_HELO_PASS SPF: HELO matches SPF record -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message X-Headers-End: 1W5MyB-0001oC-1K Subject: Re: [Bitcoin-development] BIP0039: Final call 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: Mon, 20 Jan 2014 22:05:24 -0000 --f46d044288c01c741c04f06e1631 Content-Type: text/plain; charset=ISO-8859-1 On Mon, Jan 20, 2014 at 11:42 AM, slush wrote: > Hi all, > > during recent months we've reconsidered all comments which we received > from the community about our BIP39 proposal and we tried to meet all > requirements for such standard. Specifically the proposal now doesn't > require any specific wordlist, so every client can use its very own list of > preferred words. Generated mnemonic can be then applied to any other > BIP39-compatible client. Please follow current draft at > https://github.com/trezor/bips/blob/master/bip-0039.mediawiki. > So, because the [mnemonic]->[bip32 root] is just hashing, you've effectively made your "mnemonic sentence" into a brainwallet? Since every mnemonic sentence can now lead to a bip32 root, and only the client that created the mnemonic can verify the mnemonic passes its checksum (assuming all clients use different wordlists, the only client that can help you if you fat-finger the sentence is the client that created it)? Brooks --f46d044288c01c741c04f06e1631 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

= On Mon, Jan 20, 2014 at 11:42 AM, slush <slush@centrum.cz> wr= ote:
Hi all,

during recent months we'v= e reconsidered all comments which we received from the community about our = BIP39 proposal and we tried to meet all requirements for such standard. Spe= cifically the proposal now doesn't require any specific wordlist, so ev= ery client can use its very own list of preferred words. Generated mnemonic= can be then applied to any other BIP39-compatible client. Please follow cu= rrent draft at=A0https://github.com/trezor/bips/blob/maste= r/bip-0039.mediawiki.


So, because the [mnemonic]->[bip32 root] is just= hashing, you've effectively made your "mnemonic sentence" in= to a brainwallet? Since every mnemonic sentence can now lead to a bip32 roo= t, and only the client that created the mnemonic can verify the mnemonic pa= sses its checksum (assuming all clients use different wordlists, the only c= lient that can help you if you fat-finger the sentence is the client that c= reated it)?

Brooks

--f46d044288c01c741c04f06e1631--