Date: Sat, 4 Jul 2020 00:10:50 +0500
From: Dmitry Petukhov <dp@simplexum.com>
To: Dmitry Petukhov via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
Message-ID: <20200704001050.3ffbbd7e@simplexum.com>
In-Reply-To: <20200703215344.349376cd@simplexum.com>
References: <20200702212839.2d59e435@simplexum.com>
 <20200703143945.kvuczb7z4vr6ehwr@ganymede>
 <20200703215344.349376cd@simplexum.com>
Organization: simplexum.com
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_/cwT+jVUOu9AdE3Su.gcfFQJ";
 protocol="application/pgp-signature"; micalg=pgp-sha256
Subject: Re: [bitcoin-dev] BIP draft: BIP32 Path Templates
Precedence: list

--Sig_/cwT+jVUOu9AdE3Su.gcfFQJ
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable


=D0=92 Fri, 3 Jul 2020 21:53:44 +0500
Dmitry Petukhov via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
wrote:

> The format for the path templates described in the presented BIP draft
> aims to provide a building block for interoperability between various
> hardware and software vendors in regard to this particular task of
> specifying derivation path restrictions.

One example of an interoperability workflow might be:

A software vendor that utilizes custom derivation paths in their
schemes create a "profile" that contains the constraints on the paths
(and possibly other parameters, but this is out of scope of the
proposal) for their particular scheme. In a simple case it might just
be a path template string provided in the documentation.

A user of a software solution from that vendor takes a hardware wallet
that supports path templates (or richer "profiles") and installs the
profile for that solution into hardware wallet. In a simple case, the
user just pastes a path template string into some configuration utility
program and then confirms the setting on-device.

The device statrts to enforce the constraints specified in the template
(or "profile"), and the software solution works as intended by the
software vendor.


--Sig_/cwT+jVUOu9AdE3Su.gcfFQJ
Content-Type: application/pgp-signature
Content-Description: Цифровая подпись OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEsXo1u6GHOVeE4qazIwHSa9wVFg0FAl7/groACgkQIwHSa9wV
Fg0H0Q/9EADAyb87hj1hB9OIrAtgdF4emgWK4lrdnqnYUk9O+OlRCUUfnyJpoHTU
4MjLv8nQIM0CT8sFZI9RHN9tv8RY8Nqt4S6HHuSaEMBTGU9MkvPLiIP8HnccAYb1
OaA7GWHfBuYvBsg0L7lDt/4k1XgZZMctBR9KGLFS9UDOvuCQNPw+TfAMnMgsz+n3
FtYAX3GL3SuU12+1j2WZ5Z0pIuFROzQmsiB45CLFXBrmTiER/iW4W6vxsnKoOpvt
WpOF9DQiWfpdB9y/8FB+RgMcb7f7XM3tKtQPE9ZLhQB4eiNJeNnLU9ua1UWASVyF
KSgqk0ZSu3N/uB2r7CPfJZjVsvdYzL8MW1kdQvVIyN/z7oQUQKLeriaQZPgJUUtF
sbh+bpEl16Zn71H1q1ssPsxaQX6JAizte8kN5uQE3xsxSw4KEtvP2T0dCn3ONc9x
YKaUO57G57eJv+TeaUKIqvyg8QEAeTfduw2nxe+t57CSxqX+I1cP1+fYW4QvnNPn
HYM+wTMplKIeoVvJZtbYXiKUpG+VRpP0TCAUiG2tDWgp+KAPQ6jZJ9ed9X9GFEUD
6Xhcck7Llbn4snTD1S7sE8xgDsjlPbmt/7JtUtCmkF6UxAvHFGaZTP7sd0WCCJJK
TEweTMMQsGuqwyvBoqXgozNAsbHI7BAb0r1PiYknk8DIspIwzzs=
=xDgv
-----END PGP SIGNATURE-----

--Sig_/cwT+jVUOu9AdE3Su.gcfFQJ--