🏐: Evaluate feasibility of Evmos proposal creation

[jnaviask]

Description

To investigate: how do Evmos proposals work? What would be required for us to support Evmos transactions?

Timebox: 2 hours.

[mhagel]

Unsupported type: '/ethermint.types.v1.EthAccount'

[mhagel]

We could set up another devnet for this case: https://docs.evmos.org/protocol/evmos-cli/single-node

[mhagel]

Evmos has their own library for keplr/MM interactions. So we could set up another fork in the code for these Ethermint cases. https://academy.evmos.org/articles/advanced/wallet-integration

[mhagel]

Evmos uses Cosmos SDK gov v1beta1. https://docs.evmos.org/protocol/modules

So, the errors we are seeing may just be account lookup errors. Keplr TXs may work once that is figured out.

[mhagel]

The biggest lift here may be supporting Keplr AND MM. That would be the best Evmos implementation. But just supporting Keplr would be a good start, and so far that is not looking too difficult.

[mhagel]

stack trace

"Error: Unsupported type: '/ethermint.types.v1.EthAccount'\n    
at Object.accountFromAny (webpack-internal:///../../../node_modules/@cosmjs/stargate/build/accounts.js:62:19)\n    
at SigningStargateClient.getAccount (webpack-internal:///../../../node_modules/@cosmjs/stargate/build/stargateclient.js:82:41)\n    
at async SigningStargateClient.getSequence (webpack-internal:///../../../node_modules/@cosmjs/stargate/build/stargateclient.js:96:25)\n    
at async SigningStargateClient.sign (webpack-internal:///../../../node_modules/@cosmjs/stargate/build/signingstargateclient.js:173:49)\n    
at async SigningStargateClient.signAndBroadcast (webpack-internal:///../../../node_modules/@cosmjs/stargate/build/signingstargateclient.js:153:23)"

[mhagel]

May just need this patch: https://github.com/hanchon-live/cosmjs-patch
If so, this is very easy.

[mhagel]

relevant: cosmos/cosmjs#1351

[mhagel]

Findings:

• Easiest solution: add EvmosJs, and if needed, create an EthermintGovernance code path for Evmos and fork-chains.
• CosmJs does not support ethermint, and it's not straightforward to patch on our side

Estimate for suggested solution: 5
Estimate for adding Evmos devnet: 2

It might be easier than this, but adding another governance path means testing a lot of code.
I haven't looked into adding the integration yet. There is a chance that we wouldn't need a whole new code path (governance-ethermint.ts, etc), if this somehow unblocks v1beta1 TXs.

@jnaviask

[jnaviask]

Great findings, thanks for diving in. Will review and follow up with work items.