Topic: cannot input bitaddress.org private key into Electrum 1.9.5 (Read 1421 times)
A friend of mine reported the same importation problem with Electrum on Mac OSX 10.8
Worked for me in 1.9.5 Windows 7 x64.
I could not import this, windows 7 x64 electrum 1.9.5
Anyone else?Are you also running Win x64? (The test I made was on 32-bit)
I could not import this, windows 7 x64 electrum 1.9.5
Anyone else?
I could not import this, windows 7 x64 electrum 1.9.5
Working flawless in Portable 1.9.5 Windows 7
Hello,
I have contacted the OP to inspect the issue. He was able to import the private keys on blockchain.info just fine.
He then gave me one of the private keys, which imported perfectly fine in both Electrum 1.9.2 and 1.9.5 on Linux.
However, when trying to import the private key on the Windows client 1.9.5, it fails.
Can someone else using Windows 7/8 please try to import the following private key to see if you can reproduce this?
5JB5KGpo2MeSgkKbRJrwoNVQPViuohZYa8NiURWqQt3bdcEsF6k
I have contacted the OP to inspect the issue. He was able to import the private keys on blockchain.info just fine.
He then gave me one of the private keys, which imported perfectly fine in both Electrum 1.9.2 and 1.9.5 on Linux.
However, when trying to import the private key on the Windows client 1.9.5, it fails.
Can someone else using Windows 7/8 please try to import the following private key to see if you can reproduce this?
5JB5KGpo2MeSgkKbRJrwoNVQPViuohZYa8NiURWqQt3bdcEsF6k
Don't have Win 7/8 at hand, but at least on Win XP it works for me (1.9.5):
Hello,
I have contacted the OP to inspect the issue. He was able to import the private keys on blockchain.info just fine.
He then gave me one of the private keys, which imported perfectly fine in both Electrum 1.9.2 and 1.9.5 on Linux.
However, when trying to import the private key on the Windows client 1.9.5, it fails.
Can someone else using Windows 7/8 please try to import the following private key to see if you can reproduce this?
5JB5KGpo2MeSgkKbRJrwoNVQPViuohZYa8NiURWqQt3bdcEsF6k
I have contacted the OP to inspect the issue. He was able to import the private keys on blockchain.info just fine.
He then gave me one of the private keys, which imported perfectly fine in both Electrum 1.9.2 and 1.9.5 on Linux.
However, when trying to import the private key on the Windows client 1.9.5, it fails.
Can someone else using Windows 7/8 please try to import the following private key to see if you can reproduce this?
5JB5KGpo2MeSgkKbRJrwoNVQPViuohZYa8NiURWqQt3bdcEsF6k
On Windows 7 8 (sorry, corrected) operating system, I installed Electrum 1.9.5. Back on November 23 I generated a paper wallet at bitaddress.org. I sent 0.121 btc from my coinbase account to the public key of this wallet.
Today I have imported the private key into Electrum and am getting 'The following inputs could not be imported'. This seems to not be just an issue with electrum - I had the same issue with a public wallet I created at blockchain.info.
I have spent some funds in the past from bitaddress.org paper wallets before without issues, so I considered them trustworthy.
Can anyone shed light on this, or private message me as appropriate?
thanks
Edit: I just scanned the qr code of the private key on this paper wallet into a qr code readeer and copy/pasted that into electrum private key import and also received the same error. This was to rule out all possibility of transcription error.
Today I have imported the private key into Electrum and am getting 'The following inputs could not be imported'. This seems to not be just an issue with electrum - I had the same issue with a public wallet I created at blockchain.info.
I have spent some funds in the past from bitaddress.org paper wallets before without issues, so I considered them trustworthy.
Can anyone shed light on this, or private message me as appropriate?
thanks
Edit: I just scanned the qr code of the private key on this paper wallet into a qr code readeer and copy/pasted that into electrum private key import and also received the same error. This was to rule out all possibility of transcription error.
Jump to: