Get desktop application:
View/edit binary Protocol Buffers messages
* Request: Ask device to sign typed data @start @next EthereumTypedDataStructRequest @next EthereumTypedDataValueRequest @next EthereumTypedDataSignature @next Failure
BIP-32 path to derive the key from master node
name of the root message struct
use MetaMask v4, see
https://github.com/MetaMask/eth-sig-util/issues/106
network and/or token definitions
hash of the typed data to be signed (if set, user will
* Request: Type information about a struct. @next EthereumTypedDataStructRequest
Used in:
Used in:
for integer types: size in bytes (uint8 has size 1, uint256 has size 32)
for bytes types: size in bytes, or unset for dynamic for arrays: size in elements, or unset for dynamic for structs: number of members for string, bool and address: unset
for array types, type of single entry
for structs: its name
Used in:
* Response: Device asks for type information about a struct. @next EthereumTypedDataStructAck
name of the requested struct
* Request: Single value of a specific atomic field. @next EthereumTypedDataValueRequest
* atomic types: value of the member. Length must match the `size` of the corresponding field type, unless the size is dynamic. * array types: number of elements, encoded as uint16. * struct types: undefined, Trezor will not query a struct field.
* Response: Device asks for data at the specific member path. @next EthereumTypedDataValueAck
member path requested by device