Modify transaction fields
When submitting a transaction to the Hedera network, various fields can be modified, such as the transaction ID, consensus time, memo field, account ID of the node, and the maximum fee. These values can be set using methods provided by the SDKs. However, they are not required as the SDK can automatically create or use default values.
Note: The total size for a given transaction is limited to 6KiB.
Fields | Description |
Transaction ID | 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. |
Valid Duration | Set the duration that this transaction is valid for Note: Max network valid duration is 180 seconds. SDK default value is 120 seconds. The minium valid duration period is 15 seconds. |
Memo | Set a note or description that should be recorded in the transaction record (maximum length of 100 characters). Anyone can view this memo on the network |
Node ID | Set the account ID of the node that this transaction will be submitted to. |
Max transaction fee | Set the max transaction fee for the operator (transaction fee payer account) is willing to pay Default: 2 hbar |
Note: The SDKs do not require you to set these fields when submitting a transaction to a Hedera network. All methods below are optional and can be used to modify any fields.
Method | Type |
---|---|
| TransactionID |
| Duration |
| String |
| List<AccountId> |
| Hbar |
| Duration |
| boolean |
Get transaction properties
Method | Type |
---|---|
| TransactionID |
| Duration |
| String |
| AccountID |
| Hbar |
| byte[ ] |
| Map<AccountId, byte [ ]> |
| Map<AccountId, Map<PublicKey, byte [ ]>> |
Last updated