Return-Path: Received: from fraxinus.osuosl.org (smtp4.osuosl.org [140.211.166.137]) by lists.linuxfoundation.org (Postfix) with ESMTP id 1A201C0733 for ; Fri, 3 Jul 2020 14:40:34 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by fraxinus.osuosl.org (Postfix) with ESMTP id 0305587CB4 for ; Fri, 3 Jul 2020 14:40:34 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from fraxinus.osuosl.org ([127.0.0.1]) by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VBGgPCh4CjiL for ; Fri, 3 Jul 2020 14:40:33 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from newmail.dtrt.org (li1228-87.members.linode.com [45.79.129.87]) by fraxinus.osuosl.org (Postfix) with ESMTPS id 697F587CAB for ; Fri, 3 Jul 2020 14:40:33 +0000 (UTC) Received: from harding by newmail.dtrt.org with local (Exim 4.92) (envelope-from ) id 1jrMrf-0001Wy-K1; Fri, 03 Jul 2020 10:40:31 -0400 Date: Fri, 3 Jul 2020 10:39:45 -0400 From: "David A. Harding" To: Dmitry Petukhov , Bitcoin Protocol Discussion Message-ID: <20200703143945.kvuczb7z4vr6ehwr@ganymede> References: <20200702212839.2d59e435@simplexum.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="uhnjrwdpgbag5dht" Content-Disposition: inline In-Reply-To: <20200702212839.2d59e435@simplexum.com> User-Agent: NeoMutt/20180716 Subject: Re: [bitcoin-dev] BIP draft: BIP32 Path Templates X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jul 2020 14:40:34 -0000 --uhnjrwdpgbag5dht Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 02, 2020 at 09:28:39PM +0500, Dmitry Petukhov via bitcoin-dev w= rote: > I think there should be standard format to describe constraints for > BIP32 paths. >=20 > I present a BIP draft that specifies "path templates" for BIP32 paths: >=20 > https://github.com/dgpv/bip32_template_parse_tplaplus_spec/blob/master/bi= p-path-templates.mediawiki Hi Dmitry, How do path templates compare to key origin identification[1] in output script descriptors? Could you maybe give a specfic example of how path templates might be used? Are they for backups? Multisig wallet coordination? Managing data between software transaction construction and hardware device signing? Thanks, -Dave [1] https://github.com/bitcoin/bitcoin/blob/master/doc/descriptors.md#key-o= rigin-identification (See earlier in the doc for examples) --uhnjrwdpgbag5dht Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEgxUkqkMp0LnoXjCr2dtBqWwiadMFAl7/QzEACgkQ2dtBqWwi adPjWw//fZHnHx+r2SxDLwlW9g8143bWe4zy3612+tP9NU0AiN4bwurn0d8ACWIA VJRLGikqLZhV0yM7WVii53cO7k4Zf++gGYCB2PbLSLp1ZN7uUxcIgxgcLnM7ZQyq rg0YO/ysuKztuLJ4oo2WYcts3RrKTno20PS9GooErt9Ro+qTaHgvsunWIhf5tGGn 248qJJaqSrwPUSTnLhMAxg8ZvZeomQIBCRoC1DY2/VTriaEqb/dSMs25LKZCncW3 9uu/e6QtHjitPP49YRoiElhttnpneQCff6ng7kjkKwnL2xyhi8aHee7ltgueiZgm NnApLFGSKdZmy3cbSyVge2AJEebbL0oHJ7naaYl3FAFQFXCDUMRzpCPGdWmDXg77 wiMHQHt1lHmlnaCOE6k0MyGk75PN9o+xwyfg0y++oer7BYNNPl9MoLAqynr3scfY VZaGnZUaqpVYwwDEoS78c/0zu16DlH55cqqjsiuxL3w8a1bovsyvzlx/vGuxLePp IAsRwBE/Z6wpOOYkqak0IFItWLUhzKMph031e7xcyPwEhRR7f8fSGTM56hRUeSEH ZEncScE7qD3g/FtbC47sc2MTGdci/biL1tV2MOgS3ItsDPFPxxMdgtCLP2y+zu+7 xSW+IrJGhz2KiFMYQ/cNibnlHdQOshdmaE82Tdp2CiMTgtdHUj0= =H0xe -----END PGP SIGNATURE----- --uhnjrwdpgbag5dht--