Default package

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

message Address

messages.proto:335

* Response: Contains address derived from device private seed @prev GetAddress

message ApplyFlags

messages.proto:168

* Request: set flags of the device @next Success @next Failure

message ApplySettings

messages.proto:156

* Request: change language and/or label of the device @next Success @next Failure @next ButtonRequest @next PinMatrixRequest

message BackupDevice

messages.proto:391

* Request: Perform backup of the device seed if not backed up using ResetDevice @next ButtonRequest

(message has no fields)

message ButtonAck

messages.proto:221

* Request: Computer agrees to wait for HW button press @prev ButtonRequest

(message has no fields)

message ButtonRequest

messages.proto:212

* Response: Device is waiting for HW button press. @next ButtonAck @next Cancel

enum ButtonRequestType

types.proto:92

* Type of button request @used_in ButtonRequest

Used in: ButtonRequest

message Cancel

messages.proto:247

* Request: Abort last operation that required user interaction @prev ButtonRequest @prev PinMatrixRequest @prev PassphraseRequest

(message has no fields)

message ChangePin

messages.proto:177

* Request: Starts workflow for setting/changing/removing the PIN @next ButtonRequest @next PinMatrixRequest

message CipherKeyValue

messages.proto:540

* Request: Ask device to encrypt or decrypt value of given key @next CipheredKeyValue @next Failure

message CipheredKeyValue

messages.proto:554

* Response: Return ciphered/deciphered value @prev CipherKeyValue

message ClearSession

messages.proto:146

* Request: clear session (removes cached PIN, passphrase, etc). @next Success

(message has no fields)

message CoinType

types.proto:168

* Structure representing Coin @used_in Features

Used in: Features

message DebugLinkDecision

messages.proto:829

* Request: "Press" the button on the device @next Success

message DebugLinkFlashErase

messages.proto:903

* Request: Erase block of flash on device WARNING: Writing to the wrong location can irreparably break the device.

message DebugLinkGetState

messages.proto:837

* Request: Computer asks for device state @next DebugLinkState

(message has no fields)

message DebugLinkLog

messages.proto:866

* Response: Device wants host to log event

message DebugLinkMemory

messages.proto:885

* Response: Device sends memory back @prev DebugLinkMemoryRead

message DebugLinkMemoryRead

messages.proto:876

* Request: Read memory from device @next DebugLinkMemory

message DebugLinkMemoryWrite

messages.proto:893

* Request: Write memory to device. WARNING: Writing to the wrong location can irreparably break the device.

message DebugLinkState

messages.proto:844

* Response: Device current state @prev DebugLinkGetState

message DebugLinkStop

messages.proto:860

* Request: Ask device to restart

(message has no fields)

message DecryptMessage

messages.proto:519

* Request: Ask device to decrypt message @next Success @next Failure

message DecryptedMessage

messages.proto:530

* Response: Decrypted message @prev DecryptedMessage

message ECDHSessionKey

messages.proto:762

* Response: Device provides ECDH session key @prev GetECDHSessionKey

message EncryptMessage

messages.proto:496

* Request: Ask device to encrypt message @next EncryptedMessage @next Failure

message EncryptedMessage

messages.proto:508

* Response: Encrypted message @prev EncryptMessage

message Entropy

messages.proto:280

* Response: Reply with random data generated by internal RNG @prev GetEntropy

message EntropyAck

messages.proto:407

* Request: Provide additional entropy for seed generation function @prev EntropyRequest @next ButtonRequest

message EntropyRequest

messages.proto:399

* Response: Ask for additional entropy from host computer @prev ResetDevice @next EntropyAck

(message has no fields)

message EstimateTxSize

messages.proto:569

* Request: Estimated size of the transaction This behaves exactly like SignTx, which means that it can ask using TxRequest This call is non-blocking (except possible PassphraseRequest to unlock the seed) @next TxSize @next Failure

message EthereumAddress

messages.proto:343

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

message EthereumGetAddress

messages.proto:326

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

message EthereumMessageSignature

messages.proto:712

* Response: Signed message @prev EthereumSignMessage

message EthereumSignMessage

messages.proto:692

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

message EthereumSignTx

messages.proto:648

* 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. @next PassphraseRequest @next PinMatrixRequest @next EthereumTxRequest @next Failure

message EthereumTxAck

messages.proto:679

* Request: Transaction payload data. @prev EthereumTxRequest @next EthereumTxRequest

message EthereumTxRequest

messages.proto:667

* 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. @prev EthereumSignTx @next EthereumTxAck

message EthereumVerifyMessage

messages.proto:702

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

message Failure

messages.proto:202

* Response: Failure of the previous request

enum FailureType

types.proto:36

* Type of failures returned by Failure message @used_in Failure

Used in: Failure

message Features

messages.proto:119

* Response: Reports various information about the device @prev Initialize @prev GetFeatures

message FirmwareErase

messages.proto:788

* Request: Ask device to erase its firmware (so it can be replaced via FirmwareUpload) @next Success @next FirmwareRequest @next Failure

message FirmwareRequest

messages.proto:796

* Response: Ask for firmware chunk @next FirmwareUpload

message FirmwareUpload

messages.proto:806

* Request: Send firmware in binary form to the device @next Success @next Failure

message GetAddress

messages.proto:312

* Request: Ask device for address corresponding to address_n path @next PassphraseRequest @next Address @next Failure

message GetECDHSessionKey

messages.proto:752

* Request: Ask device to generate ECDH session key @next ECDHSessionKey @next Failure

message GetEntropy

messages.proto:272

* Request: Request a sample of random data generated by hardware RNG. May be used for testing. @next ButtonRequest @next Entropy @next Failure

message GetFeatures

messages.proto:111

* Request: Ask for device details (no device reset) @next Features

(message has no fields)

message GetPublicKey

messages.proto:290

* Request: Ask device for public key corresponding to address_n path @next PassphraseRequest @next PublicKey @next Failure

message HDNodePathType

types.proto:159

Used in: MultisigRedeemScriptType

message HDNodeType

types.proto:150

* Structure representing BIP32 (hierarchical deterministic) node Used for imports of private key into the device and exporting public key out of device @used_in PublicKey @used_in LoadDevice @used_in DebugLinkState @used_in Storage

Used in: DebugLinkState, HDNodePathType, LoadDevice, PublicKey

message IdentityType

types.proto:271

* Structure representing identity data @used_in IdentityType

Used in: GetECDHSessionKey, SignIdentity

message Initialize

messages.proto:104

* Request: Reset device to default state and ask for device details @next Features

(message has no fields)

enum InputScriptType

types.proto:68

* Type of script which will be used for transaction output @used_in TxInputType

Used in: GetAddress, SignMessage, TxInputType

message LoadDevice

messages.proto:360

* Request: Load seed and related internal settings from the computer @next ButtonRequest @next Success @next Failure

message MessageSignature

messages.proto:482

* Response: Signed message @prev SignMessage

enum MessageType

messages.proto:20

* Mapping between Trezor wire identifier (uint) and a protobuf message

message MultisigRedeemScriptType

types.proto:185

* Type of redeem script used in input @used_in TxInputType

Used in: GetAddress, TxInputType, TxOutputType

enum OutputScriptType

types.proto:55

* Type of script which will be used for transaction output @used_in TxOutputType

Used in: TxOutputType

message PassphraseAck

messages.proto:262

* Request: Send passphrase back @prev PassphraseRequest

message PassphraseRequest

messages.proto:255

* Response: Device awaits encryption passphrase @next PassphraseAck @next Cancel

(message has no fields)

message PinMatrixAck

messages.proto:237

* Request: Computer responds with encoded PIN @prev PinMatrixRequest

message PinMatrixRequest

messages.proto:229

* Response: Device is asking computer to show PIN matrix and awaits PIN encoded using this matrix scheme @next PinMatrixAck @next Cancel

enum PinMatrixRequestType

types.proto:110

* Type of PIN request @used_in PinMatrixRequest

Used in: PinMatrixRequest

message Ping

messages.proto:185

* Request: Test if the device is alive, device sends back the message in Success response @next Success

message PublicKey

messages.proto:301

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

message RecoveryDevice

messages.proto:416

* Request: Start recovery workflow asking user for specific words of mnemonic Used to recovery device safely even on untrusted computer. @next WordRequest

enum RecoveryDeviceType

types.proto:126

* Type of recovery procedure. These should be used as bitmask, e.g., `RecoveryDeviceType_ScrambledWords | RecoveryDeviceType_Matrix` listing every method supported by the host computer. Note that ScrambledWords must be supported by every implementation for backward compatibility; there is no way to not support it. @used_in RecoveryDevice

enum RequestType

types.proto:80

* Type of information required by transaction signing process @used_in TxRequest

Used in: TxRequest

message ResetDevice

messages.proto:376

* Request: Ask device to do initialization involving user interaction @next EntropyRequest @next Failure

message SelfTest

messages.proto:817

* Request: Perform a device self-test @next Success @next Failure

message SetU2FCounter

messages.proto:774

* Request: Set U2F counter @next Success

message SignIdentity

messages.proto:726

* Request: Ask device to sign identity @next SignedIdentity @next Failure

message SignMessage

messages.proto:459

* Request: Ask device to sign message @next MessageSignature @next Failure

message SignTx

messages.proto:590

* Request: Ask device to sign transaction @next PassphraseRequest @next PinMatrixRequest @next TxRequest @next Failure

message SignedIdentity

messages.proto:737

* Response: Device provides signed identity @prev SignIdentity

message SimpleSignTx

messages.proto:607

* Request: Simplified transaction signing This method doesn't support streaming, so there are hardware limits in number of inputs and outputs. In case of success, the result is returned using TxRequest message. @next PassphraseRequest @next PinMatrixRequest @next TxRequest @next Failure

message Success

messages.proto:195

* Response: Success of the previous request

message TransactionType

types.proto:234

* Structure representing transaction @used_in SimpleSignTx

Used in: SimpleSignTx, TxAck

message TxAck

messages.proto:635

* Request: Reported transaction data @prev TxRequest @next TxRequest

message TxInputType

types.proto:196

* Structure representing transaction input @used_in SimpleSignTx @used_in TransactionType

Used in: SimpleSignTx, TransactionType

message TxOutputBinType

types.proto:225

* Structure representing compiled transaction output @used_in TransactionType

Used in: TransactionType

message TxOutputType

types.proto:212

* Structure representing transaction output @used_in SimpleSignTx @used_in TransactionType

Used in: SimpleSignTx, TransactionType

message TxRequest

messages.proto:624

* Response: Device asks for information for signing transaction or returns the last result If request_index is set, device awaits TxAck message (with fields filled in according to request_type) If signature_index is set, 'signature' contains signed input of signature_index's input @prev SignTx @prev SimpleSignTx @prev TxAck

message TxRequestDetailsType

types.proto:250

* Structure representing request details @used_in TxRequest

Used in: TxRequest

message TxRequestSerializedType

types.proto:261

* Structure representing serialized data @used_in TxRequest

Used in: TxRequest

message TxSize

messages.proto:579

* Response: Estimated size of the transaction @prev EstimateTxSize

message VerifyMessage

messages.proto:471

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

message WipeDevice

messages.proto:351

* Request: Request device to wipe all sensitive data and settings @next ButtonRequest

(message has no fields)

message WordAck

messages.proto:446

* Request: Computer replies with word from the mnemonic @prev WordRequest @next WordRequest @next Success @next Failure

message WordRequest

messages.proto:435

* Response: Device is waiting for user to enter word of the mnemonic Its position is shown only on device's internal display. @prev RecoveryDevice @prev WordAck

enum WordRequestType

types.proto:136

* Type of Recovery Word request @used_in WordRequest

Used in: WordRequest