Post
Topic
Board Announcements (Altcoins)
Re: [UNO] Unobtanium Info & Discussion - Update to 0.10 Wallet - Merge Mine w/BTC!
by
cryptapus
on 19/05/2017, 12:17:57 UTC
Hi all, it's been a while but I'm still around. Today I come to you in need of a little help! I have 149kg in a Cryptapus paper wallet from Dec 2014 that I'd like to import. I'm having a problem importing the private key to my updated and current UNO Bluechist wallet, which itself holds more UNO correctly and without error.

Someone else had this problem in 2015:

When trying to import a private key in Bitcoin core v0.10.0rc1 I'm getting:

Invalid private key encoding (code -5)

Address was generated at Blockchain.info.

I'm trying to import the address with:

Code:
importprivkey yourPrivateKeyInWalletImportFormat "TheLabelThatIWant"

As described here: https://en.bitcoin.it/wiki/How_to_import_private_keys_v7%2B

Blazr came to the rescue...

I have two keys to import, one starts with 'D' the other with 'C', same error with both.

Your private keys aren't in Wallet Import Format, they are base58 which doesn't work with Bitcoin Core.

On blockchain.info, go to import/export > export unencrypted and on the dropdown "select private key format" select "Bitcoin-Qt Format". They should begin with 5, K or L.

I have no idea why blockchain.info uses base58 as the default format, they really should change that to WIF. Almost no clients use base58.


Like the OP there, it appears my private key is stored in unencrypted Base58 format (58 character private key, starts with '6') and I need to convert it to Bitcoin-qt format. Blazr's advice to the other poster seems to be just what I need to do - however, it appears Blockchain.info has now removed the Export tool from their wallet.

Is there anywhere else I can get my paper wallet address into the right format? Sincere thanks for anything you can suggest! -Craig

ps. cryptocointalk looks great! easy on the eyes Smiley

Hi,

Please try to import the private key in Electrum_uno. It seems to usually do a good job picking the correct format... Also, what is the first character of the string of the private key? Don't post more than the first character obviously.