Deploy two EVM gateways

[fadeev]

Right now we have an EVM gateway and a ZetaChain gateway, but some (most?) apps need to simulate transfer of value/data between EVM chains. Maybe we should have two EVM gateways (we can call them EVM1 and EVM2) to model these sort of transfers.

[fadeev]

I think we can do this after we support ERC-20 custody, ZETA transfers, etc. in localnet

[fadeev]

@skosito what do you think about having two EVM gateways?

[skosito]

@skosito what do you think about having two EVM gateways?

looks like a good idea, would emulate real scenarios better

[fadeev]

@skosito do you think it would be an overkill to actually start several anvil instances to further emulate an environment with multiple chains?

[skosito]

@skosito do you think it would be an overkill to actually start several anvil instances to further emulate an environment with multiple chains?

initially that was proposed but we agreed to not do it (cc: @lumtis we discussed this at the start), but not sure at the state of the localnet is now and it's usage, maybe now it makes more sense

apart from emulating env with multiple chains, are there more benefits to it? if not, maybe this will just increase development time and maintenance which might reduce purpose of this localnet as fast testing and development env

wdyt?

[fadeev]

I think we'll stick with two EVM gateways for now. I am concerned that having multiple chains will impact dev ex, because devs will have to make sure to use right chains, stuff balances on different chains might be difficult to manage, etc.