What is transaction queueing?
Ready Wallet Multisig accounts allow users to queue and manage pending transactions.
In the "Activity" tab, you will see two sections: Queue and History.
- Transactions in the Queue are pending and not yet executed
- Transactions in History have already been executed (accepted on L2)
Queued transactions must be executed in the correct order because each transaction has a unique nonce that increases by 1 each time. This keeps processing correct on the blockchain.
For example, based on the screenshot shown:
- First - "Send" 0.5 ETH
- Second - Add owners and set 2/3
- Third - Remove multisig owner
You must follow this order. If you try to execute a transaction out of order, it will not go through.
How to reject a queued multisig transaction?
If you want to cancel a transaction in the queue, you need to reject it onchain.
When rejecting, confirm your intent by selecting "Yes, reject this transaction" in the pop-up.
Rejecting a transaction is an onchain action.
You will need to sign an onchain rejection message and collect signatures from the required signers.
Once all required signatures are collected, the transaction is rejected (the nonce is burned).
It will then disappear from the queue - for example, after rejecting the "Send 0.5 ETH" transaction, only the other two transactions will remain.
Why does rejecting a transaction require an onchain action and network fees?
Even though rejecting is not common, it is important for security.
It permanently cancels the transaction with onchain proof, preventing any tampering later.
Since Ready Wallet Multisig supports offchain confirmations (signatures stored on our backend), an onchain rejection burns the nonce.
This makes sure that rejected transactions cannot be executed by unauthorized parties later.