Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id AABE7A64 for ; Tue, 5 Sep 2017 17:04:17 +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 62C583D4 for ; Tue, 5 Sep 2017 17:04:17 +0000 (UTC) Received: from gin.localnet (unknown [208.184.212.126]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id 79F1D38A1C3E; Tue, 5 Sep 2017 17:03:45 +0000 (UTC) X-Hashcash: 1:25:170905:bitcoin-dev@lists.linuxfoundation.org::AVErd3UlLJPczsKH:aSQwh X-Hashcash: 1:25:170905:thomasv@electrum.org::3pxfE4VCyoUlX4aP:blCAL From: Luke Dashjr To: bitcoin-dev@lists.linuxfoundation.org, Thomas Voegtlin Date: Tue, 5 Sep 2017 13:03:39 -0400 User-Agent: KMail/1.13.7 (Linux/4.12.1+; KDE/4.14.32; x86_64; ; ) References: <43636dd6-ab9e-da15-59ae-f31eb11ff7ff@electrum.org> In-Reply-To: <43636dd6-ab9e-da15-59ae-f31eb11ff7ff@electrum.org> 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-1" Content-Transfer-Encoding: 7bit Message-Id: <201709051303.43410.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: Tue, 05 Sep 2017 17:04:17 -0000 On Tuesday 05 September 2017 06:25:16 Thomas Voegtlin via bitcoin-dev wrote: > I have heard the argument that xpub/xprv serialization is a format for > keys, and that it should not be used to encode how these keys are used. > However, the very existence of version bytes, and the fact that they are > used to signal whether keys will be used on testnet or mainnet goes > against that argument. > > If we do not signal the script type in the version bytes, I believe > wallet developers are going to use dirtier tricks, such as the bip32 > child number field in combination with bip43/bip44/bip49. I think it makes more sense to use a child number field for this purpose. It seems desirable to use the same seed for all different script formats... As you note, xpub\xprv are already being used for both P2PKH and P2SH. It really doesn't make sense to differentiate segwit specifically. Luke