EIP712 Encoding shouldn't need the Domain in the types

[JoseAfonsoThreeSigma]

The Eip712TypedDataEncoder throws when encoding typed data if the "EIP712Domain" is not listed in the TypedData types. But according to the most recent EIP712 spec this shouldn't be necessary, the js lib ethers even fails if this happens with this issue ethers-io/ethers.js#4000

Expected Behavior

The encode function should be able to encode the payload correctly without needing to specify the EIP712 type

Current Behavior

The encode function throws when the EIP712 type isn't defined in the typed payload

Possible Solution

Refactor the code to assume the EIP712 type from the spec

Thank you @juanfranblanco

[juanfranblanco]

Hi, where is the upgraded spec? https://eips.ethereum.org/EIPS/eip-712 712 is typed data, so you need the types.