<p>According to Bip32 - Bip44 - Bip49(Segwit) You can generate many public keys using one master private/public key.</p>

<p>I don't know which deriving path Bitpay using but Electrum using path 44 for legacy bitcoin addresses and 49 for Segwit addresses.</p>

<p>As @pebwindkraft answer Bitpay maybe providing you an extended private key so generating address progress become like that in electrum when you are providing Bip44 extended private key:</p>

<p>Bip44 Extended Key -> Bip44 Extended Key -> Public Keys -> index</p>

<p>instead of: </p>

<p>Master Private Key -> Bip44 Extended Key -> Public Keys -> index</p>

<p><strong>Addresses generated in one application can be visible in second one?</strong>
Yes if they are using same deriving path.</p>

<p>Your Bitpay transactions should appear in Electrum.</p>

<p><strong>Where can I read about rules of generation keys and addresses described in simple words?</strong>
<a href="https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki" rel="nofollow noreferrer">Bitcoin improvement protocol 44</a></p>

<p>Mastering Bitcoin Book is helpful.</p>

CC BY-SA 3.0
2018-01-30T17:15:08.207Z
In this BitPay wallet there is used derivation strategy: BIP44, and kind of address: P2PKH.
Daniel
CC BY-SA 3.0
2018-01-30T11:49:26.227Z
2018-01-30T12:01:16.650Z
2018-01-30T12:01:16.650Z
Tailer
<p>One private key can generate two different bitcoin addresses. That depends on the ECDSA logic and encoding schemes used. Probably you have heard about compressed and uncompressed keys. The details are deep under the hood, and requires some reading, e.g. Andreas book "Mastering Bitcoin" (2nd edition), which is <a href="http://chimera.labs.oreilly.com/books/1234000001802/index.html" rel="nofollow noreferrer">online available</a>. Chapter 4 and 5 are the relevant ones. </p>

<p>I am not sure, how bitpay creates his keys, but I have already imported privkeys into Electrum as well. As long as I was working with compressed keys in my source wallet, Electrum showed the same. However, this gets different, when you extract keys from bip39/44 wallets. From looking at their website, I think bitpay has only a function to extract an extended private key, that is for sure different from a "std private key". An extended private key is used in HD wallets, to generate a set of xpub keys, that can be used e.g. on websites, to avoid re-use of keys. And depending how the seed is implemented, wallets are not always compatible to each other. This might be the case, why you see different addresses. Electrum uses [m/44'/0'/a'] as xpriv path for derivation. But maybe there is a way, look for samuelt33's comment on 5 Aug 2017 on the <a href="https://github.com/bitpay/copay/issues/5859" rel="nofollow noreferrer">webpage here</a>. </p>

<p>On standard privkeys and pubkeys, there is a longer thread here: <a href="https://bitcoin.stackexchange.com/questions/69315/how-are-compressed-pubkeys-generated/69322?noredirect=1#comment80498_69322">How are compressed PubKeys generated?</a></p>

CC BY-SA 3.0
2018-01-30T11:57:00.757Z
"I think bitpay has only a function to extract an extended private key" Good catch!
Tailer
CC BY-SA 3.0
2018-01-30T11:48:49.997Z
2018-01-30T11:48:49.997Z
pebwindkraft
<p>I created wallet in BitPay. I have public and private keys.</p>

<p>Then I created wallet in Electrum using existing private key.</p>

<p>Now wallet in electrum has other public key than in BitPay but
the same private key.</p>

<p>Is it ok? Addresses generated in one application can be visible 
in second one? Where can I read about rules of generation keys and
addresses described in simple words?</p>

<p>I generated wallet in electrum using the same private key second time
and i obtained the same public key like last time I generated on electrum, but not the same like in BitPay wallet. I do not understand why.</p>

CC BY-SA 3.0
2018-01-30T08:42:00.767Z
Are you import private keys to the electrum wallet with the seed phrase?
Roman Kiselenko
CC BY-SA 3.0
2018-01-30T08:57:25.500Z
No. I selected "Use public or private keys", then I pasted private key only.
Daniel
<private-key><electrum><mnemonic-seed><copay><bip44>
One private key generate many public keys?
Daniel
# One private key generate many public keys?

(Asked by: username_0 on 2018-01-30)

I created wallet in BitPay. I have public and private keys.

Then I created wallet in Electrum using existing private key.

Now wallet in electrum has other public key than in BitPay but
the same private key.

Is it ok? Addresses generated in one application can be visible
in second one? Where can I read about rules of generation keys and
addresses described in simple words?

I generated wallet in electrum using the same private key second time
and i obtained the same public key like last time I generated on electrum, but not the same like in BitPay wallet. I do not understand why.

**Tags:** private-key, electrum, mnemonic-seed, copay, bip44

> **Comments:**
> **username_1**: Are you import private keys to the electrum wallet with the seed phrase?  
> **username_0**: No. I selected "Use public or private keys", then I pasted private key only.  

---

## 2 answers

### Answer by username_2 on 2018-01-30. Score: 1 | Accepted answer

According to Bip32 - Bip44 - Bip49(Segwit) You can generate many public keys using one master private/public key.

I don't know which deriving path Bitpay using but Electrum using path 44 for legacy bitcoin addresses and 49 for Segwit addresses.

As @username_3 answer Bitpay maybe providing you an extended private key so generating address progress become like that in electrum when you are providing Bip44 extended private key:

Bip44 Extended Key -> Bip44 Extended Key -> Public Keys -> index

instead of:

Master Private Key -> Bip44 Extended Key -> Public Keys -> index

**Addresses generated in one application can be visible in second one?**
Yes if they are using same deriving path.

Your Bitpay transactions should appear in Electrum.

**Where can I read about rules of generation keys and addresses described in simple words?**
[Bitcoin improvement protocol 44](https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki)

Mastering Bitcoin Book is helpful.

> **Comments:**
> **username_0**: In this BitPay wallet there is used derivation strategy: BIP44, and kind of address: P2PKH.  

---

### Answer by username_3 on 2018-01-30. Score: 1

One private key can generate two different bitcoin addresses. That depends on the ECDSA logic and encoding schemes used. Probably you have heard about compressed and uncompressed keys. The details are deep under the hood, and requires some reading, e.g. Andreas book "Mastering Bitcoin" (2nd edition), which is [online available](http://chimera.labs.oreilly.com/books/1234000001802/index.html). Chapter 4 and 5 are the relevant ones.

I am not sure, how bitpay creates his keys, but I have already imported privkeys into Electrum as well. As long as I was working with compressed keys in my source wallet, Electrum showed the same. However, this gets different, when you extract keys from bip39/44 wallets. From looking at their website, I think bitpay has only a function to extract an extended private key, that is for sure different from a "std private key". An extended private key is used in HD wallets, to generate a set of xpub keys, that can be used e.g. on websites, to avoid re-use of keys. And depending how the seed is implemented, wallets are not always compatible to each other. This might be the case, why you see different addresses. Electrum uses [m/44'/0'/a'] as xpriv path for derivation. But maybe there is a way, look for samuelt33's comment on 5 Aug 2017 on the [webpage here](https://github.com/bitpay/copay/issues/5859).

On standard privkeys and pubkeys, there is a longer thread here: [How are compressed PubKeys generated?](https://bitcoin.stackexchange.com/questions/69315/how-are-compressed-pubkeys-generated/69322?noredirect=1#comment80498_69322)

> **Comments:**
> **username_2**: "I think bitpay has only a function to extract an extended private key" Good catch!  

---

