Description

Add basic switchEthereumChain feature for Dapps to prompt and suggest a user to switch to a specified chain that they already have added to MetaMask. This method will work with default networks like mainnet.

Technical Requirements

• Implement the wallet_switchEthereumChain RPC Method (EIP3326)
• Implement the UI that allows the user to accept or reject the request
• Figma - https://www.figma.com/file/dzapXt5s0pKBxb9lZkIoDM/%231352---Confirm-transactions?node-id=3474%3A3906
• Implement warnings in case the parameters are malformed or the chainId is invalid

Acceptance Criteria

• It should successfully switch networks in the case the request is accepted
• It should throw an error for malformed requests or invalid chainId

References

• Sentry issue: https://sentry.io/organizations/metamask/issues/2396504126/?environment=production&project=2299799&query=is%3Aunresolved&sort=user&statsPeriod=14d
• Related to custom network parity issue https://www.notion.so/Allow-me-to-easily-safely-switch-from-a-custom-network-to-mainnet-default-testnets-via-Network--4b8d0f7dce9e4446a111a4146ad6315e
• Technical guidance from Brad: https://consensys.slack.com/archives/G1L7H42BT/p1624408934213000
• Merged PR on extension - rough in switchEthereumChain metamask-extension#10905
• Proposal in EIP 3326 - https://github.com/rekmarks/EIPs/blob/3326-create/EIPS/eip-3326.md
  eip-3326.md

Products POV

• really high on Sentry,
• couple GH issues opened by devs,
• extension parity issue.
• Fixed on extension, looks like lower effort than transaction state (confirm with engineers?)
  ** can't answer this yet until grooming/specing out work is done