📅 Original date posted:2021-02-18
📝 Original message:Hi Adam,
Commenting on your question:
> With segWit vs pre-SegWit didn't wallets just select and standardize
> on a different HD derivation path?
>
> Is there something else needed than a Schnorr derivation path?
The general accepted practice (defined in BIP43) is to define a dedicated purpose field for each kind of key derivation and address encoding. There is a dedicated purpose for pre-SegWit, SegWit, multisigs — and now a purpose for Schnorr sigs/Taproot outputs is needed. That is why I brought forward this proposal, which addresses exactly this need - and also will support at the same time multisigs and pre-Taproot outputs, making all previously used purpose fields redundant, simplifying future wallets.
Kind regards,
Maxim
Dr Maxim Orlovsky [ARCHIVE] /
npub1a8…rpwgy
2023-06-07 18:28:30
in reply to nevent1q…y97l
Author Public Key
npub1a80jcetgws9xmu7wnylvekpymw2acym2psjpp03e0chmhq38pc8qwrpwgyPublished at
2023-06-07 18:28:30Event JSON
{
"id": "f3d11a98969e109351876290782524727c862d937aad75f67205b56f857366a3",
"pubkey": "e9df2c6568740a6df3ce993eccd824db95dc136a0c2410be397e2fbb82270e0e",
"created_at": 1686162510,
"kind": 1,
"tags": [
[
"e",
"d2c8b65efdaee73f5c5fd62fe4b915d4fcf718277dfab7951f3a1bbc122c404e",
"",
"root"
],
[
"e",
"60f8860bf415d56656cec38896b3583caa287e623ab1dd22301f087554104222",
"",
"reply"
],
[
"p",
"e9df2c6568740a6df3ce993eccd824db95dc136a0c2410be397e2fbb82270e0e"
]
],
"content": "📅 Original date posted:2021-02-18\n📝 Original message:Hi Adam,\n\nCommenting on your question:\n\n\u003e With segWit vs pre-SegWit didn't wallets just select and standardize\n\u003e on a different HD derivation path?\n\u003e \n\u003e Is there something else needed than a Schnorr derivation path?\n\nThe general accepted practice (defined in BIP43) is to define a dedicated purpose field for each kind of key derivation and address encoding. There is a dedicated purpose for pre-SegWit, SegWit, multisigs — and now a purpose for Schnorr sigs/Taproot outputs is needed. That is why I brought forward this proposal, which addresses exactly this need - and also will support at the same time multisigs and pre-Taproot outputs, making all previously used purpose fields redundant, simplifying future wallets.\n\nKind regards,\nMaxim",
"sig": "e4393733d90064c46aa0b39a01d8cd3194a24b5f7f99492d1846cedca08825ba7b40155cc7ef33f254436558672942f33782204b46710faf18a285129d39c1c8"
}