Skip to content
This repository has been archived by the owner on Nov 21, 2019. It is now read-only.

Private key / JSON logs into wrong address. Private key public address mismatch #1121

Open
bluecollarcrypto opened this issue Oct 12, 2017 · 26 comments

Comments

@bluecollarcrypto
Copy link

Hello,

When creating the wallet, I copied and pasted public address & private key into .txt file and saved on my pc.
I saved JSON file on my pc.
I type password into txt. file which gets saved to my pc, from which I copy and paste password into browser field when creating new wallet.

Private key opens incorrect address.
JSON file opens incorrect address.

View only via public address opens & loads correct wallet address and displays my REAL tokens.

I would like to transfer my REAL tokens and can not right now

@kvhnuke
Copy link
Collaborator

kvhnuke commented Oct 12, 2017

It seems like you saved the wrong private key or a private key for a different wallet. Does the private key and JSON file derive the same address?

@bluecollarcrypto
Copy link
Author

I'm not sure that is the case because I save at moment of creation prior to execute any transfers etc.
The private key and JSON should derive from same address as it was created and saved all upon creating the new wallet.

Im hoping I do not have issue as posted here
https://www.reddit.com/r/ethereum/comments/48rt6n/using_myetherwalletcom_just_burned_me_for/

Additionally I am wondering if token issuer may be able to recall tokens and transfer them to other address I use as it was an ICO event for these tokens I am only able to view at this time

@kvhnuke
Copy link
Collaborator

kvhnuke commented Oct 12, 2017

Does your JSON file and private key derive the same address?

@bluecollarcrypto
Copy link
Author

How do I check that ?

@kvhnuke
Copy link
Collaborator

kvhnuke commented Oct 12, 2017

Open the wallet using your private key, then remember the address you see. Then unlock the wallet using the JSON file and check whether that address matches the previous one. Also let me know what token you are trying to transfer?

@bluecollarcrypto
Copy link
Author

It opens incorrect wallet with JSON or private key. Only able to view with public address. I saved JSON and private at time of wallet creation

@kvhnuke
Copy link
Collaborator

kvhnuke commented Oct 12, 2017

Are the public address shown by the private key and JSON the same?

@bluecollarcrypto
Copy link
Author

Let me log in with each and see

@bluecollarcrypto
Copy link
Author

JSON and Private log ins do bring up same public address

@kvhnuke
Copy link
Collaborator

kvhnuke commented Oct 12, 2017

Ok, what kind of token are you trying to transfer? And how did you receive these tokens? From an exchange? ICO?

@bluecollarcrypto
Copy link
Author

ICO. It was for REAL. Here is my public address. I created this wallet for this specific ICO as I do for other ICOs (to not show all other balances I hold)

0x07E9Cd8DbC4186014DBcaa1520eB648F98F87919

@kvhnuke
Copy link
Collaborator

kvhnuke commented Oct 12, 2017

upon checking your address it seems like you definitely had access to the correct privatekey. you were able to send out multiple transactions approx 41 days ago. I would go through all other private keys you have and see whether any of those derives the correct address.

@bluecollarcrypto
Copy link
Author

Let me see what I come up with

@kvhnuke
Copy link
Collaborator

kvhnuke commented Oct 12, 2017

Check under MonethaTokenCrowdsale it seems like you used that address for that initially

@bluecollarcrypto
Copy link
Author

Yes I did. I was unsuccessful, it sold in minutes. I noted that as well in my ICO wallet and participation notes. Let me look to see if i can find more in monetha notes

@tayvano
Copy link
Contributor

tayvano commented Oct 31, 2017

Did you ever unlock your wallet by hand typing the key?

Please be sure that you are carefully and accurately typed it. A single wrong character will open a different wallet than "yours".

If you go to https://www.myetherwallet.com/helpers.html, scroll allllll the way to the bottom, and enter your private key and address and see if that resolves. If that doesn't work, try hand typing your private key faster or slower or with your eyes closed.

Essentially we are trying to recreate the way you accessed the wallet the first time to try to regain access.

@bluecollarcrypto
Copy link
Author

bluecollarcrypto commented Oct 31, 2017 via email

@iquidus
Copy link
Contributor

iquidus commented Nov 27, 2017

It's not possible for the MEW team to move coins from any address, the server/nodes never see any private keys or wallet files, MEW does not hold any coins. Everything takes place clientside in your browser.

@Uelese
Copy link

Uelese commented Jan 8, 2018

I've had the same problem. I generated a new MEW for the purpose of connecting into EtherDelta. MEW generates a private key which is automatically saved to my computer using a surface 3. Once i unlocked my new wallet, I scrolled down and copied the address from that wallet and sent coins from my MEW which is connected to my trezor. I checked the transaction and it had been successful, so I went back to my private key which was saved in my comp with the name UTC-2018 etc and none of the 3 keys in that file match the original address which was generated. My mistake is that I didn't close and double check the keys matched but I'm in the same boat as many others. I'm hoping for a solution which i understand is slim. Any help appreciated.

Thanks

@wparad
Copy link

wparad commented Jan 8, 2018

@Uelese, could you expand with more details, i.e. the address you copied, tx adress, and the actions you performed others than those listed. It also sounds like you are saying that the file you opened show two different addresses on each subsequent opening, how is that possible?

@Uelese
Copy link

Uelese commented Jan 9, 2018

@wparad this is the address that the wallet generated "0x04eb66d8cbdc5f822aba31c6bd4790519c098228" TX is "0xf28c171b9abb54a77e4c6de5b55bc4ccaa10f252e402c5fa44b268c4bc8170b5" I opened my wallet using the private key option. I then opened the file which saves automatically when creating the wallet. In order to read the file i converted it into notepad so i could get the numbers, and cut out the numbers which were bracketed right after the "cipher text", and it didn't match the address i had sent it too. I then scrolled across the same file and saw some numbers after "salt": - So i cut those out and entered them into the private key option on MEW and still not the same. I scrolled across the same file and some numbers right after the "mac": and cut them out and still not the same. That's how I got 3 different addresses from that file. I then opened my wallet using the "Keystore/ JSON file and it brings up the one address which is not the same one i copied to send my tokens too.

@wparad
Copy link

wparad commented Jan 9, 2018

@Uelese, I'm confused, two things of note:

  • there are many more than 3 values in the JSON keystore. As a matter of fact the public address is none of three you listed but actually the ones saved in the address field.
  • looking at address 0x04eb66d8cbdc5f822aba31c6bd4790519c098228, seems you managed to successful sign two transactions after the transfer from your trezor from this address to this address.

This happened after your last post, does that mean you figured this out?

@Uelese
Copy link

Uelese commented Jan 9, 2018 via email

@numero41
Copy link

@Uelese

Please can you ask your friend to give us an update about what he did, because there are other people that try to figure out the same issues.
Thank you!

@bluecollarcrypto

@numero41
Copy link

numero41 commented Jan 24, 2018

@bluecollarcrypto

Is your issue similar to this one?
#1528

@Massat168
Copy link

I have same problem.

When I created MEW account, I copied, screen shotted the private key, and downloaded the keystore file, but both private key and keystore file gives me different account.

I have already put my coins in my account, so I cant take my coin out....

Does anyone know how to fix it?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

8 participants