đź“… Original date posted:2021-03-13
đź“ť Original message:Hello,
I am working on a draft BIP for a signature and script independent hierarchy for deterministic wallets.
I believe with the implementation of descriptor wallets, the typical use case of of a BIP43 `purpose’` level per script type is redundant. The differentiation of separate BIPs for multisignature derivation paths, with BIP45 and “BIP” 48, is also redundant – with path levels such as `cosigner_index` and `script_type`. Descriptors can set the order of the public keys with `multi` or have them sorted lexicographically with `sortedmulti`.
I don’t believe we should be mixing keys and scripts in the same layer. The wallet should create extended private/public keys independent of the script or signature type, whereas the descriptor language tells wallets to watch (single or multi-sig) outputs with the specified public keys.
The BIP defines the following 5 levels in the BIP32 path:
m / purpose' / coin_type' / account' / change / address_index
It is crucial that the `account’` level is increased for each new wallet joined or private/public keys created; for both privacy and cryptographic purposes. For example, in multisignature wallets, before sending a new key record to a coordinator, the wallet must increment the `account’` level. Before creating it's own single signature wallet, the `account’` level must again be incremented. This prevents key reuse - across single signature and multisignature wallets, across ECDSA and Schnorr signatures, and inbetween the same wallet types.
For full details, please see the BIP here: https://github.com/Rspigler/bips-1/blob/Sane_Mulitisg_deriv/Modern%20Derivation%20Standard.mediawiki
Please see the PR here: https://github.com/Rspigler/bips-1/pull/1
Looking forward to comments.
Thank you,
Robert Spigler
Personal Fingerprint: BF0D 3C08 A439 5AC6 11C1 5395 B70B 4A77 F850 548F
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20210314/1cdda930/attachment.html>;
Robert Spigler [ARCHIVE] /
npub1jv…n4h4q
2023-06-07 18:30:44
in reply to nevent1q…59fj
Author Public Key
npub1jvdxs20huh95a9c3870fexu3t9l75ewathejfupw26r7n3uh847shn4h4qPublished at
2023-06-07 18:30:44Event JSON
{
"id": "a7923e5e4ec3e581df96b0d3df79971a79198fb42d6cd4679fe8400ec4637844",
"pubkey": "931a6829f7e5cb4e97113f9e9c9b91597fea65dd5df324f02e5687e9c7973d7d",
"created_at": 1686162644,
"kind": 1,
"tags": [
[
"e",
"913d86f3b70d7097b85745228f5bcf5ab314d109dd3d1e78a2db64c8151cf10d",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2021-03-13\n📝 Original message:Hello,\n\nI am working on a draft BIP for a signature and script independent hierarchy for deterministic wallets.\n\nI believe with the implementation of descriptor wallets, the typical use case of of a BIP43 `purpose’` level per script type is redundant. The differentiation of separate BIPs for multisignature derivation paths, with BIP45 and “BIP” 48, is also redundant – with path levels such as `cosigner_index` and `script_type`. Descriptors can set the order of the public keys with `multi` or have them sorted lexicographically with `sortedmulti`.\n\nI don’t believe we should be mixing keys and scripts in the same layer. The wallet should create extended private/public keys independent of the script or signature type, whereas the descriptor language tells wallets to watch (single or multi-sig) outputs with the specified public keys.\n\nThe BIP defines the following 5 levels in the BIP32 path:\n\nm / purpose' / coin_type' / account' / change / address_index\n\nIt is crucial that the `account’` level is increased for each new wallet joined or private/public keys created; for both privacy and cryptographic purposes. For example, in multisignature wallets, before sending a new key record to a coordinator, the wallet must increment the `account’` level. Before creating it's own single signature wallet, the `account’` level must again be incremented. This prevents key reuse - across single signature and multisignature wallets, across ECDSA and Schnorr signatures, and inbetween the same wallet types.\n\nFor full details, please see the BIP here: https://github.com/Rspigler/bips-1/blob/Sane_Mulitisg_deriv/Modern%20Derivation%20Standard.mediawiki\n\nPlease see the PR here: https://github.com/Rspigler/bips-1/pull/1\n\nLooking forward to comments.\n\nThank you,\n\nRobert Spigler\n\nPersonal Fingerprint: BF0D 3C08 A439 5AC6 11C1 5395 B70B 4A77 F850 548F\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20210314/1cdda930/attachment.html\u003e",
"sig": "fa534df075869e574c82fb3f6346fabcc6be199cd1278a2152e47604d9e628e8a81ce00bed089abc17cec312e5998a3fe91f95dc998f771447b1b0162bba5821"
}