I have extracted my private key from the old Android app that I still had installed. The key is 53 characters long and begins with "P". If I do importprivkey in auroracoin-qt, I get an "invalid private key encoding" error. Any thoughts as to why this happens?

I'm maybe not the best one here to answer this but I did some digging and it seems the backup is encrypted with AES encryption. I don't think there is any simple solution to this but it's likely that this command would help. You would need openssl installed on your machine to execute this and I'm not sure the command would be the same on Windows.

Hi, thanks for the response. I have already done this part. I pulled the encrypted file off the phone and decrypted it with OpenSSL. The resulting file is a list of private keys (1 in this case). It looks something like this:

The above, of course, is a fake private key. The instructions I've found so far across the internet are basically: pull the backup file off the phone, decrypt it with OpenSSL, then run importprivkey with the resulting key(s). Unfortunately, this gives the error described in the original post. I've also tried converting the key into hex and back and some other similar things, but that didn't work either unforuntately.

taehul wrote:Hi, thanks for the response. I have already done this part. I pulled the encrypted file off the phone and decrypted it with OpenSSL. The resulting file is a list of private keys (1 in this case). It looks something like this:

The above, of course, is a fake private key. The instructions I've found so far across the internet are basically: pull the backup file off the phone, decrypt it with OpenSSL, then run importprivkey with the resulting key(s). Unfortunately, this gives the error described in the original post. I've also tried converting the key into hex and back and some other similar things, but that didn't work either unforuntately.

I don't have time at the moment to check this further but some of the other guys are looking into the matter.

Yeah, everything I can find says that it's in WIF. And apparently that should just be directly importable. Somehow it isn't though. Thanks for letting me know that some people are looking at it. Later today I can also try an older backup that was made closer to the original date I made the key (though I'm pretty sure I don't remember the password).

One useful bit of information: When converting the key back into hex, it does not have 0x80 at the start. Instead, it's 0x90. Perhaps that's an intentional choice by the Auroracoin developers, but maybe it's relevant.

I've been looking into this since this afternoon. The example you gave earlier, is that a real generated "false" key, or just some bogus data? It contains an "O", which is an invalid character for Base58.

What I would do, is make a backup from your auroracoin-qt wallet (wallet software shut down) and follow the steps in the link above to generate the private key and try to import that. See if the transactions show up (or you'll have to rescan the block chain to show them up).

I've been looking into this since this afternoon. The example you gave earlier, is that a real generated "false" key, or just some bogus data? It contains an "O", which is an invalid character for Base58.

What I would do, is make a backup from your auroracoin-qt wallet (wallet software shut down) and follow the steps in the link above to generate the private key and try to import that. See if the transactions show up (or you'll have to rescan the block chain to show them up).

Please let me know how that goes and document the steps.

I will try this, probably some time tomorrow. The key pasted in this thread is completely bogus, and was just meant as an example of what the decrypted file from the phone looks like. Tomorrow I will also generate a new private key from the Android app and try importing that. And that key I can paste since it isn't tied to anything.

I've been looking into this since this afternoon. The example you gave earlier, is that a real generated "false" key, or just some bogus data? It contains an "O", which is an invalid character for Base58.

What I would do, is make a backup from your auroracoin-qt wallet (wallet software shut down) and follow the steps in the link above to generate the private key and try to import that. See if the transactions show up (or you'll have to rescan the block chain to show them up).

Please let me know how that goes and document the steps.

Here are some preliminary results. I have not done any backing up of auroracoin-qt's wallet, but I did generate a new test private key on the Android app. The key it generated is "PUzuKkzGYTQUj2WHPkQAfcquf9H4p2KNNuM6MM9uir8QNATrNS5w". The decoded hex version of this is "97FBEA310C3B4299A5DB6561DFB7A25F0D754B6B905B3C77A8F84DBFC8F0DF10BD0177B58EFA". The current auroracoin-qt does not accept these. I do notice that any keys generated by the current auroracoin-qt tend to start with "T" in Base58 format, and when decoded their hex representation begins with a "B".

Or, does any android wallet contains file named wallet.dat as usual version linux/ windows based?

Latest response to his post:

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.

That wallet was not made by us, but by independent developers, so we're reverse engineering this as well.

I'll have a look to see if I can import it myself with your test key.I also understood that one of my dev-colleagues has one of his people working on an update for the android schildbach wallet. If he would succeed in that you could access your coins from your mobile wallet again.

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.

I too have that problem, have my auroracoins stuck in the android app wallet, and it cant connect to any1 so i cant send my coins to my new wallet, and i cant import the private keys to my new wallet as they don't match the new coding..