-
Notifications
You must be signed in to change notification settings - Fork 82
Conversation
This looks correct but it doesn't seem to restore the same public key that is displayed in Keplr. For example: In Keplr using this mnemonic
I see this evmos address But if I run If I run Chain registry says coin type for evmos should be 60 I saw similar results before this PR where the keys would never match what Keplr displays and thought this would fix it but I'm starting to think Keplr is doing something behind the scenes to generate the address. |
It's not immediately obvious what the value for
|
Still seeing some panic's that stem from the SDK. I am running this as a test case:
and seeing this output:
|
this should solve it import (
"github.com/cosmos/cosmos-sdk/codec/legacy"
"github.com/tharsis/ethermint/crypto/ethsecp256k1"
)
legacy.Cdc.RegisterConcrete(ðsecp256k1.PubKey{},
ethsecp256k1.PubKeyName, nil)
legacy.Cdc.RegisterConcrete(ðsecp256k1.PrivKey{},
ethsecp256k1.PrivKeyName, nil) see this note https://github.com/tharsis/ethermint/blob/v.10.1/crypto/codec/amino.go#L24 |
Ahh looks like that does it! 😄 |
this commit must also be added to allow to simulate tx |
Right, I'm guessing this is a temporary need until the SDK has EthSecp256K1 built-in |
relayer needs to know about EthAccounts to interoperate with EVM chains.
This integrates the approach used by @giansalex into lens
cosmos/relayer@main...disperze:ethermint