A transaction with attached signatures. To submit a transaction, this message should be serialized and included in a SubmitTransactionRequest.
| JSON representation |
|---|
{ "serializedClientTransaction": string, "senderSignature": string, "senderSigningKeySlot": enum ( |
| Fields | |
|---|---|
serializedClientTransaction |
Required. A serialized A base64-encoded string. |
senderSignature |
Required. The signature of the transaction sender. The signature should be computed by signing the For a transaction chain, the bytes to be signed are computed as the concatenation of: - A digest of the serialized client transaction of the entire chain. - A digest of the serialized signed transaction of each unit in the chain, in the order they appear in the chain. The digests are computed using SHA-256. A base64-encoded string. |
senderSigningKeySlot |
Optional. The key slot of the sender used to sign the transaction. Uses the primary slot of the sender account if not specified. |
otherSignatures[] |
Optional. The signatures of accounts listed as additional transaction signatories. The number and order of these signatures must match the The bytes to be signed are the same as those for the The number and identity of additional signatories depends on the particular transaction kind. For a transaction chain, one signature is needed for each account appearing either as the sender or as a signatory of a unit in the chain. A base64-encoded string. |
otherSigningKeySlots[] |
Optional. The key slots of the accounts listed as additional transaction signatories. If set, the number and order of these key slots must match the |