It still does not work. I am trying to sweep keys from blockchain.info, but electrum says: "No input found. (Note that inputs need to be confirmed)" But they are very old coins I have parked on blockchain.info for years and haven't made any transaction for a long period of time...
If you still have the wallet file that contains your keys try using this page to import it. If that doesn't work maybe the instructions I posted can help.
https://blockchain.info/wallet/import-walletWere the private keys from the legacy web wallet or the new HD web wallet?
Are your private keys 44 characters long like this example?
HtacbtAnGRxvecHkjf3Jia5r8TZRpnwZek1aU7CApYDi
If they are then they are probably from the legacy web wallet. This reddit thread might explain the problem.
https://www.reddit.com/r/BitcoinBeginners/comments/434tei/blockchaininfo_bci_new_beta_web_wallet_weird/WIF is always base58, right? I'm used to those keys being 51-52 chars long, and always starting with 5, K, or L.
But these weird private keys are 44 chars long, and don't start with 5/K/L.
Unfortunately the simplest solution that reddit thread provides uses the old blockchain.info legacy web wallet login page, and that appears to be discontinued. It currently gives a 404 error.
https://blockchain.info/wallet-legacy/logineditI might have figured out a solution to the problem that doesn't need the old legacy wallet page.
Download and install multibit classic 0.4.18 from here.
https://multibit.org/releases/multibit-classic/multibit-0.4.18/It supports importing those 44 character private keys from blockchain.info, but the newer releases don't.
Copy and paste this code into notepad, then delete HtacbtAnGRxvecHkjf3Jia5r8TZRpnwZek1aU7CApYDi and add your private key in its place. Delete 1Fqdu8waAy53dFKqjBgRgbciLjHQyDrdyY and add your private key's address in its place. Save it as a file named wallet.json
{
"guid": "abf66471-fe0a-6820-8877-55d7e8c1f6b2",
"sharedKey": "5ad12271-57d5-6ad8-79ce-49785a99f539",
"keys": [
{
"addr": "1Fqdu8waAy53dFKqjBgRgbciLjHQyDrdyY",
"priv": "HtacbtAnGRxvecHkjf3Jia5r8TZRpnwZek1aU7CApYDi",
"tag": 2,
"label": "Savings"
}
],
"extended_keys": [
{
"name": "Default",
"master": "000102030405060708090a0b0c0d0e0f",
"accounts": [
{
"id": 0,
"name": "FirstAccount",
"xpub": "xpub68Gmy5EdvgibQVfPdqkBBCHxA5htiqg55crXYuXoQRKfDBFA1WEjWgP6LHhwBZeNK1VTsfTFUHCdrfp1bgwQ9xv5ski8PX9rL2dZXvgGDnw",
"xpriv": "xprv9uHRZZhk6KAJC1avXpDAp4MDc3sQKNxDiPvvkX8Br5ngLNv1TxvUxt4cV1rGL5hj6KCesnDYUhd7oWgT11eZG7XnxHrnYeSvkzY7d2bhkJ7",
"count": 2000
},
{
"id": 1,
"name": "SecondAccount",
"xpub": "xpub68Gmy5EdvgibQVfPdqkBBCHxA5htiqg55crXYuXoQRKfDBFA1WEjWgP6LHhwBZeNK1VTsfTFUHCdrfp1bgwQ9xv5ski8PX9rL2dZXvgGDnw",
"xpriv": "xprv9uHRZZhk6KAJC1avXpDAp4MDc3sQKNxDiPvvkX8Br5ngLNv1TxvUxt4cV1rGL5hj6KCesnDYUhd7oWgT11eZG7XnxHrnYeSvkzY7d2bhkJ7",
"count": 2000
}
]
}
]
}Run multibit classic, then click tools, then click "import private keys".
Click the button named "choose import file", then select "Blockchain.info (*.json")" from the drop down list labelled "files of type".
Afterwards select the wallet.json file you saved earlier, and click the open button.
Next click the button labelled "import private keys". If the import was successful you should be able to see two addresses in your multibit request window.
Click tools in the menu bar, then select "export private keys" from the drop down list.
Click the button named "choose export file" and create a file to export keys to. Check the radio button labelled "do not password protect export file", then click the button labelled "export private keys".
Open the file you exported the keys to in notepad. This is an example of what it should look like.
# KEEP YOUR PRIVATE KEYS SAFE !
# Anyone who can read this file can spend your bitcoin.
#
# Format:
# <Base58 encoded private key>[<whitespace>[<key createdAt>]]
#
# The Base58 encoded private keys are the same format as
# produced by the Satoshi client/ sipa dumpprivkey utility.
#
# Key createdAt is in UTC format as specified by ISO 8601
# e.g: 2011-12-31T16:42:00Z . The century, 'T' and 'Z' are mandatory
#
5JG6wPGejvdYkt7qqzf4gTju2xBmouB8YmLBhCPjcNfSN2Y2JDx 2009-01-03T18:15:05Z
5Kioc2a2otQ1J59m5t6Mxk8rNsN754Qmz36y1yr1NGtw8eYuRCi 2009-01-03T18:15:05Z
# End of private keys
The characters in red are the private key from the blockchain.info wallet converted to a format normal wallets recognise.
This is the address blockchain.info gave for the key 1Fqdu8waAy53dFKqjBgRgbciLjHQyDrdyY
This is the private key blockchain.info gave HtacbtAnGRxvecHkjf3Jia5r8TZRpnwZek1aU7CApYDi
This is the key converted by multibit 5Kioc2a2otQ1J59m5t6Mxk8rNsN754Qmz36y1yr1NGtw8eYuRCi
If you check it in bitaddress you will see two addresses generated for the same private key, one of which is 1Fqdu8waAy53dFKqjBgRgbciLjHQyDrdyY from the blockchain.info wallet.
https://www.bitaddress.org/Bitaddress shows two addresses for each private key because one is derived from a compressed private key, and the other is derived from an uncompressed private key.
