Bitcoin Forum
May 03, 2024, 05:47:33 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Auroracoin: Importing private keys from Android wallet to desktop wallet  (Read 2784 times)
degxtra1 (OP)
Member
**
Offline Offline

Activity: 228
Merit: 46


View Profile
April 10, 2016, 09:46:01 PM
 #1

I just faced problem with importing private keys from my Android wallet to desktop based.

I used openssl to decrypt this key using command enc -d -aes-256-cbc -in keyfile -a -k psswd.
In output I got 52 chars long key.  When trying to importprivatekeys in debug console I got message: Invalid private key encoding (code -5)

So far I read compatible length of key is 58 chars.

Now would like to ask this question:

Are all android based wallets always using same kind encryption when creating backup keys : aes-256-cbc ?
Is command I used to decrypt keys correct?

Sorry, I'm just begginer, anyone help appreciated.
1714758453
Hero Member
*
Offline Offline

Posts: 1714758453

View Profile Personal Message (Offline)

Ignore
1714758453
Reply with quote  #2

1714758453
Report to moderator
1714758453
Hero Member
*
Offline Offline

Posts: 1714758453

View Profile Personal Message (Offline)

Ignore
1714758453
Reply with quote  #2

1714758453
Report to moderator
1714758453
Hero Member
*
Offline Offline

Posts: 1714758453

View Profile Personal Message (Offline)

Ignore
1714758453
Reply with quote  #2

1714758453
Report to moderator
Transactions must be included in a block to be properly completed. When you send a transaction, it is broadcast to miners. Miners can then optionally include it in their next blocks. Miners will be more inclined to include your transaction if it has a higher transaction fee.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714758453
Hero Member
*
Offline Offline

Posts: 1714758453

View Profile Personal Message (Offline)

Ignore
1714758453
Reply with quote  #2

1714758453
Report to moderator
1714758453
Hero Member
*
Offline Offline

Posts: 1714758453

View Profile Personal Message (Offline)

Ignore
1714758453
Reply with quote  #2

1714758453
Report to moderator
degxtra1 (OP)
Member
**
Offline Offline

Activity: 228
Merit: 46


View Profile
April 15, 2016, 09:22:50 PM
Last edit: April 15, 2016, 11:02:47 PM by degxtra1
 #2

If – after decrypting – you could identify the file as a wallet (see end of "DECRYPTING" section of https://raw.githubusercontent.com/bitcoin-wallet/bitcoin-wallet/master/wallet/README.recover) decryption was obviously successful so this is not an encryption problem.
Hi Andreas, thanks for your reply

Yes, it's not decryption problem as long private key is 52 chars long. I repeated this steps on linux and win7 booth gives same output: 52 chars long key with date created.

Problem occurs when trying to importprivatekey on Windows based auroracoin wallet.
getting again -5 code

Quote
I assume all forks of Bitcoin Wallet use AES-256-CBC for backup encryption.
Should I contact with creator of AUR android wallet?.. Wink

Quote
In your description you skipped the part about using wallet-tool. Are you using that to extract the keys from the wallet?
I really don't know what is wallet-tool. Do you mean backup keys usual feature on any android wallet?

Edit on 00:00 16/04/2016

Seems Aurora android wallet  produces WIF format key which, as I read may be 51/52/53 chars long. Any advice?

Or, does any android wallet contains file named wallet.dat as usual version linux/ windows based?
degxtra1 (OP)
Member
**
Offline Offline

Activity: 228
Merit: 46


View Profile
April 18, 2016, 06:39:42 PM
 #3

Ok so it seems your backup file is still in the old (pre May 2014) format. Yes I think you should ask the Auroracoin people. In the Bitcoin world, you can import those WIF keys into Bitcoin Core with importprivkeys.
Andreas,
do you know any tool to convert from WIF to Base58 ?
shorena
Copper Member
Legendary
*
Offline Offline

Activity: 1498
Merit: 1499


No I dont escrow anymore.


View Profile WWW
April 18, 2016, 07:06:56 PM
 #4

Ok so it seems your backup file is still in the old (pre May 2014) format. Yes I think you should ask the Auroracoin people. In the Bitcoin world, you can import those WIF keys into Bitcoin Core with importprivkeys.
Andreas,
do you know any tool to convert from WIF to Base58 ?

WIF keys are in base58.

Im not really here, its just your imagination.
degxtra1 (OP)
Member
**
Offline Offline

Activity: 228
Merit: 46


View Profile
May 07, 2016, 07:32:41 AM
 #5



WIF keys are in base58.
Yes, I'm definitely begginer Smiley

However in the meantime I got some kind of answer :

Quote
According to one of our devs it is not possible to import the keys from the Schildbach wallet directly into the auroracoin wallet. He is having a colleague to make a tool to achieve this, he would check tomorrow with him on the status of that.

We also found that the wallet contained a bug to import private keys (from paper wallets) with the latest wallet software. This has been fixed (currently in the development branch of the github repo) and new binaries are prepared.



For anyone exoeriencing this problem I would suggest to check this thread http://auroraspjall.is/viewtopic.php?f=7&t=349
MikkiRefur
Member
**
Offline Offline

Activity: 78
Merit: 16

Auroracoin Community Development


View Profile WWW
August 23, 2016, 01:50:00 PM
 #6

Successfully Imported Private Keys from Old Android Wallet into Coinomi !


In the previous comments above you will find instructions concerning openssl and decoding the android wallet.

(This topic was concerning importing private keys to desktop wallet, but this solution utilizes the Coinomi Android Wallet, from there you can send to your desktop wallet if desired)

I created an "openssl" directory on my cdrive, and placed the file in there, and ran the following:

C:\openssl>openssl enc -d -aes-256-cbc -a -in wallet.dat

WARNING: can't open config file: /usr/local/ssl/openssl.cnf
enter aes-256-cbc decryption password: (type_pwd_here)

Example Output:
-----------------------
# KEEP YOUR PRIVATE KEYS SAFE! Anyone who can read this can spend your Bit

PPu1xUcGGuPMhYKPQspkSyqQee1XiFFk9Ba19yUhF1G4MaemEBzS 2014-06-29T16:17:09Z
PUANfzwVt2ftFqH5jizrDDkLdMYBnbHH6rz2g2YmbxAeHufYUxvq 2014-04-24T19:51:37Z
------------------------

I then simply pasted the above private keys (just individual codes, not date)
into http://www.the-qrcode-generator.com to create a QR Code.

Then used the Coinomi "Sweep Wallet" function to scan the QR Code.

Coinomi will verify that a balance exists and then "sweep" the wallet which may take some minutes.

When it finishes you will see a new AUR address and a Send button.

This address is simply another "receive" address for your Coinomi wallet.

Press "Send" and see the pending transaction in your balance tab.

------------

I have verified this process and the transaction has now been confirmed and appears in the blockchain.

Thank you Coinomi !

[aurtip]AeV3xdbvZCqbMa2DovWpBvmc9t5NWhz9VZ[/aurtip]
MegaHertz
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!