Message signed on the wrong chain

[avious00]

Context

A user ended up signing a warp route transfer intended from inEVM on zkSync ⁠[discord]

Investigation

As per zksync and etherscan this happened a few times on other chains as well.

@jmrossy suspects imperfect wallet switching behavior within https://github.com/wevm/wagmi for this.

Potential Solutions

Some workarounds are:

1. adding more explicit wallet chain checks after switching (possibly hacky)
2. upgrading to wagmi 2
3. Possibly more user prompts to make sure that they are signing on the right chain (unfortunately wallets don't indicate the presence of calldata for a call to a non-existing contract)