package hw.trezor.messages.ethereum

Mouse Melon logoGet desktop application:
View/edit binary Protocol Buffers messages

message EthereumAddress

messages-ethereum.proto:50

* Response: Contains an Ethereum address derived from device private seed @end

message EthereumGetAddress

messages-ethereum.proto:41

* Request: Ask device for Ethereum address corresponding to address_n path @start @next EthereumAddress @next Failure

message EthereumGetPublicKey

messages-ethereum.proto:21

* Request: Ask device for public key corresponding to address_n path @start @next EthereumPublicKey @next Failure

message EthereumMessageSignature

messages-ethereum.proto:114

* Response: Signed message @end

message EthereumPublicKey

messages-ethereum.proto:30

* Response: Contains public key derived from device private seed @end

message EthereumSignMessage

messages-ethereum.proto:105

* Request: Ask device to sign message @start @next EthereumMessageSignature @next Failure

message EthereumSignTx

messages-ethereum.proto:63

* Request: Ask device to sign transaction All fields are optional from the protocol's point of view. Each field defaults to value `0` if missing. Note: the first at most 1024 bytes of data MUST be transmitted as part of this message. @start @next EthereumTxRequest @next Failure

message EthereumTxAck

messages-ethereum.proto:95

* Request: Transaction payload data. @next EthereumTxRequest

message EthereumTxRequest

messages-ethereum.proto:84

* Response: Device asks for more data from transaction payload, or returns the signature. If data_length is set, device awaits that many more bytes of payload. Otherwise, the signature_* fields contain the computed transaction signature. All three fields will be present. @end @next EthereumTxAck

message EthereumVerifyMessage

messages-ethereum.proto:126

* Request: Ask device to verify message @start @next Success @next Failure