1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
|
Return-Path: <dp@simplexum.com>
Received: from silver.osuosl.org (smtp3.osuosl.org [140.211.166.136])
by lists.linuxfoundation.org (Postfix) with ESMTP id 2C1E2C0733
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 3 Jul 2020 19:07:56 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by silver.osuosl.org (Postfix) with ESMTP id 053CC266BD
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 3 Jul 2020 19:07:56 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
Received: from silver.osuosl.org ([127.0.0.1])
by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id F2vn2WaOqPoJ
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 3 Jul 2020 19:07:55 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from mail.ruggedbytes.com (mail.ruggedbytes.com [88.99.30.248])
by silver.osuosl.org (Postfix) with ESMTPS id CB3C5203C8
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 3 Jul 2020 19:07:54 +0000 (UTC)
Received: from mail.ruggedbytes.com (localhost [127.0.0.1])
by mail.ruggedbytes.com (Postfix) with ESMTPS id 2E3EA260023D;
Fri, 3 Jul 2020 19:07:52 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=simplexum.com;
s=mail; t=1593803272;
bh=BgeLz7mn64jsOfwJNXm13mhV3iXw9B52j27HaHDh7n0=;
h=Date:From:To:Cc:Subject:In-Reply-To:References;
b=K6qyTGSytzhqFUAfW5/ktmRjerc4ar0ldQlEkxuHGb8JqPYXQPFZ9kMPbpZ7hzjBz
za7ifm3ga1Z714sr8GU+VWK5BOQ0+ydeMcWN3y7D+vP3uBmr/UKV8UdEX3rnI5TWME
I488s+T5n1K5I54Vl0WBMmoDQwlZL9SU0AG+78SQ=
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
X-Mailman-Approved-At: Fri, 03 Jul 2020 19:20:27 +0000
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 <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jul 2020 19:07:56 -0000
--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--
|
