Add a specification for a typed data (ERC712) signature request message. The message is a JWT much like our other messages, with the difference that the typedData field, (in place of unsignedClaim) is structured according to ERC712. The JWT response also contains an explicit signature field, representing the signature over the typedData alone, while the JWT itself is signed over its entire structure, including the issuer and subject fields.
Note: The response still feels a little strange to me, I would love input from @aldigjo @simonas-notcat @pelle -- Is it fine to just wrap the concept of an ERC712 typed data and signature inside a JWT? Specifically, do we want two signatures on a single JWT, one of them inside of the object itself? Also is there still necessarily a concept of a subject?
Add a specification for a typed data (ERC712) signature request message. The message is a JWT much like our other messages, with the difference that the
typedDatafield, (in place ofunsignedClaim) is structured according to ERC712. The JWT response also contains an explicit signature field, representing the signature over thetypedDataalone, while the JWT itself is signed over its entire structure, including the issuer and subject fields.Note: The response still feels a little strange to me, I would love input from @aldigjo @simonas-notcat @pelle -- Is it fine to just wrap the concept of an ERC712 typed data and signature inside a JWT? Specifically, do we want two signatures on a single JWT, one of them inside of the object itself? Also is there still necessarily a concept of a subject?