Date: Thu, 18 Feb 2021 18:52:12 +0000
To: Adam Back <adam@cypherspace.org>
From: Dr Maxim Orlovsky <orlovsky@protonmail.com>
Reply-To: Dr Maxim Orlovsky <orlovsky@protonmail.com>
Message-ID: <FFB823E1-97FF-4BA9-948A-EF293D56C0FD@protonmail.com>
In-Reply-To: <CALqxMTG1MG+PvLfSLRqsa_yHBQOdu7BOqBjm4_ShSsB3CNSCOA@mail.gmail.com>
References: <D962F4E0-E10F-433D-BFC9-3462A8A9CF7A@protonmail.com>
 <mCGqNxZZgiKEO8gbRcHFUxcU5fGBMWMfkJdapM2Nuhe0gemmqXRfnyqqaRY70UFea1udvQe0LIYt9Ps3lsgDArVHlfeMOWacXqZ7ZiGzMTU=@wuille.net>
 <5096768E-3A77-4CD8-AC22-105CA63152A7@protonmail.com>
 <CALqxMTG1MG+PvLfSLRqsa_yHBQOdu7BOqBjm4_ShSsB3CNSCOA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP32/43-based standard for Schnorr signatures &
	decentralized identity
Precedence: list

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