Keplr Suggest Chain for unsupported chains

[tombeynon]

Keplr only supports a few chains out of the box. I get an error There is no chain info for cheqd-mainnet-1 for Cheqd for example. We need to use the Suggest Chain feature to hook this up. Info can come from Chain Registry, and cosmos.directory APIs.

Adding issue for my tracking but this will hold up #76 and others for now. @Galadrin I think we chatted about this too.

[pwnfoo]

Not sure what issue you're referring to here. I was able to add cheqd to Keplr just fine when I started a local version of restake.

Just the denoms looked broken

EDIT: Just realised this was because I already had it added in Keplr

[jemrickrioux]

#87 This is covered in my last commit but we will need to make some changes to networks.json @tombeynon

• Base denom (Ex.: ATOM vs minimal denom: uatom)
• coinGeckoId
• coinType (To support other types than 118 that is currently hardcoded

[Sdpierret]

@pwnfoo if you already know Cheqd network in your Keplr, you dont see the issue.
on a fresh Keplr install, you will need to add the network, and the SuggestChain is mandatory

(I'm Galadrin, second Github account)

[tombeynon]

Fantastic work 💥

Base denom we can get from chain registry
Coin gecko again in CR
Coin type we can just set in networks.json when we identify a network needs it.

Might separate your Suggest Chain work from #87 so we can merge it separately, would be great to get that in sooner

[jemrickrioux]

@tombeynon #91 Here is the clean branch, I will need to add the 2 values from CR

[jemrickrioux]

Fantastic work 💥

Base denom we can get from chain registry Coin gecko again in CR Coin type we can just set in networks.json when we identify a network needs it.

Might separate your Suggest Chain work from #87 so we can merge it separately, would be great to get that in sooner

These have been done in my new PR #91

[jemrickrioux]

#123 - Merging as we speak