Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 9EC96266 for ; Thu, 7 Sep 2017 04:29:34 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from relay6-d.mail.gandi.net (relay6-d.mail.gandi.net [217.70.183.198]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 1FFEC12A for ; Thu, 7 Sep 2017 04:29:34 +0000 (UTC) X-Originating-IP: 85.180.249.43 Received: from [192.168.1.26] (x55b4f92b.dyn.telefonica.de [85.180.249.43]) (Authenticated sender: thomasv@electrum.org) by relay6-d.mail.gandi.net (Postfix) with ESMTPSA id C46F8FB88B for ; Thu, 7 Sep 2017 06:29:32 +0200 (CEST) To: bitcoin-dev@lists.linuxfoundation.org References: <0d405f5d-c0a4-bad7-b6c3-08ba4424bf17@satoshilabs.com> From: Thomas Voegtlin Message-ID: <8b4831a4-791e-c03e-baa4-16d9e5ead442@electrum.org> Date: Thu, 7 Sep 2017 06:29:32 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <0d405f5d-c0a4-bad7-b6c3-08ba4424bf17@satoshilabs.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW autolearn=disabled version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Subject: Re: [bitcoin-dev] Proposal: Extended serialization format for BIP-32 wallets X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Sep 2017 04:29:34 -0000 On 07.09.2017 00:29, Pavol Rusnak via bitcoin-dev wrote: > The discussion about changing bip32 version bytes for SegWit got me > thinking and I ended up with what I think is the best proposal: > > https://github.com/satoshilabs/slips/blob/master/slip-0032.md > > (It is hosted in SL repo for now, but if there is will, I would love to > have this added to BIP repo as an extension to BIP32) > > Feel free to comment. > Your proposal forces wallets to use the derivation path in order to determine the type of output script. it will work only in the context of BIP43. Therefore, it should not be proposed as a BIP32 improvement, but as a improvement of BIP43. A solution is still needed to wallets who do not wish to use BIP43