Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WXWYy-000126-6K for bitcoin-development@lists.sourceforge.net; Tue, 08 Apr 2014 13:59:48 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmx.de designates 212.227.17.22 as permitted sender) client-ip=212.227.17.22; envelope-from=thomasv1@gmx.de; helo=mout.gmx.net; Received: from mout.gmx.net ([212.227.17.22]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1WXWYw-0004yY-Vy for bitcoin-development@lists.sourceforge.net; Tue, 08 Apr 2014 13:59:44 +0000 Received: from [192.168.1.27] ([84.101.32.222]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0M9NIY-1Wi1UU34HO-00CmAV for ; Tue, 08 Apr 2014 15:59:36 +0200 Message-ID: <534400C8.2010600@gmx.de> Date: Tue, 08 Apr 2014 15:59:36 +0200 From: Thomas Voegtlin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: <53344FF8.7030204@gk2.sk> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K0:H2UDDraOyq9gOl1S7L3i21OFgZ6QbbjE5leZ0GeBvj1wxex4VxY NcGiXk0/vkh62Yda9zHN47tDwi+Pzx+JXOJwH1/AUTlzAkijP9e5CRkOnN78pAJYxCsMPGB YDfeipfzuVLaAON+BSGNuC9/pQSGQ53a8NJnCzZ0nxujLqHXVnGWMguw5+Z9YwgrvDGyflE dQIeMqZEg+ggRJpMuPPMQ== X-Spam-Score: -1.2 (-) 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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (thomasv1[at]gmx.de) -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [212.227.17.22 listed in list.dnswl.org] -0.0 SPF_PASS SPF: sender matches SPF record 0.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in digit (thomasv1[at]gmx.de) X-Headers-End: 1WXWYw-0004yY-Vy Subject: Re: [Bitcoin-development] New BIP32 structure 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, 08 Apr 2014 13:59:50 -0000 +1 I would prefer that solution... Le 08/04/2014 15:53, Pieter Wuille a écrit : > I see the cause of our disagreement now. > > You actually want to share a single BIP32 tree across different > currency types, but do it in a way that guarantees that they never use > the same keys. > > I would have expected that different chains would use independent > chains, and have serializations encode which chain they belong to. > > Let me offer an alternative suggestion, which is compatible with the > original default BIP32 structure: > * You can use one seed across different chains, but the master nodes > are separate. > * To derive the master node from the seed, the key string "Bitcoin > seed" is replaced by something chain-specific. > * Every encoded node (including master nodes) has a chain-specific > serialization magic. > > This is in practice almost the same as your suggestion, except that > the m/cointype' in m/cointype'/account'/change/n is replaced by > different masters. The only disadvantage I see is that you do not have > a way to encode the "super master" that is the parent of all > chain-specific masters. You can - and with the same security > properties - encode the seed, though. >