test signatures with typedDataSign

[pnowosie]

#825 introduced another way to sign a transaction. /transaction.create returns typed_data field which serves as a request to web3's eth.signTypedData. This function isn't fully implemented in all clients software yet. Currently the only tests on typed_data was manual tests with MetaMask.

📔 we're not ready to implement such test, however some results of our tries are worth to be noted,

Results with parity
Implementing #825 some effort was made to create such automated test with parity (parity 2.5.0-beta) which implements typedDataSign.

We learned from ☝️ experiments that parity requires optional parameter chainId as mandatory. Reported issue did not take result.

We made a changes that introduces chainId to our EIP712 domain, add prepare working test.
It might be useful, we situation would clarify and we get ready to implement this test.

[InoMurko]

is this still relevant @pnowosie ? if not pls close

[pdobacz]

such test (or something similar) would be a good check if our EIP712 structures are interpreted the same by an external signing facility (like geth, parity, Metamask etc.).

For now we only have some elixir-omg (our implementation) vs plasma-contracts (our implementation) tests

Not sure about priorities tho