The executable to use for sending transactions is located at ./bin/tester. You can add it to PATH by running PATH=$PATH:$(pwd)/bin. If you choose to omit this last step, please use ./bin/tester instead of tester for the following examples.

Only five options are currently available for the tester command, which enables us to send transactions of a specified type with relevant parameters:

transfer: send multiple transactions

second-signature: create wallets with two signatures

delegate-registration: create multiple delegates

vote: create multiple votes for a delegate

multi-signature: create multiple multisig wallets

To view which parameters each transaction type requires and offers, use tester [type] help.

As with the transfer transaction type, other types also follow the same model. When specifying a dynamic fee or range of fees for a given transaction to the tester-cli, the transaction will only be accepted if a delegate has set a minimum fee for its type equal to or lower than the specified value/range.

The syntax and output follow the same model as the transfer transaction, with the added type-specific parameter.

Now, despite the error, the newly registered delegate can still be found here; with a registration fee of 100 000 000 arktoshi (1 ARK only). This is due to the blockchain having to spin more than 2.5 blocks, or 20 seconds, before reaching this low delegate dynamic fee threshold, while the Ark Core Tester CLI only waits a strict 20 seconds before determining whether the transaction was successful or not.

You should now be able to properly manage your test transactions with the help of the tester cli utility! If you have any questions or signals to present, please do so either on Slack with a message or GitHub with an issue.