Keplr address doesn't match autostaking script address

Had reports of this for Desmos, maybe others. When your autostaking mnemonic is imported into Keplr, the address matches for most networks but some it does not. E.g. Desmos.

For the purpose of running the script, the address spat out by npm run autostake is the correct one. This is the one you should fund and the script will send TXs from. I’m not sure how to actually access this in Keplr as of writing but it’s probably derivation path related.

If you see this on any other networks, please add to this issue. I’ll put a note in the README asap.

[tombeynon]

Thought about this some more. This only affects the operator side of things, the UI is handled by Keplr.

I’ll update the autostaking script to use the chain-registry slip44 path by default, and output that address. However if the path differs from 118, we will actually check for operators matching either the 118 path OR the slip44 path. One will be found (no duplicate operators), and if it’s not the 118 version we will check the grants for both addresses to include any grants from the 118 address too. We will need to de-dup the granted addresses here.

Main thing this achieves is a safe migration to the correct slip44 path without missing any users who granted the old operator address. Operators can change their address when they’re ready, and users will be able to grant the new address while their previous grants remain functional.

This introduces a bit of overhead to some networks so I’ll also include a way to disable this behaviour in networks.local.json. This switch can be reversed in the future to disable the functionality by default.

[tombeynon]

@poorbuthappy see #304