Multiple (batch) transactions
Batch transactions are a set of transactions generated by a CSV file. This enables you to sign a series of transactions at once. If there is a Batch transaction available for you to sign it will appear as the following notification on your Home screen:
Field | Description |
Sender account | The Hedera account with the checksum value the funds are being debited from |
First transaction date | The date the first transaction will be sent to the network. Required to sign before the specified date/time. |
All transactions will be sent at | The time the transaction will be executed on the Hedera network |
Transactions will be submitted to nodes | The account IDs of the nodes that will submit the transaction to the Hedera network Limit: 5 |
More details | A link that displays the CSV file from which the transactions will be generated from |
Your comments to the coordinating administrator | Comments/notes to provide to the administrator that will be collating and submitting the transaction |
Signing the transaction
The application will display any keys that are available to sign the transaction with
You can select BROWSE to add a key that is not stored within the application Keys folder
You can select ADD MORE to add keys from your application Keys folder
If you would not like to sign the transaction click DECLINE
After you select the keys you would like to sign the transaction with click SIGN and enter your password
The batch transaction should now be in the history section of the home screen
If you would like to use another key to sign the same transaction you may navigate to the transaction in your history and click ADD MORE SIGNATURES
A CSV file is generated in the user's OutputFiles folder
CSV File Format
A CSV file is used to create and sign more than one transaction, a batch of transactions. The following format is required for the batch transaction feature to work as expected. The CSV file needs to be saved as a zip file. Add the CSV.zip file to the InputFiles folder for the application to read in as a new task on the Home screen.
Field | Description | Format |
Sender Account | The account ID of the account the transfer will be debited from. | x.y.z (ex. 0.0.70) |
Fee Payer Account | The account ID of the account paying for the transaction. If the field is not present the app will use the | x.y.z (ex. 0.0.70) |
Sending Time | The time the transaction will be submitted to the network 24 hour clock UTC time. | 18:30 |
Node IDs | The account ID of the node that will submit the transaction to the network Limit: 5 | x.y.z (ex. 0.0.3) |
Transaction Fee | The max transaction fee. The fee must be entered in tinybars. If the field is not present, the app will use the default in Settings. | 156657951 |
Transaction Valid Duration | The time the transaction is valid when submitted to the network. An int from 1 to 180. If the field is not present, the app will use the default in Settings. | 113 |
Account ID | The account IDs of the accounts that will be credited from the transaction. | x.y.z (ex. 0.0.10) |
Memo | A note that gets submitted with all transactions and recorded on ledger in string format. If the field is not present, the application will not add a memo to the transactions. Max: 100 characters. | ex. "a memo for all transfers" |
Amount per distribution (tinybar) | The amount in tinybars the accounts will be credited from the sender account. | Number (no decimals) tinybars |
Start Date | The start date of the distribution. | MM/DD/YY |
Example File:
Last updated
