Multisig derivation paths and xpubs - page 2.

nc50lc

legendary

Activity: 2394

Merit: 5531

Self-proclaimed Genius

Quote from: aesthete2022 on June 28, 2023, 06:18:15 PM

I took what I know to be valid xpubs from my three keys and used the derivation path for nested segwit. However, I can't sign from that quorum. I'm thinking this is probably because the xpubs I am using were not generated by the derivation path I specified?

Perhaps.
If those Nested SegWit extended public keys are derived from your master private key with m/49'/0'/0' path,
But used it in a MultiSig setup and provided the standard path of m/48'/0'/0'/1' (BIP48 - Nested SegWit), then your hardware wallet will derive a different xpub key than what you've provided.

What does the descriptor looks like? You can edit the extended public keys for privacy reasons.
BTW, in Sparrow, you can't use the standard derivation path of BIP49 in a MultiSig setup by design.

aesthete2022

jr. member

Activity: 59

Merit: 31

I have the master fingerprints, so could sign. That’s not the issue. The private keys are stored in my hardware wallets.

blue Snow

legendary

Activity: 1484

Merit: 1024

#SWGT CERTIK Audited

Quote from: aesthete2022 on June 28, 2023, 06:18:15 PM

Ok, so I'm learning through doing here. I took what I know to be valid xpubs from my three keys and used the derivation path for nested segwit. However, I can't sign from that quorum. I'm thinking this is probably because the xpubs I am using were not generated by the derivation path I specified?

You can't sign because you don't have the private key, So is not because of different xpubs or public keys.

aesthete2022

jr. member

Activity: 59

Merit: 31

Ok, so I'm learning through doing here. I took what I know to be valid xpubs from my three keys and used the derivation path for nested segwit. However, I can't sign from that quorum. I'm thinking this is probably because the xpubs I am using were not generated by the derivation path I specified?

witcher_sense

legendary

Activity: 2310

Merit: 4313

🔐BitcoinMessage.Tools🔑

Quote from: aesthete2022 on June 27, 2023, 05:12:05 PM

My question is, can each device in a multisig setup have a different derivation path? I always thought every device had to refer to the same one.

A derivation scheme is just one of the ways to organize the storage or relationship of keys: each key in such a scheme will have its own place within this huge hierarchy, but they all can be derived from the common ancestor. The entropy (single signature wallet) or a bunch of entropies (multi-signature wallet) serve as an entry point from which to generate information needed for wallet creation and signing of transaction data. While you are absolutely free to determine how initial entropy and derived keys should relate to each other, it is advisable to follow standards described in BIPs and similar specifications because this helps wallet software to remain interoperable and interchangeable.

o_e_l_e_o

legendary

Activity: 2268

Merit: 18509

Quote from: aesthete2022 on June 27, 2023, 05:12:05 PM

My question is, can each device in a multisig setup have a different derivation path?

Absolutely.

The derivation path tells your software how to turn a seed phrase in to an extended private key and extended public key. So if you use m/49/0/3, this tells the wallet to derive the extended key at the 50th index, then use that to derive the extended key at the 1st index, then use that to derive the extended key at the 4th index. This final extended key is the xprv/xpub used in your multi-sig wallet.

It doesn't matter if every seed phrase in your multi-sig uses a different derivation path - each one will end up with an xprv/xpub which are combined to create your multi-sig. In fact, the wallet does not even need to know the derivation paths at all. Indeed, there doesn't even need to be a seed phrase in the first place. You could just generate an xprv directly from some entropy source.

As long as you feed it it the same xprvs/xpubs, it will always generate the same addresses, regardless of where these xprvs/xpubs came from.

nc50lc

legendary

Activity: 2394

Merit: 5531

Self-proclaimed Genius

Quote from: aesthete2022 on June 27, 2023, 05:12:05 PM

My question is, can each device in a multisig setup have a different derivation path? I always thought every device had to refer to the same one.

Technically, it's not an issue since each of your MultiSig Addresses are derived from each cosigner's individual child keys.
The derivation path is just a way to tell the client a way to derive child keys.

Signing wont be an issue either as long as the client know how to derive those child keys from the master key.

As for Sparrow, it's using "Descriptors" to take note of the derivation path for each cosigner master keys.

blue Snow

legendary

Activity: 1484

Merit: 1024

#SWGT CERTIK Audited

Quote from: aesthete2022 on June 27, 2023, 05:12:05 PM

My question is, can each device in a multisig setup have a different derivation path? I always thought every device had to refer to the same one.

I believe every wallet has a different costume path, so be careful about that. we've discussed it here: https://bitcointalksearch.org/topic/m.54314948

aesthete2022

jr. member

Activity: 59

Merit: 31

My current multisig (with a third-party provider) uses m/49/0/3. I took the derivation paths and xpubs from that and created a smaller multisig quorum, which has signed fine.

aesthete2022

jr. member

Activity: 59

Merit: 31

I am having trouble wrapping my head around derivation paths in multisig setups. I had a multisig wallet with the derivation path m/49/0/3 (i.e., each key used that path). I wanted to swap a key to set up a new wallet. I used Sparrow and, even though the new device used the derivation path m/48/0/0/2 and the other two had m/49/0/3, it still generated the multisig wallet (i.e., Sparrow detected no error).

My question is, can each device in a multisig setup have a different derivation path? I always thought every device had to refer to the same one.

Topic: Multisig derivation paths and xpubs - page 2. (Read 349 times)