Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fail to send token: signature verification failed on genesis_29-2 and wrong public key imported from CLI #419

Closed
alpha-omega-labs opened this issue Jun 3, 2022 · 4 comments
Labels
bug Something isn't working

Comments

@alpha-omega-labs
Copy link

Hello,
Cosmos delegators recently received L1 coin in genesis_29-2 network. In tests about few weeks ago all tests were fine and after receiving coins, cosmos users were able to transact with Keplr.
Now users who received actual airdrop see their coins in Keplr after adding the genesis_29-2 network, however sending tx failed:
please verify account number (22470), sequence (0) and chain-id (genesis_29-2): unauthorized

Also importing private key from node CLI leads to wrong "other" public key (not same as in CLI).

Thank you

@alpha-omega-labs alpha-omega-labs added the bug Something isn't working label Jun 3, 2022
@alpha-omega-labs
Copy link
Author

alpha-omega-labs commented Jun 3, 2022

How to reproduce:

Create new keplr account/address
Send L1 coins to this address - goes well
Send L1 coins from this address fail with:
"Fail to send token: signature verification failed; please verify account number (428101), sequence (0) and chain-id (genesis_29-2): unauthorized"

Unsigned transaction formed in Keplr looks like:

"chain_id": "genesis_29-2",
"account_number": "0",
"sequence": "0",

Seems like problem is with path derivation: in account_number and/or sequence

Keplr was working correctly with GenesisL1 network at least on May 21, 2022

@alpha-omega-labs
Copy link
Author

alpha-omega-labs commented Jun 3, 2022

Seems to be one of related issues: #217 #96

@Thunnini
Copy link
Member

Thunnini commented Jun 6, 2022

I'm not sure what chain you're talking about, but looking at the chain id, it looks like it's probably an evmos fork. Currently, evmos-related codes are managed by the evmos team, and only chain created by the evmos team are officially supported (with beta). We do not solve any other problems that occur on the other chains.

@alpha-omega-labs
Copy link
Author

alpha-omega-labs commented Jun 7, 2022

Noted, thank you, this issue can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants