From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Z67Ep-0005Dx-Ma for bitcoin-development@lists.sourceforge.net; Sat, 20 Jun 2015 01:06:27 +0000 Received: from bi.petersson.at ([46.4.24.198] helo=petersson.at) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1Z67Eo-0000VL-DP for bitcoin-development@lists.sourceforge.net; Sat, 20 Jun 2015 01:06:27 +0000 Received: from [192.168.1.11] (unknown [213.47.22.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: andreas) by petersson.at (Postfix) with ESMTPSA id 0B88123812C9 for ; Sat, 20 Jun 2015 03:14:14 +0200 (CEST) Message-ID: <5584BA85.3050008@petersson.at> Date: Sat, 20 Jun 2015 02:57:41 +0200 From: Andreas Petersson User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: <55847E98.3050307@gem.co> <558488D0.50904@envrin.com> <5584A667.2050205@gem.co> In-Reply-To: <5584A667.2050205@gem.co> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -0.3 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.3 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1Z67Eo-0000VL-DP Subject: Re: [Bitcoin-development] Alternate HD path structure: BIP, blog, or wat? 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: Sat, 20 Jun 2015 01:06:27 -0000 >m/##'/0'/99'/0' > >where 99 is the identifier for, say, counterparty What is stopping you from using m/44'/9'/a'/c/i as descibed here: http://doc.satoshilabs.com/slips/slip-0044.html to avoid having an internal mapping from 9'-> 0' to find out what blockchain to query, this sounds like it should be trivial for any wallet= =2E