<p>HD is really about back-ups and wallet recovery, a multisig address can be created from <strong>any</strong> public keys regardless how/where they were generated. Heck you could use the same public key 3 times, although I wouldn't recommend it I'm just trying to prove a point.</p>
<p>To answer your exact questions:</p>
<blockquote>
<p>How does the generation of the other 2 Master Keys happen?</p>
</blockquote>
<p>Do you want 2 more master keys, or do you just think you need them? Additional master seeds are not necessary, but if you want more master keys then create additional HD seeds.</p>
<blockquote>
<p>What do these keys share?</p>
</blockquote>
<p>The master keys? They shouldn't share anything, again not relevant to creating a multisig address.</p>
<blockquote>
<p>When new private keys are generated by the user are new keys derived
also on the server?</p>
</blockquote>
<p>Private keys are not needed to create a multisig address, just the public keys. If you only want one HD seed to back-up, then use different accounts for each key pair. By accounts I'm referring to the derivation path, for example Account 1 Index 0: <code>m/0/0/0/0</code>, Account 2 Index 0: <code>m/0/0/1/0</code>, Account 3 Index 0: <code>m/0/0/2/0</code>, this would produce 3 key pairs, all with an index of 0 and the public key of each would be used to create the multisig address.</p>

CC BY-SA 4.0
2020-09-22T02:34:07.733Z
2020-09-22T02:34:07.733Z
m1xolyd1an
<p>Private keys are simply 256bit random numbers. A seed phrase is simply a different way to generate 256bits of randomness in a more human-readable way.</p>
<p>So, to answer your questions</p>
<blockquote>
<p>How does the generation of the other 2 Master Keys happen?</p>
</blockquote>
<p>You need to securely generate a 256bit random number. This can be done in software.  You can also generate them in a HSM.  Regardless, for a secure, multi-sig setup, these keys must be generated on different machines, and ideally using different random number generation schemes.</p>
<blockquote>
<p>What do these keys share?</p>
</blockquote>
<p>For your example, they should share nothing.  The user's key and the service/backup keys should be as independent as possible, and hopefully never be active on the same machine.</p>
<blockquote>
<p>When new private keys are generated by the user are new keys derived also on the server?</p>
</blockquote>
<p>Each master private key must be kept on separate machines, otherwise, you're nullifying most of your multi-signature benefits.  Derivations using the private key should only be done when as needed for signing, and the derivations must be independent for each key.</p>
<p>Derivation of the public key can be done on any machine (it's public information).  This can help with generating derived multi-sig addresses that can be computed anywhere.</p>

CC BY-SA 4.0
2020-09-23T18:27:44.540Z
So the generations happen independently. Do they work as if they were independent wallets? I don't understand how they can agree to sign a transaction.
MaXbeMan
CC BY-SA 4.0
2020-09-22T14:55:21.447Z
2020-09-22T14:55:21.447Z
mike belshe
<p>I need clarification on multisig hd wallets. Let's imagine we have a 2/3 multisig. The first key is generated by the user on a mobile wallet, the second is kept on a server while the third is off-line (for emergencies). In an hd wallet the seed is generated from the seed phrase and, from this, the Master Private Key.</p>
<blockquote>
<p>How does the generation of the other 2 Master Keys happen?</p>
</blockquote>
<blockquote>
<p>What do these keys share?</p>
</blockquote>
<blockquote>
<p>When new private keys are generated by the user are new keys derived also on the server?</p>
</blockquote>

<wallet><multi-signature><bip32-hd-wallets><p2sh>
Clarifications on hd multisig wallet
MaXbeMan
# Clarifications on hd multisig wallet

(Asked by: username_0 on 2020-09-21)

I need clarification on multisig hd wallets. Let's imagine we have a 2/3 multisig. The first key is generated by the user on a mobile wallet, the second is kept on a server while the third is off-line (for emergencies). In an hd wallet the seed is generated from the seed phrase and, from this, the Master Private Key.

> How does the generation of the other 2 Master Keys happen?

> What do these keys share?

> When new private keys are generated by the user are new keys derived also on the server?

**Tags:** wallet, multi-signature, bip32-hd-wallets, p2sh


---

## 2 answers

### Answer by username_1 on 2020-09-22. Score: 1

HD is really about back-ups and wallet recovery, a multisig address can be created from **any** public keys regardless how/where they were generated. Heck you could use the same public key 3 times, although I wouldn't recommend it I'm just trying to prove a point.

To answer your exact questions:

> How does the generation of the other 2 Master Keys happen?

Do you want 2 more master keys, or do you just think you need them? Additional master seeds are not necessary, but if you want more master keys then create additional HD seeds.

> What do these keys share?

The master keys? They shouldn't share anything, again not relevant to creating a multisig address.

> When new private keys are generated by the user are new keys derived
> also on the server?

Private keys are not needed to create a multisig address, just the public keys. If you only want one HD seed to back-up, then use different accounts for each key pair. By accounts I'm referring to the derivation path, for example Account 1 Index 0: `m/0/0/0/0`, Account 2 Index 0: `m/0/0/1/0`, Account 3 Index 0: `m/0/0/2/0`, this would produce 3 key pairs, all with an index of 0 and the public key of each would be used to create the multisig address.


---

### Answer by username_2 on 2020-09-22. Score: 1

Private keys are simply 256bit random numbers. A seed phrase is simply a different way to generate 256bits of randomness in a more human-readable way.

So, to answer your questions

> How does the generation of the other 2 Master Keys happen?

You need to securely generate a 256bit random number. This can be done in software. You can also generate them in a HSM. Regardless, for a secure, multi-sig setup, these keys must be generated on different machines, and ideally using different random number generation schemes.

> What do these keys share?

For your example, they should share nothing. The user's key and the service/backup keys should be as independent as possible, and hopefully never be active on the same machine.

> When new private keys are generated by the user are new keys derived also on the server?

Each master private key must be kept on separate machines, otherwise, you're nullifying most of your multi-signature benefits. Derivations using the private key should only be done when as needed for signing, and the derivations must be independent for each key.

Derivation of the public key can be done on any machine (it's public information). This can help with generating derived multi-sig addresses that can be computed anywhere.

> **Comments:**
> **username_0**: So the generations happen independently. Do they work as if they were independent wallets? I don't understand how they can agree to sign a transaction.  

---

