Queue
Given the design of Coinshift's multi-sig Safes, queued transactions do not automatically execute. Instead, you must manually instruct the dApp to execute them.
Queued transactions must be executed in the order in which they are queued. Coinshift does this to most effectively maintain the state and balance of your Safe. It will freeze queued transactions executed out of order until resolved.
The best way to avoid this is to look at the Nonce field and try to execute a transaction with a smaller nonce before moving to the transaction with a higher nonce value.
For further guidance, please carefully watch the GIF below.
Notice the warning message when the user tries executing the latest transaction before running the existing queued transactions.
After your transaction receives the necessary number of signatures – the Safe's threshold – it can be pushed through for execution.
Click on the transaction.
You will now find the option to execute it.
Once you click on the Execute button, the transaction will be submitted to the network.
Transactions successfully executed are added to the History tab.
The Signer who fulfills the Safe's threshold with their approval of the transaction can make use of a streamlined command, Approve and Execute. As the name suggests, this command approves and executes the transaction in a single step instead of performing two separate steps, i.e., approving to then execute separately.
Last modified 1mo ago