search

greymass / anchor

EOSIO Desktop Wallet and Authenticator
https://greymass.com/anchor/
MIT License
568 stars 221 forks source link

Failed to locate an account #1002

Open Nika6126 opened 3 years ago

Nika6126 commented 3 years ago

Hi, I am trying to pair my private key withAnchor wallet but I always get message Failed to locate an account. But it is the same key I was using. When I set up Watch wallet with account name connected to my private key, it is working...

aaroncox commented 3 years ago

The Watch Wallet setup completely bypasses key matching and you'd be able to set that up for any account. You can test this by going to setup a watch wallet and using teamgreymass as the account name.

Have you changed the API server Anchor uses? That could be a possible reason the key lookup is not working. Not many API servers in the ecosystem currently support key lookups. You can check this under "Manage Blockchains" and clicking on the gear icon next to the chain you're attempting to configure an account for. For EOS specifically, you're welcome to use https://eos.greymass.com which will allow these types of lookups.

Another thing you could try is going into Tools -> Key Validator. Enter your Private Key there, and it will return a Public Key. You can then take the Public Key and look up the accounts associated with it yourself using a block explorer (like bloks.io).

Nika6126 commented 3 years ago

For API server I am using https://eos.greymass.com already. I tried Key validator and I ve got message Invalid key....I dont know why...my EOS are properly registered...when I put my ETH address into eosauthority it showed me account with the same amount of EOS I bought...I also tried eosflare.io to test public key I saved together with my private key after registration and it gets me to the same account and same amount of EOS like ETH address...so looks like something is wrong with private key

aaroncox commented 3 years ago

If it’s reporting an invalid key - that’s likely why the lookup is failing. The private key should start with the number 5 and be 51 characters long, is that correct?

Nika6126 commented 3 years ago

yes, it is...

aaroncox commented 3 years ago

Was this written down and possible the letters/numbers were transposed or a character is wrong? Something like a lower case l, 1 or I getting mixed up? Testing these things inside the Key Validator tool until it results in the proper public key for the account may be the way forward.

If the key is incorrect, there's not much we can do besides offer some suggestions on how you might go about trying different combinations in trying to recover it.

fonzalado commented 3 years ago

Hi, I'm having exactly the same issue as above - was this ever resolved? Key Validator finds my key pair no problem and I can also watch my wallet but I cannot find it to import. When I use an API server other than https://eos.greymass.com nothing at all happens and the output box disappears. When I use https://eos.greymass.com, it outputs "Failed to locate an account" like for the above user. Thanks!

aaroncox commented 3 years ago

After using the key validator, have you tried taking the public key it returns (the one that starts with EOS) and searching for that key on an explorer like bloks.io?

fonzalado commented 3 years ago

Thanks for the response. I realised I was being an idiot and using the wrong Private Key in Key Validator. When I try my actual one (or what I believe it to be), it says:

Verification Results Information based on the Private Key entered above Invalid Key

As such, I've gone through the Lost Key route. Fingers crossed.