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-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WXVvX-0000XF-JL for bitcoin-development@lists.sourceforge.net; Tue, 08 Apr 2014 13:18:59 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.223.169 as permitted sender) client-ip=209.85.223.169; envelope-from=pieter.wuille@gmail.com; helo=mail-ie0-f169.google.com; Received: from mail-ie0-f169.google.com ([209.85.223.169]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WXVvW-0004Vq-Ca for bitcoin-development@lists.sourceforge.net; Tue, 08 Apr 2014 13:18:59 +0000 Received: by mail-ie0-f169.google.com with SMTP id to1so876652ieb.0 for ; Tue, 08 Apr 2014 06:18:53 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.42.120.15 with SMTP id d15mr2758422icr.35.1396963133092; Tue, 08 Apr 2014 06:18:53 -0700 (PDT) Received: by 10.50.141.135 with HTTP; Tue, 8 Apr 2014 06:18:52 -0700 (PDT) In-Reply-To: References: <53344FF8.7030204@gk2.sk> Date: Tue, 8 Apr 2014 15:18:52 +0200 Message-ID: From: Pieter Wuille To: slush Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: -1.6 (-) 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 (pieter.wuille[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1WXVvW-0004Vq-Ca Cc: Bitcoin Dev 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:18:59 -0000 I still don't understand the purpose of cointype. If you don't want to risk reusing the same keys across different currencies, just don't use the same seed or the same account? That is purely a client-side issue. If the consensus is to add the cointype anyway, can we fix it to be equal to the 4-byte magic in the serialization (after setting the high bit to true)? That way there aren't two 4-byte magic codes that need to be defined for each, and at the same time make it obvious from the serialized form what it is for. On Tue, Apr 8, 2014 at 2:43 PM, slush wrote: > After some off-list discussion about details with wallet developers, it > seems that structure > > m/'/'// > > fulfill requirements of all wallet developers around, including myTrezor, > Electrum, Multibit, Wallet32 and other software is willing to adapt once > anything will be standardized (i.e. they don't care). > > Because I think that everybody told their comments to the topic already and > because it seems that there's quite wide agreement on that, I would like to > close the discussion and finally implement these paths into our software. > > Cheers, > Marek > > > On Fri, Mar 28, 2014 at 3:59 PM, slush wrote: >> >> I agree that 'version' field of bip32 is not necessary and xpriv/xpub >> should be enough for all cases; there's actually no need to use different >> BIP32 roots for different altcoins. >> >> I'm happily using one xpub for Bitcoin/Testnet/Litecoin at once, and by >> having the "cointype" distinction in the bip32 path itself, I'm sure that I >> don't reuse the same pubkey across blockchains which may be a privacy issue >> otherwise. >> >> Marek >> >> >> On Thu, Mar 27, 2014 at 5:28 PM, Pieter Wuille >> wrote: >>> >>> On Thu, Mar 27, 2014 at 5:21 PM, Pavol Rusnak wrote: >>> > Cointype in path is for separation purposes, not for identification. >>> >>> I don't understand what that gains you. >>> >>> -- >>> Pieter >>> >>> >>> ------------------------------------------------------------------------------ >>> _______________________________________________ >>> Bitcoin-development mailing list >>> Bitcoin-development@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development >> >> > > > ------------------------------------------------------------------------------ > Put Bad Developers to Shame > Dominate Development with Jenkins Continuous Integration > Continuously Automate Build, Test & Deployment > Start a new project now. Try Jenkins in the cloud. > http://p.sf.net/sfu/13600_Cloudbees > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development >