Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 0C221BED for ; Thu, 7 Sep 2017 19:02:52 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from zinan.dashjr.org (zinan.dashjr.org [192.3.11.21]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id B2D9D1B3 for ; Thu, 7 Sep 2017 19:02:51 +0000 (UTC) Received: from gin.localnet (unknown [IPv6:2607:f598:b1e8:fa00:c22a:d1fd:1758:a3d7]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id CBABD38A1308; Thu, 7 Sep 2017 19:02:20 +0000 (UTC) X-Hashcash: 1:25:170907:bitcoin-dev@lists.linuxfoundation.org::Aq1Tk4Q/8i46axfQ:gqab X-Hashcash: 1:25:170907:kabuto@samouraiwallet.com::7zBuXQovo/=Y5JJ=:db3n X-Hashcash: 1:25:170907:thomasv@electrum.org::r41AQTQX/YMHOhj9:b24SO From: Luke Dashjr To: bitcoin-dev@lists.linuxfoundation.org, Kabuto Samourai Date: Thu, 7 Sep 2017 15:02:17 -0400 User-Agent: KMail/1.13.7 (Linux/4.12.1+; KDE/4.14.32; x86_64; ; ) References: In-Reply-To: X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F X-PGP-Key-ID: BD02942421F4889F X-PGP-Keyserver: hkp://pgp.mit.edu MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201709071502.19413.luke@dashjr.org> X-Spam-Status: No, score=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED, RP_MATCHES_RCVD 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: bip32 version bytes for segwit scripts 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 19:02:52 -0000 On Tuesday 05 September 2017 15:00:04 Kabuto Samourai via bitcoin-dev wrote: > I think Luke and Thomas may be talking past one another. When exporting a > root master HD seed, encoding the {x,y,z}{pub,prv} distinctions makes no > sense, as the root seed should derive all paths for all coins. Wallets may > need additional code to discover which paths have been used when importing > a root seed. But when exporting / importing an account-level seed for > watch-only and receive address generation, changing the serialization > version bytes is appropriate and (in our view) essential to avoid loss of > funds. In that case, I think we should go back to the proposal I started with in March... https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-March/013726.html This handles not only simple HD seeds, but also multisig HD and such. Luke