Optional props: { Get the grpc deadline
Get the max attempts on the request
Get the max backoff
Get the min backoff
Is transaction ID regeneration enabled
Get the curent transaction ID
Get the transaction memo
Get the transaction valid duration
Add a signature explicitly
This method requires the transaction to have exactly 1 node account ID set since different node account IDs have different byte representations and hence the same signature would not work for all transactions that are the same except for node account ID being different.
Execute this request using the signer
This method is part of the signature providers feature https://hips.hedera.com/hip/hip-338
Freeze this transaction from future modification to prepare for signing or serialization.
Freeze this transaction from further modification to prepare for signing or serialization.
Will use the Client, if available, to generate a default Transaction ID and select 1/3
nodes to prepare this transaction for.
Freeze the transaction using a signer
This is part of the signature provider feature.
Set the given byte array as the file's contents.
This may be omitted to append an empty file.
Note that total size for a given transaction is limited to 6KiB (as of March 2020) by the network; if you exceed this you may receive a HederaPreCheckStatusException with Status#TransactionOversize.
In this case, you will need to break the data into chunks of less than ~6KiB and execute this transaction with the first chunk and then use FileAppendTransaction with FileAppendTransaction#setContents(Uint8Array) for the remaining chunks.
Set the keys which must sign any transactions modifying this file. Required.
All keys must sign to modify the file's contents or keys. No key is required to sign for extending the expiration time (except the one for the operator account paying for the transaction). Only one key must sign to delete the file, however.
To require more than one key to sign to delete a file, add them to a KeyList and pass that here.
The network currently requires a file to have at least one key (or key list or threshold key) but this requirement may be lifted in the future.
Set the grpc deadline
Set logger
Set the max attempts on the request
Set the max backoff for the request
Set the maximum transaction fee the operator (paying account) is willing to pay.
Set the min backoff for the request
Set the node account IDs
Set the maximum transaction fee the operator (paying account) is willing to pay.
Set the ID for this transaction.
The transaction ID includes the operator's account ( the account paying the transaction fee). If two transactions have the same transaction ID, they won't both have an effect. One will complete normally and the other will fail with a duplicate transaction status.
Normally, you should not use this method. Just before a transaction is executed, a transaction ID will be generated from the operator on the client.
Set a note or description to be recorded in the transaction record (maximum length of 100 bytes).
Sets the duration (in seconds) that this transaction is valid for.
This is defaulted to 120 seconds (from the time its executed).
Sign the transaction with the private key
NOTE: This is a thin wrapper around .signWith()
Sign the transaction with the public key and signer function
If sign on demand is enabled no signing will be done immediately, instead
the private key signing function and public key are saved to be used when
a user calls an exit condition method (not sure what a better name for this is)
such as toBytes[Async](), getTransactionHash[PerNode]() or execute().
Sign the transaction with the client operator. This is a thin wrapper
around .signWith()
NOTE: If client does not have an operator set, this method will throw
Sign the transaction using a signer
This is part of the signature provider feature
Static _fromThis method is called by each *Transaction._fromProtobuf() method. It does
all the finalization before the user gets hold of a complete Transaction
Static fromDeserialize a transaction from bytes. The bytes can either be a proto.Transaction or
proto.TransactionList.
Generated using TypeDoc
A transaction specifically to append data to a file on the network.
If a file has multiple keys, all keys must sign to modify its contents.