geth wallet import - Fatal:???

shawnlearyshawnleary Posts: 20
Any idea why I am getting "Fatal: Could not create the account:decrypted addr not equal to expected addr %...."

I know that my Passphrase: entry is perfect. I've heard there was an issue with the format of the .json backup wallet file in terms of compatibility with Frontier? Any help or point in the right direction is greatly appreciated.

TIA
Shawn

Comments

  • shawnlearyshawnleary Posts: 20
    I'm getting this back "Fatal: Could not create the account: decrypted addr not equal to expected addr % !(EXTRA string=.........., string=................)"

    Does this mean wrong passphrase?
  • KenKKenK Posts: 44 admin
    Which client are you using to import your wallet?
  • shawnlearyshawnleary Posts: 20
    think my password is wrong. i was using a terminal window on my mac. but kraken is giving me the same response using their browser tool. oh well, someday it might be worth it to brute force it. would love to see what the password instructions were at the time of sale. i wonder if i modified my password based on some recommendations at that time.
  • charleycharley Posts: 6
    Receiving the same error. I'm almost sure my password is correct.
  • UTlex92UTlex92 Posts: 2
    I am also receiving the same error using what I would call my most likely password.

    I've tried variations of my password at myetherwallet.com and all give the following error: Invalid password. Error: unable to decrypt data

    Yet only when I use my most likely password I get this error:
    Invalid password. Error: Decoded key mismatch - possibly wrong passphrase

    I confirmed the above using Geth command line tools. Geth gives the following error:
    Fatal: decrypted addr 'resulting address ' not equal to expected addr 'my address'

    Using knowingly wrong password provides:
    Fatal: could not decrypt key with given passphrase.

    Any information regarding this error would be greatly appreciated.
  • bitmasterbitmaster Posts: 2
    UTlex92- Did you ever come to a solution for your problem? I have the same exact issue!!! Please help! Thanks!
  • UTlex92UTlex92 Posts: 2
    bitmaster said:

    UTlex92- Did you ever come to a solution for your problem? I have the same exact issue!!! Please help! Thanks!

    Bitmaster, not yet but I have uncovered some interesting results. Using the Geth console I tried to login with using my presale wallet json file and the password that gives the mentioned error. I wrote down the address Geth provided as an output (which does not match the address in my presale wallet json file). I then opened my presale wallet json in a text editor, saved as with new name (don't override your existing wallet) and replaced the ethaddress with the address Geth provided as an output, and saved the document.

    I then went through the login process again using geth, this time used the updated json file and the same password that resulted in the above error. To my surprise, geth accepted it. Unfortunately, what appears in mist is the empty wallet for the wrong ethaddress that Geth provided. Scratching my head here. It would be great if someone familiar with coding of the wallets could comment. I think this case history provides sufficient evidence that the passwords are not being entered incorrectly.
Sign In or Register to comment.