feat/552 - Updates to integrations, better support chain ID updates

[jurevans]

resolves #552

• Bump versions to 0.2.1
• Updates integrations (useIntegration) to index instances by a ChainKey which is "namada" | "cosmos" | "ethereum" for now, instead of chain Id, as the chain ID can be changed on the Namada side in the extension
• Similarly, account state in Interface was also keyed this way, updated to use ChainKey
• With this change, got rid of the defaultChainId export (and related ones from Cosmos, etc.)
• Changing chain ID in Extension does not break association with integration now
• Fixed IBC form to work with integration updates
• Update Ledger Tx to use correct chainId for Reveal PK (ConfirmLedgerTx)
• All requests in Interface now use rpc & chainId from the extension settings (which user may override)

Testing

If you have balances on the current public testnet, then testing is pretty easy. This is the default value in the chain config for Namada, so the extension & interface can be built without any .env variables - if they are defined, they only affect the initial state of the chain config in the extension, and a user can override those with the Network form

1. With a local chain connected, use the Network form in the interface, and update the Chain ID & URL
2. Issue a transaction on the interface - this should submit to your local chain, with the correct chain ID (it will fail and complain otherwise)
3. In the extension, switch the network to the following:

public-testnet-15.0dacadb8d663
https://proxy.heliax.click/public-testnet-15.0dacadb8d663/

• Balances should update in the interface (if you have testnet balances for those same accounts)

4. Issue a transaction - this should use balances & chain ID for the testnet

Also, we can test integrations on the IBC page - when switching Network around, and without refreshing the interface, you should see that Keplr & Namada integrations always work

[github-actions]

🚀 Deployed on https://pull-request-554--wallet-development-heliax-dev.netlify.app

[emccorson]

Code looks good to me! I just left some questions where I'm not familiar with the code.

It didn't work for me at first, but I just needed to clear the cache to get rid of the old chain config.

[emccorson]

Do we still need to have chainId here now that chainKey is added?

[emccorson]

Not a problem with this PR, but I think chainId and rpc here are going to be wrong if they change in the extension. Although actually, is the RPC setting in the extension meant to apply to the interface too or just the extension?

[jurevans]

yep, that's expected! These are just initial values. One of the things I needed to address is that the Network settings in extension are always read as the source of truth. RPC applies to both, since Query & SDK use it in extension, and the interface also uses Query, so the chain RPC setting in the interface must match the extension always (the query to load any new chain settings from extension is important)

[emccorson]

In some cases, we are getting the Namada chain config from Redux state, and in others using chains.namada. What is the difference?

[jurevans]

oh, this is wrong! That should be pulled from Redux state. I can add it here, or in a follow up PR. I mainly focused on getting everything confirmed to work at least for transfers (to confirm extension is correct), but yeah, this needs to use Redux state here.

[jurevans]

I just pushed up a fix for this, and also the Staking actions were referring to default config instead of the Redux state