Proposal creation support for Evmos

[jnaviask]

Description

Per findings on #3986, we want to support proposal creation for Evmos communities. This will involve adding EvmosJs and creating another codepath for Evmos support.

Please ensure we perform proper codesplitting practices to avoid needing to download the EvmosJs bundle from the root. It should only be loaded when the user lands on a route that requires it.

Open questions:

• Can we support voting as well as proposal creation? How much additional work is required?
• Will we be able to support Metamask & WalletConnect as well as Keplr? Which wallets do we expect to work generally?

Acceptance Criteria

• Can create Evmos proposals.

[mhagel]

• Can we support voting as well as proposal creation? How much additional work is required?

Yes, I was looking at this as evmos TX support, which would be voting and proposal creation

• Will we be able to support Metamask & WalletConnect as well as Keplr? Which wallets do we expect to work generally?

Still need to find out about this. Keplr for sure.

[CowMuon]

Excited to see draft PR here; do we have any updates on Keplr? @mhagel

[mhagel]

@CowMuon EvmosJS supports Metamask and Keplr. I don't know enough about WalletConnect yet to know if it will work.

Please ensure we perform proper codesplitting practices to avoid needing to download the EvmosJs bundle from the root. It should only be loaded when the user lands on a route that requires it.

There is a quirk about EvmosJS that is annoying for us. It is not supported in yarn v1. It works with npm and yarn v2/3. I don't want to bother with upgrading yarn because that is a painful move. I prefer not to mix npm with yarn either, but that seems like the best option right now.

As far as loading on the route, the package will only be imported for ethermint cases that we choose. I don't think we can get around adding the evmosjs package to the commonwealth bundle. But this is pretty standard unless I am missing something.

Possible pivot:

I am considering looking into whether Telescope can generate the types we need instead of using evmosjs. EvmosJs includes transaction support along with typings, but I just need to see if it is any different from cosmJs under the hood. If not, we can use telescope just like we did for v1.

[mhagel]

Came across some valuable info here

[mhagel]

Lots of cleanup to do, but I have a POC in #4286

This does not use EvmosJS, but uses some helpers from that library.

[CowMuon]

This is the other story would like Ian to pair on, this one likely more actionable than other one? Will look for update.