Ready X multisig accounts allow owners to create multiple transaction requests and keep them pending in a queue.
How does the transaction queue work?
In Activity, you'll see two sections:
- Queue contains transactions that are still pending.
- History contains transactions that have already been executed.
Transactions in the queue must be executed in the order they were created.
Each transaction has a unique nonce, which increases with every transaction. Because of this, a later transaction cannot be executed before the transactions ahead of it in the queue.
For example, if your queue contains:
- Send 0.5 ETH
- Add owners and change the threshold to 2 of 3
- Remove a multisig owner
The transactions need to be processed in that order.
How do I reject a queued transaction?
If you don't want a queued transaction to be executed, you can reject it.
- Select the transaction in the Queue.
- Choose Reject.
- Confirm by selecting Yes, reject this transaction.
- Sign the rejection.
- Collect the required approvals from the other multisig owners.
Once the required approval threshold is reached, the transaction is rejected and removed from the queue.
Why does rejecting a transaction require approvals?
Rejecting a queued transaction is an onchain action.
Ready X multisig transaction approvals can be collected offchain before execution. Rejecting the transaction onchain permanently invalidates its nonce so that the rejected transaction cannot be executed later.
The rejection therefore requires the same multisig approval threshold as other actions performed by the account.