From: Robert Spigler <RobertSpigler@protonmail.ch>
To: "bitcoin-dev@lists.linuxfoundation.org"
<bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] Signature and Script Independent Hierarchy for Deterministic Wallets.
Date: Sun, 14 Mar 2021 01:51:15 +0000 [thread overview]
Message-ID: <7z-e5nLz7_TTCW9LAKAOgEWBliTvJkq7BTpm0ARmpD_LHp9S4ETlkK1M5jfG8klRSHQiuZHl6zEhqIjbsVPgcvo12Qg6bI2wp28m01x9lXU=@protonmail.ch> (raw)
[-- Attachment #1: Type: text/plain, Size: 1867 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 3251 bytes --]
next reply other threads:[~2021-03-14 1:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-14 1:51 Robert Spigler [this message]
2021-03-14 15:13 [bitcoin-dev] Signature and Script Independent Hierarchy for Deterministic Wallets SomberNight
2021-03-14 20:46 ` Robert Spigler
2021-03-17 7:26 ` Craig Raw
2021-03-18 15:29 ` Jochen Hoenicke
2021-03-18 20:44 ` Robert Spigler
2021-03-18 21:42 ` Robert Spigler
2021-03-19 7:54 ` Craig Raw
2021-03-19 8:59 ` Robert Spigler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='7z-e5nLz7_TTCW9LAKAOgEWBliTvJkq7BTpm0ARmpD_LHp9S4ETlkK1M5jfG8klRSHQiuZHl6zEhqIjbsVPgcvo12Qg6bI2wp28m01x9lXU=@protonmail.ch' \
--to=robertspigler@protonmail.ch \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox