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
|
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 7B3FDC013A
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 5 Feb 2021 22:02:30 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by silver.osuosl.org (Postfix) with ESMTP id 63C692E12E
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 5 Feb 2021 22:02:30 +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 n3RH5ftPvWlx
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 5 Feb 2021 22:02:29 +0000 (UTC)
X-Greylist: delayed 00:07:35 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 8D343203AA
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 5 Feb 2021 22:02:27 +0000 (UTC)
Received: from mail.ruggedbytes.com (localhost [127.0.0.1])
by mail.ruggedbytes.com (Postfix) with ESMTPS id E687D260023D;
Fri, 5 Feb 2021 21:54:48 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=simplexum.com;
s=mail; t=1612562088;
bh=aMPtQ9qd0Y6feZJM9F+0m5FrwwD5PkWUG8ubQnWNAHU=;
h=Date:From:To:Cc:Subject:In-Reply-To:References;
b=g71RBf7OXmDMGS+mTXPpWFcP6mGzmfuF/wzlq6O8j1BG3PcRn0BtkcnQkynicIaNa
iX7WPDrKHmFCTPHH5iWHqgqxAqXKsGYbqFFl0jHyNp6BVTYWuiKPl1h1p5rcUXV6hv
4hyjynOsO7pzMvUIKr4wiQH1MNdkf4d6rtQQpg1I=
Date: Fri, 5 Feb 2021 23:00:29 +0100
From: Dmitry Petukhov <dp@simplexum.com>
To: bitcoin-dev@lists.linuxfoundation.org
Message-ID: <20210205230029.4dd6fc4d@simplexum.com>
In-Reply-To: <D962F4E0-E10F-433D-BFC9-3462A8A9CF7A@protonmail.com>
References: <D962F4E0-E10F-433D-BFC9-3462A8A9CF7A@protonmail.com>
Organization: simplexum.com
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Fri, 05 Feb 2021 22:26:38 +0000
Subject: Re: [bitcoin-dev] BIP32/43-based standard for Schnorr signatures &
decentralized identity
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, 05 Feb 2021 22:02:30 -0000
=D0=92 Fri, 05 Feb 2021 17:51:27 +0000
Dr Maxim Orlovsky via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> Testnet path is unhardened from this point & till the end of the
> derivation path: no need to prevent private key leak there,
> simplifies test software (hardened paths require private key access
> for derivation).
I believe this will reduce robustness and will add complexity to the
test software instead. If the derivation path is hardened in 'production
code' and is unhardened in 'test code', then: code paths that depend on
hardened derivation may not be tested; there will be unnecessary
code that will need to deal with 'un-hardening' the paths for test code.
It is much more robust to just change the 'purpose' part of the path,
and leave the rest unchanged.
It is OK to require privkey access to hardened paths in test
software, because the same behaviour is expected in 'production'.
|
