Devon Bear

@yihuang @loredanacirstea. All of the above makes sense, I've been doing some research into getting state changing precompile working and ultimately am realizing that the StateDB is the problem. IMO...

@yihuang correct. But the issue is that we can't call arbitrary module logic, in the way that we can pass CosmosMsg's from CosmWasm VM to the module directly. Going this...

Seems like bad developer UX, there has to be a way to get it to work like how CosmWasm works. That should be the end goal for Stateful Precompiles IMO.

Having an EthTx revert, revert the whole Cosmos Txn would resolve this issue, no?

Needless to say, I think the approach should be attempt to get synchronous ability to call Cosmos SDK modules from the evm. Having to duplicate all the logic seems like...

should look into making special stripped out go-ethereum fork specifically for ethermint. (Think SubnetEVM)

(Maybe that's even the place to start)

Implementing a generic MsgServer and Querier as stateful precompile seems like the correct approach here. Similar to how it is handled in CosmWasm.

+1 big issues, definitely a cosmos-sdk thing though

Not possible given the current architecture. Since the multsig will sign the Cosmos Txn. However EthTx bypass the sig check at the Cosmos SDK, and require that the Signatureless CosmosSDK...