<p>There are several different types of bitcoin addresses, which can be derived from the same private key. You can see <a href="https://bitcoin.stackexchange.com/questions/92907/how-many-possible-addresses-per-bitcoin-private-key">this question</a> for some more info about the different types.</p>

<p>So it sounds like your bitcoin-core wallet is creating P2SH-P2WPKH addresses, but then when you imported it into other wallets, they are deriving a P2PKH address. </p>

<p>So the fix is to instruct the wallet that you are importing the address to, to derive the correct address type. Not every wallet will be able to do this, but some of the more feature-rich options out there should be able to do so. </p>

CC BY-SA 4.0
2020-05-02T10:50:24.767Z
but I can't find those L2 addresses mentioned anywhere...
Eagle1
CC BY-SA 4.0
2020-05-02T11:18:31.013Z
The strings starting with `L...` are encoded private keys, not addresses. See: https://bitcoin.stackexchange.com/questions/95648/why-bitcoin-private-key-wif-format-always-be-started-in-k-or-l
chytrik
CC BY-SA 4.0
2020-05-01T22:26:02.833Z
2020-05-01T22:26:02.833Z
chytrik
<p>I used Bitcoin Core 0.19 to create some addresses offline. When I dumped the private keys, I was surprised to see all of them starting with L2… (and the addresses with 3…), but I went for it. I took note of the private keys/addresses.</p>
<p>The next day, I import one of the private keys into another Bitcoin Core wallet, it scans, but the noted address never shows up in my receiving addresses. Instead, it added another address to my list which started with 1B….</p>
<p>So I also added this private key into an Electrum wallet. And surprise, that same address is showing up, not the original one that I got when I created the pair.</p>
<p>What's happening? Is that due to the L2… type?</p>

<bitcoin-core><address-generation><private-key-import>
Different address generated when importing a private key
Eagle1
# Different address generated when importing a private key

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

I used Bitcoin Core 0.19 to create some addresses offline. When I dumped the private keys, I was surprised to see all of them starting with L2… (and the addresses with 3…), but I went for it. I took note of the private keys/addresses.

The next day, I import one of the private keys into another Bitcoin Core wallet, it scans, but the noted address never shows up in my receiving addresses. Instead, it added another address to my list which started with 1B….

So I also added this private key into an Electrum wallet. And surprise, that same address is showing up, not the original one that I got when I created the pair.

What's happening? Is that due to the L2… type?

**Tags:** bitcoin-core, address-generation, private-key-import


---

## 1 answers

### Answer by username_1 on 2020-05-01. Score: 1

There are several different types of bitcoin addresses, which can be derived from the same private key. You can see [this question](https://bitcoin.stackexchange.com/questions/92907/how-many-possible-addresses-per-bitcoin-private-key) for some more info about the different types.

So it sounds like your bitcoin-core wallet is creating P2SH-P2WPKH addresses, but then when you imported it into other wallets, they are deriving a P2PKH address.

So the fix is to instruct the wallet that you are importing the address to, to derive the correct address type. Not every wallet will be able to do this, but some of the more feature-rich options out there should be able to do so.

> **Comments:**
> **username_0**: but I can't find those L2 addresses mentioned anywhere...  
> **username_1**: The strings starting with `L...` are encoded private keys, not addresses. See: https://bitcoin.stackexchange.com/questions/95648/why-bitcoin-private-key-wif-format-always-be-started-in-k-or-l  

---

