nizjwz (OP)
Newbie
 Offline
Activity: 9
Merit: 0
|
 |
April 22, 2015, 09:47:58 PM |
|
Hello,
i saved my private key who was base64 and if i import it on blockchain i get another bitcoin address do i first need to decrypt or encrypt or something to get my address back?
|
|
|
|
|
|
|
|
|
|
|
|
Remember that Bitcoin is still beta software. Don't put all of your money into BTC!
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
nizjwz (OP)
Newbie
Offline
Activity: 9
Merit: 0
|
|
April 22, 2015, 11:03:45 PM |
|
No one  ? |
|
|
|
|
DannyHamilton
Legendary
Offline
Activity: 3388
Merit: 4653
|
|
April 23, 2015, 01:03:30 AM |
|
Where did you get a base64 private key from?
Why did you save your key in base64 and not in Wallet Import Format?
|
|
|
|
|
dsattler
Legendary
Offline
Activity: 924
Merit: 1000
|
|
April 23, 2015, 06:03:02 AM |
|
Hello,
i saved my private key who was base64 and if i import it on blockchain i get another bitcoin address do i first need to decrypt or encrypt or something to get my address back?
You could use this c# utility to convert between different private key formats: https://github.com/casascius/Bitcoin-Address-Utility |
Bitcointalk member since 2013! 
|
|
|
nizjwz (OP)
Newbie
Offline
Activity: 9
Merit: 0
|
|
April 23, 2015, 02:56:13 PM |
|
i got the key from blockchain in base64 and thanks for the link
|
|
|
|
|
nizjwz (OP)
Newbie
Offline
Activity: 9
Merit: 0
|
|
April 23, 2015, 03:04:05 PM |
|
BTW, How do i run this? is it in linux or can i run it also in another os?
|
|
|
|
|
DannyHamilton
Legendary
Offline
Activity: 3388
Merit: 4653
|
|
April 23, 2015, 03:05:53 PM |
|
I suspect that when the base64 was generated, the wallet was using uncompressed keys, and that blockchain.info has probably been updated now to use compressed keys. I'm not certain, but I think the base64 encoding doesn't include information about whether the key was used for a compressed or uncompressed address (Wallet Import Format does include that information), therefore blockchain.info doesn't know which address to connect it to.
If you convert the base64 to uncompressed key Wallet Import Format, it will probably import just fine.
|
|
|
|
|
coinableS
Legendary
Offline
Activity: 1442
Merit: 1179
|
|
April 23, 2015, 03:17:24 PM |
|
Goto bitaddress.org click on the "Wallet Details" section/tab and paste it in there. It will then convert your base 64 key into a WIF key so you can import it into your wallet. It's all javascript so you can save the webpage to your computer and do it all offline that way you don't expose your private key.
|
|
|
|
nizjwz (OP)
Newbie
Offline
Activity: 9
Merit: 0
|
|
April 23, 2015, 03:32:15 PM |
|
Goto bitaddress.org click on the "Wallet Details" section/tab and paste it in there. It will then convert your base 64 key into a WIF key so you can import it into your wallet. It's all javascript so you can save the webpage to your computer and do it all offline that way you don't expose your private key.
oops its not base64 its base58 its not working on bitaddress :S anyone help me please? |
|
|
|
|
coinableS
Legendary
Offline
Activity: 1442
Merit: 1179
|
|
April 23, 2015, 03:58:31 PM |
|
It's base 58 and it's not working?? Where did you get this key? How did you generate it? Base 58 Private Keys are already in WIF format and they start with a 5, K or L and are 51 or 52 characters long. How many characters in your private key? If it's not working sounds like you have a typo somewhere or whatever you used to create the key is not reliable.
|
|
|
|
DannyHamilton
Legendary
Offline
Activity: 3388
Merit: 4653
|
|
April 23, 2015, 04:14:48 PM |
|
It's base 58 and it's not working?? Where did you get this key? How did you generate it? Base 58 Private Keys are already in WIF format and they start with a 5, K or L and are 51 or 52 characters long.
This is not correct. Blockchain.info allows you to export your private keys as a straight base58 conversion (without the checksum or version number). I have no idea why they would allow this, nor do I understand why they wouldn't explain to their users that their base58 is NOT WIF. Regardless, much like base64, if you exported as base58, then there isn't any information in the private key about whether it was from a compressed key address or an uncompressed key address. I'd convert the address to WIF and try importing that. Unless you know for certain which one you need, you may want to try both compressed and uncompressed format. |
|
|
|
|
nizjwz (OP)
Newbie
Offline
Activity: 9
Merit: 0
|
|
April 23, 2015, 04:24:31 PM |
|
can you do this for me i pm you the base58 i hope you can help me
|
|
|
|
|
DannyHamilton
Legendary
Offline
Activity: 3388
Merit: 4653
|
|
April 23, 2015, 04:48:20 PM |
|
Have you shared that information with anybody else?
Giving your private key to someone allows them full control of your bitcoins. You should never give it to anyone unless you have good reason to trust them.
I see right now that the address you sent me currently has NO BALANCE.
Bitcoins were received at that address (and then immediately spent) as recently as 12 hours ago.
If you are not able to import the private key, then how are you spending the bitcoins?
Either you have acquired someone else's private key (and are attempting to steal their bitcoins), or someone else has acquired your private key (and has already stolen your bitcoins).
|
|
|
|
|
coinableS
Legendary
Offline
Activity: 1442
Merit: 1179
|
|
April 23, 2015, 04:51:37 PM |
|
It's base 58 and it's not working?? Where did you get this key? How did you generate it? Base 58 Private Keys are already in WIF format and they start with a 5, K or L and are 51 or 52 characters long.
Blockchain.info allows you to export your private keys as a straight base58 conversion (without the checksum or version number). Ahh, good to know, thanks Danny! That does seem odd they would do that. I've seen how to manually do the checksum and version number before but personally don't know how to do it. |
|
|
|
|
