Scheduled Transaction Support

[jbair06]

In the case of an emergency transaction, the admin will need to get signatures and submit the transaction as quickly as possible. Currently, this is accomplished by creating multiple copies of the same transaction that have the valid start separated by 1 or more hours. If a transaction is successfully submitted, any subsequent copies will be aborted.

We need to support a better form of an emergency transaction flow. With the addition of the manual transaction feature, multiple copies of a transaction can be created without the fear of a duplicate transaction from being submitted. However, users have asked that the Transaction Tool supports scheduled transactions to better handle these emergency transactions.

Scheduled transactions would allow an admin to create a single transaction that would be submitted as soon as the required signatures are gathered. This would be the quickest way to get the emergency transaction through.

There are a number of difficulties related to supporting scheduled transactions:

• Scheduled transactions are different in how they handles signatures, as each signature is a transaction. This means that the admin and each signer will need to pay for the transaction and signatures. Either each user will need to have access to their own funded account, or another joint account will need to be created for all signers (this has issues of its own).
• The process for how the backend determines who needs to sign the transaction is not the same as a more standard transaction.
• While the signatures can be stored in the backend, it isn't quite the same as how we currently store signatures as each is a scheduled sign transaction.
• A scheduled transaction can be signed outside of the tool, and therefore the tool may not have the full history of the signatures.

More research may be needed to determine the level of effort.