<p>Bitcoin uses ECDSA for signing and verifying. That is, <code>G</code> is a curve parameter (known constant), <code>k</code> is a number, then the public key is <code>kG</code>, etc. The same mechanism is used in different script types too: Multisig scripts and other P2SH scripts. However, note that it is easier to brute-force a P2SH multisig scripts, which is why the Bech32 format P2SH scripts have longer hashes. Similarly, P2SH scripts might not use signature validation at all.</p>

<p>An HD private key can be encoded in the WIF private key format, and any wallet supporting importing private keys would be able to spend its outputs. This doesn't hold true for other address types.</p>

CC BY-SA 4.0
2020-05-25T15:23:45.933Z
Sorry, but I am unable to link this additional info to the question I asked. Are Multi-sigs & P2SH usual private keys too? (Y/N) I am still learning about how signing of transactions work.
Ashfame
CC BY-SA 4.0
2020-05-25T15:27:55.213Z
A P2SH script may need zero or more private keys. A multisig needs one or more private keys. Those private keys are all of the same type: a large number between 0 and about 2^256.
MCCCS
CC BY-SA 4.0
2020-05-25T15:33:10.683Z
`m-of-n` multisig means there are `n` public keys. For it to be spendable we need private keys of `m` of those public keys so sign. So a multisig is like batch verification of signatures made by private keys.
MCCCS
CC BY-SA 4.0
2020-05-25T15:37:33.723Z
Gotcha, I think it will make more sense with time as I understand signing of transactions. Thank you! I have an additional related question https://bitcoin.stackexchange.com/q/96144/82646 Can you take a look?
Ashfame
CC BY-SA 4.0
2020-05-25T12:35:48.780Z
2020-05-25T12:35:48.780Z
MCCCS
<p>Aside from the fact that HD wallets derive them deterministically, is it correct to state that keys driven at any path or index under BIP32 isn't any different from a private key that's derived randomly in a non-HD wallet?</p>

<p>In other words, its theoretically possible for someone to derive a private key that's at a particular node under your master key in HD wallets, irrespective of how small the probability is, and actually the same probability that there is for generating a private key (non-deterministically) that's already in use by someone else?</p>

<p>Essentially, private key being just a number in a specific range, you can either guess it randomly every single time or have a mechanism of generating random numbers, it essentially means the same thing and is possible to arrive at the same number from either of the ways.</p>

<p>Correct?</p>

CC BY-SA 4.0
2020-05-25T11:35:34.623Z
A private key derived via the HD algorithm is still a usual private key. Does this answer your question?
MCCCS
CC BY-SA 4.0
2020-05-25T11:42:56.840Z
@MCCCS Yes, that's what I am looking to confirm. Are Multi-sigs & P2SH any different or they are also usual private keys?
Ashfame
<private-key>
Are HD wallets private keys any different than regular private keys
Ashfame
# Are HD wallets private keys any different than regular private keys

(Asked by: username_0 on 2020-05-25)

Aside from the fact that HD wallets derive them deterministically, is it correct to state that keys driven at any path or index under BIP32 isn't any different from a private key that's derived randomly in a non-HD wallet?

In other words, its theoretically possible for someone to derive a private key that's at a particular node under your master key in HD wallets, irrespective of how small the probability is, and actually the same probability that there is for generating a private key (non-deterministically) that's already in use by someone else?

Essentially, private key being just a number in a specific range, you can either guess it randomly every single time or have a mechanism of generating random numbers, it essentially means the same thing and is possible to arrive at the same number from either of the ways.

Correct?

**Tags:** private-key

> **Comments:**
> **username_1**: A private key derived via the HD algorithm is still a usual private key. Does this answer your question?  
> **username_0**: @username_1 Yes, that's what I am looking to confirm. Are Multi-sigs & P2SH any different or they are also usual private keys?  

---

## 1 answers

### Answer by username_1 on 2020-05-25. Score: 0 | Accepted answer

Bitcoin uses ECDSA for signing and verifying. That is, `G` is a curve parameter (known constant), `k` is a number, then the public key is `kG`, etc. The same mechanism is used in different script types too: Multisig scripts and other P2SH scripts. However, note that it is easier to brute-force a P2SH multisig scripts, which is why the Bech32 format P2SH scripts have longer hashes. Similarly, P2SH scripts might not use signature validation at all.

An HD private key can be encoded in the WIF private key format, and any wallet supporting importing private keys would be able to spend its outputs. This doesn't hold true for other address types.

> **Comments:**
> **username_0**: Sorry, but I am unable to link this additional info to the question I asked. Are Multi-sigs & P2SH usual private keys too? (Y/N) I am still learning about how signing of transactions work.  
> **username_1**: A P2SH script may need zero or more private keys. A multisig needs one or more private keys. Those private keys are all of the same type: a large number between 0 and about 2^256.  
> **username_1**: `m-of-n` multisig means there are `n` public keys. For it to be spendable we need private keys of `m` of those public keys so sign. So a multisig is like batch verification of signatures made by private keys.  
> **username_0**: Gotcha, I think it will make more sense with time as I understand signing of transactions. Thank you! I have an additional related question https://bitcoin.stackexchange.com/q/96144/82646 Can you take a look?  

---

