[SOLVED] Electrum importing wrong btc address for my private key

[coldice]

I generated custom BTC address via vanitygen. It gave me private key and btc address.
I imported that private key to blockchain.info and imported correct btc address. Now, I want to import that private key to electrum and when I do so it imports some other BTC address. Can someone tell what's the problem here?

Solution:
This problem got solved by visiting https://www.bitaddress.org/
And click on wallet details and enter the private you have then click on view details and it will solve your issue.

Read the replies below to know the reason.

[BitcoinReseller]

if you 're using Electron to collect your bitcoin cash this could help you :
https://bitcointalk.org/index.php?topic=2078292.0

[coldice]

if you 're using Electron to collect your bitcoin cash this could help you :
https://bitcointalk.org/index.php?topic=2078292.0

It's not bitcoin cash. It's simply Bitcoin.

[eXpl0sive]

That's weird.
Two different private keys can generate the same public address, but first time I'm seeing a private key generating two different public addresses.

Have you tried any other wallet like Core or Multibit to see how each wallet behaves?

[HCP]

Was the private key in WIF format and does it start with a "5", a "K" or an "L"?

I vaguely remember reading that importing into b.info did weird things where it was automatically converting uncompressed and compressed addresses for imported keys. If you put your private key into an offline version of BitAddress.org (wallet details tab) do you see both the address from b.info AND the address from Electrum?

[erre]

I generated custom BTC address via vanitygen. It gave me private key and btc address.
I imported that private key to blockchain.info and imported correct btc address. Now, I want to import that private key to electrum and when I do so it imports some other BTC address. Can someone tell what's the problem here?

That's because compressed/uncompressed private key. Insert your privkey in bitaddress.org (use it offline, click on "details"), and import both

[ranochigo]

That's weird.
Two different private keys can generate the same public address, but first time I'm seeing a private key generating two different public addresses.

No. It's impossible to have a single address being derived from two private keys. It is however, possible to have 2 keys derived from the same private key.
How did you generate the vanity address? If you generated it using an online website without using split-key generation, DO NOT use it or send anything to it.

Can you go to bitaddress.org and go to Wallet Details. Key in your private key and see which private key corresponds to your address. Its best to do this offline.

[coldice]

That's weird.
Two different private keys can generate the same public address, but first time I'm seeing a private key generating two different public addresses.

No. It's impossible to have a single address being derived from two private keys. It is however, possible to have 2 keys derived from the same private key.
How did you generate the vanity address? If you generated it using an online website without using split-key generation, DO NOT use it or send anything to it.

Can you go to bitaddress.org and go to Wallet Details. Key in your private key and see which private key corresponds to your address. Its best to do this offline.

I used vanitygen windows based to generate address.

This problem got solved by visiting BitAddress.org
It gave me compressed & uncompressed address + private key.

[eXpl0sive]

That's weird.
Two different private keys can generate the same public address, but first time I'm seeing a private key generating two different public addresses.

No. It's impossible to have a single address being derived from two private keys. It is however, possible to have 2 keys derived from the same private key.

I was reading about this the other day:
https://bitcoin.stackexchange.com/questions/25069/can-two-private-keys-generate-the-same-public-bitcoin-address

Or am I missing something? Noob question.

[coldice]

This problem got solved by visiting BitAddress.org
It gave me compressed & uncompressed address + private key.

Thanks for your help