From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from silver.osuosl.org (smtp3.osuosl.org [140.211.166.136]) by lists.linuxfoundation.org (Postfix) with ESMTP id 7B3FDC013A for ; 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 ; 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 ; 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 ; 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 To: bitcoin-dev@lists.linuxfoundation.org Message-ID: <20210205230029.4dd6fc4d@simplexum.com> In-Reply-To: References: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 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'.