Wallet Tx Security Provider: Send the transaction or signature request payload information to a service provider

[dragana8]

User story

As a user, I want my unsigned transaction and signatures requests to be sent to my security provider so it can verify whether it’s malicious or not before I sign them. Any eth_sendTransaction, eth_sign, personal_sign, or signTypedData_vXX method request would be forwarded to SECURITY_PROVIDER_RPC_URL in the standard JSON RPC request format prior to rendering a transaction confirmation modal to the user.

Tasks:

1. Check wether tx security provider is turned on;
2. If yes, unsigned transaction or signature request payload (eth_rpc call + url) is sent to tx security provider;
3. Tx security provider sends back a boolean response wether it wants to flag it as malicious or not

[bschorchit]

More details on data format to be forwarded available here

[bschorchit]

We should include language in ISO 639-2 code in the data we share. Slack thread cc: @filipsekulic

[sambacha]

Metamask does not allow progmatic change of chainId wrt Mainnet Ethereum