Get desktop application:
View/edit binary Protocol Buffers messages
* Response: Contains an Ethereum address derived from device private seed @end
Ethereum address as 20 bytes (legacy firmwares)
Ethereum address as hex string (newer firmwares)
* Request: Ask device for Ethereum address corresponding to address_n path @start @next EthereumAddress @next Failure
BIP-32 path to derive the key from master node
optionally show on display before sending the result
* Request: Ask device for public key corresponding to address_n path @start @next EthereumPublicKey @next Failure
BIP-32 path to derive the key from master node
optionally show on display before sending the result
* Response: Signed message @end
address used to sign the message (20 bytes, legacy firmware)
signature of the message
address used to sign the message (hex string, newer firmware)
* Response: Contains public key derived from device private seed @end
BIP32 public node
serialized form of public node
* Request: Ask device to sign message @start @next EthereumMessageSignature @next Failure
BIP-32 path to derive the key from master node
message to be signed
* 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
BIP-32 path to derive the key from master node
<=256 bit unsigned big endian
<=256 bit unsigned big endian (in wei)
<=256 bit unsigned big endian
recipient address (20 bytes, legacy firmware)
recipient address (hex string, newer firmware)
<=256 bit unsigned big endian (in wei)
The initial data chunk (<= 1024 bytes)
Length of transaction payload
Chain Id for EIP 155
(only for Wanchain)
* Request: Transaction payload data. @next EthereumTxRequest
Bytes from transaction payload (<= 1024 bytes)
* 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
Number of bytes being requested (<= 1024)
Computed signature (recovery parameter, limited to 27 or 28)
Computed signature R component (256 bit)
Computed signature S component (256 bit)
* Request: Ask device to verify message @start @next Success @next Failure
address to verify (20 bytes, legacy firmware)
signature to verify
message to verify
address to verify (hex string, newer firmware)