Return-Path: Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136]) by lists.linuxfoundation.org (Postfix) with ESMTP id 01F32C000D for ; Thu, 18 Feb 2021 18:52:28 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp3.osuosl.org (Postfix) with ESMTP id E55A560650 for ; Thu, 18 Feb 2021 18:52:27 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from smtp3.osuosl.org ([127.0.0.1]) by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A8zm5QQXBj6m for ; Thu, 18 Feb 2021 18:52:27 +0000 (UTC) Received: by smtp3.osuosl.org (Postfix, from userid 1001) id 4CCF06065F; Thu, 18 Feb 2021 18:52:27 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0 Received: from mail2.protonmail.ch (mail2.protonmail.ch [185.70.40.22]) by smtp3.osuosl.org (Postfix) with ESMTPS id 79AD560650 for ; Thu, 18 Feb 2021 18:52:25 +0000 (UTC) Date: Thu, 18 Feb 2021 18:52:12 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail; t=1613674341; bh=YmZXjp8Oqp+6579SxY4c2ZwK1gCJqGIBrByi4V8XWiY=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=g3qARxcEfNBN1nEDKd5i6vcRaiWJ8uPqe0+XTmI1hI5SXRSipiqCwS/XNFScj5EA/ jJf1oo2nxhcE/p4WB5OyJ/6eU8RrDAQVXzLMCEHJuWZB+FpcamRc1PFgS4R8ZJVK2U A760vFQjnOlK43p5WK/tCL9ADz+25X2GZ7DFHdcw= To: Adam Back From: Dr Maxim Orlovsky Reply-To: Dr Maxim Orlovsky Message-ID: In-Reply-To: References: <5096768E-3A77-4CD8-AC22-105CA63152A7@protonmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Thu, 18 Feb 2021 19:36:58 +0000 Cc: Bitcoin Protocol Discussion 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: Thu, 18 Feb 2021 18:52:28 -0000 Hi Adam, Commenting on your question: > With segWit vs pre-SegWit didn't wallets just select and standardize > on a different HD derivation path? >=20 > Is there something else needed than a Schnorr derivation path? The general accepted practice (defined in BIP43) is to define a dedicated p= urpose field for each kind of key derivation and address encoding. There is= a dedicated purpose for pre-SegWit, SegWit, multisigs =E2=80=94 and now a = purpose for Schnorr sigs/Taproot outputs is needed. That is why I brought f= orward this proposal, which addresses exactly this need - and also will sup= port at the same time multisigs and pre-Taproot outputs, making all previou= sly used purpose fields redundant, simplifying future wallets. Kind regards, Maxim