package hw.trezor.messages.bitcoin

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

message Address

messages-bitcoin.proto:131

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

enum AmountUnit

messages-bitcoin.proto:50

* Unit to be used when showing amounts on the display

Used in: AuthorizeCoinJoin, SignTx

message AuthorizeCoinJoin

messages-bitcoin.proto:618

* Request: Ask device to prompt the user to authorize a CoinJoin transaction @start @next Success @next Failure

message BenchmarkListNames

messages-benchmark.proto:19

* Request: Ask device for a list of names of all supported benchmarks @start @next Benchmarks @next Failure

(message has no fields)

message BenchmarkNames

messages-benchmark.proto:25

* Response: Contains the list of names of all supported benchmarks @end

message BenchmarkResult

messages-benchmark.proto:43

* Response: Contains the result of the benchmark @end

message BenchmarkRun

messages-benchmark.proto:35

* Request: Ask device to run a benchmark @start @next BenchmarkResult @next Failure

enum DecredStakingSpendType

messages-bitcoin.proto:42

* Type of script which will be used for decred stake transaction input

Used in: TxAck.TransactionType.TxInputType, TxInput

message GetAddress

messages-bitcoin.proto:116

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

message GetOwnershipId

messages-bitcoin.proto:142

* Request: Ask device for ownership identifier corresponding to scriptPubKey for address_n path @start @next OwnershipId @next Failure

message GetOwnershipProof

messages-bitcoin.proto:591

* Request: Ask device for a proof of ownership corresponding to address_n path @start @next OwnershipProof @next Failure

message GetPublicKey

messages-bitcoin.proto:89

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

enum InputScriptType

messages-bitcoin.proto:17

* Type of script which will be used for transaction input

Used in: AuthorizeCoinJoin, GetAddress, GetOwnershipId, GetOwnershipProof, GetPublicKey, SignMessage, TxAck.TransactionType.TxInputType, TxInput

message MessageSignature

messages-bitcoin.proto:179

* Response: Signed message @end

enum MultisigPubkeysOrder

messages-bitcoin.proto:57

Used in: MultisigRedeemScriptType

message MultisigRedeemScriptType

messages-bitcoin.proto:66

* Type of redeem script used in input @embed

Used in: GetAddress, GetOwnershipId, GetOwnershipProof, TxAck.TransactionType.TxInputType, TxAck.TransactionType.TxOutputType, TxInput, TxOutput

message MultisigRedeemScriptType.HDNodePathType

messages-bitcoin.proto:77

* Structure representing HDNode + Path

Used in: MultisigRedeemScriptType

enum OutputScriptType

messages-bitcoin.proto:29

* Type of script which will be used for transaction output

Used in: TxAck.TransactionType.TxOutputType, TxOutput

message OwnershipId

messages-bitcoin.proto:154

* Response: Contains the ownership identifier for the scriptPubKey and device private seed @end

message OwnershipProof

messages-bitcoin.proto:607

* Response: Contains the proof of ownership @end

message PrevInput

messages-bitcoin.proto:456

* Data type for inputs of previous transactions. When adding fields, take care to not conflict with TxInput @embed

Used in: TxAckPrevInput.TxAckPrevInputWrapper

message PrevOutput

messages-bitcoin.proto:470

* Data type for outputs of previous transactions. @embed

Used in: TxAckPrevOutput.TxAckPrevOutputWrapper

message PrevTx

messages-bitcoin.proto:436

* Data type for metadata about previous transaction which contains the UTXO being spent. @embed

Used in: TxAckPrevMeta

message PublicKey

messages-bitcoin.proto:103

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

message SignMessage

messages-bitcoin.proto:164

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

message SignTx

messages-bitcoin.proto:204

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

message SignTx.CoinJoinRequest

messages-bitcoin.proto:226

* Signing request for a CoinJoin transaction.

Used in: SignTx

message TxAck

messages-bitcoin.proto:298

* Request: Reported transaction data (legacy) This message contains all possible field that can be sent in response to a TxRequest. Depending on the request_type, the host is supposed to fill some of these fields. The interface is wire-compatible with the new method of specialized TxAck subtypes, so it can be used in the old way. However, it is now recommended to use more specialized messages, which have better-configured constraints on field values. @next TxRequest

message TxAck.TransactionType

messages-bitcoin.proto:305

* Structure representing transaction

Used in: TxAck

message TxAck.TransactionType.TxInputType

messages-bitcoin.proto:324

* Structure representing transaction input

Used in: TransactionType

message TxAck.TransactionType.TxOutputBinType

messages-bitcoin.proto:354

* Structure representing compiled transaction output

Used in: TransactionType

message TxAck.TransactionType.TxOutputType

messages-bitcoin.proto:362

* Structure representing transaction output

Used in: TransactionType

message TxAckInput

messages-bitcoin.proto:485

* Request: Data about input to be signed. Wire-alias of TxAck. Do not edit this type without considering compatibility with TxAck. Prefer to modify the inner TxInput type. @next TxRequest

message TxAckInput.TxAckInputWrapper

messages-bitcoin.proto:490

Used in: TxAckInput

message TxAckOutput

messages-bitcoin.proto:504

* Request: Data about output to be signed. Wire-alias of TxAck. Do not edit this type without considering compatibility with TxAck. Prefer to modify the inner TxOutput type. @next TxRequest

message TxAckOutput.TxAckOutputWrapper

messages-bitcoin.proto:509

Used in: TxAckOutput

message TxAckPrevExtraData

messages-bitcoin.proto:575

* Request: Content of the extra data of a previous transaction Wire-alias of TxAck. Do not edit this type without considering compatibility with TxAck. @next TxRequest

message TxAckPrevExtraData.TxAckPrevExtraDataWrapper

messages-bitcoin.proto:580

Used in: TxAckPrevExtraData

message TxAckPrevInput

messages-bitcoin.proto:538

* Request: Data about previous transaction input Wire-alias of TxAck. Do not edit this type without considering compatibility with TxAck. Prefer to modify the inner PrevInput type. @next TxRequest

message TxAckPrevInput.TxAckPrevInputWrapper

messages-bitcoin.proto:543

Used in: TxAckPrevInput

message TxAckPrevMeta

messages-bitcoin.proto:523

* Request: Data about previous transaction metadata Wire-alias of TxAck. Do not edit this type without considering compatibility with TxAck. Prefer to modify the inner PrevTx type. @next TxRequest

message TxAckPrevOutput

messages-bitcoin.proto:557

* Request: Data about previous transaction output Wire-alias of TxAck. Do not edit this type without considering compatibility with TxAck. Prefer to modify the inner PrevOutput type. @next TxRequest

message TxAckPrevOutput.TxAckPrevOutputWrapper

messages-bitcoin.proto:562

Used in: TxAckPrevOutput

message TxInput

messages-bitcoin.proto:390

* Data type for transaction input to be signed. When adding fields, take care to not conflict with PrevInput @embed

Used in: TxAckInput.TxAckInputWrapper

message TxOutput

messages-bitcoin.proto:418

* Data type for transaction output to be signed. @embed

Used in: TxAckOutput.TxAckOutputWrapper

message TxRequest

messages-bitcoin.proto:250

* Response: Device asks for information for signing transaction or returns the last result If request_index is set, device awaits TxAck<any> matching the request type. If signature_index is set, 'signature' contains signed input of signature_index's input @end @next TxAckInput @next TxAckOutput @next TxAckPrevMeta @next TxAckPrevInput @next TxAckPrevOutput @next TxAckPrevExtraData @next PaymentRequest

enum TxRequest.RequestType

messages-bitcoin.proto:257

* Type of information required by transaction signing process

Used in: TxRequest

message TxRequest.TxRequestDetailsType

messages-bitcoin.proto:270

* Structure representing request details

Used in: TxRequest

message TxRequest.TxRequestSerializedType

messages-bitcoin.proto:279

* Structure representing serialized data

Used in: TxRequest

message VerifyMessage

messages-bitcoin.proto:190

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