Bitcoin Forum

Hey guys!

So I am having some trouble importing my private key to blockchain...For some reason my json export exported the private key as "encrypt_privkey" and it is 96 characters long, how would I go about getting this to a working private key for import? Anyone have any ideas?

Here is an example of the 96 character encrypted private key (this is not the one I want to decrypt, so have fun with it): d7e9f17b4986bae8a0507adaf7ce5daceea0fd2b51710f5aead47fc4a67063b71f23939b9264275 d9ff717c311fb253e

I have no idea what alogorithim it is or anything someone PLEASE HELP!

Regards!

Just trying out...

b69ddd7b950613e0d1d357a5171a190d344c90a6ee9e9c29e7767774cafe493c ?

How did you get it to that? (So I can do it for my real one)

You just need to decrypt it.  Look at the header info and use that encryption and your passphrase.

I used it => http://www.xorbin.com/tools/sha256-hash-calculator

I am probably wrong. Please verify from those who had in depth knowledge of this.

How do I go about decrypting it? I have I believe the master key and salt.

Its all in json format like "encrypted_privkey" is the private key that is like the one above and then I have "encrypted_key" which I assume is the master key and then "salt" and "pubkey" I do not have the password to my wallet as it is very old....

Is there a way to use the master key and salt with the encrypted private key to get the actual private key?

If it's encrypted then you need the passphrase

Okay well I dont have the passphrase....So I am looking at the options of either Brute Forcing it? Password Recovery Service?  Or is there some method of decoding the hashes to get the passphrase?

Yeah you'd have to brute force it.  How's it encrypted? AES?  It'll say at the top.

It doesn't say just says compressed: "true".....No AES or anything, I would assume it is AES but what else could it be?

1. Run bitcoind

2. Export all private keys

3. Delete wallet.dat

4. Run bitcoind again (This will create a new unencrypted wallet.dat)

5. Import all private keys

It could just be a compressed private key, non-encrypted.  You should be able to use libbitcoin or similar to convert it from hex to base58.

Though 96 hex characters is too many, I think it should only be ~ 56 if it's a hex private key.  Can you post the whole thing, but blank out the hex info?

Here's what an unencrypted backup looks like:
{
   "guid" : "some hex",
   "sharedKey" : "some hex",
   "options" : {"pbkdf2_iterations":10,"fee_policy":0,"html5_notifications":false,"logout_time":600000,"tx_display":0,"always_keep_local_backup":false,"transactions_per_page":30,"additional_seeds":[]},
   "keys" : [
{"addr":"base58addr","priv":"56 or so hex characters","created_time":0,"created_device_name":"javascript_web","created_device_version":"1.0"}
   ]
}

  It is like this:

  "defaultkey": "btcaddress",
    "keys": [
        {
            "addr": "btcaddress",
            "compressed": true,
            "encrypted_privkey": "96 character key",
            "pubkey": "publickey",
            "reserve": 0
        },

Hope this helps? Yea that is what I thought I am so confused as to why it is 96 characters in length?

I'm sure pywallet can import that, but you need the passphrase or some idea of what it might be (# characters, etc) to brute force it.