Approvals
Review open requests, approve or cancel them, and execute signed transactions that are ready to go on-chain. Anyone may read the queue. Acting on a request needs a role that covers that step.
Where: Account → Approvals
What is in the queue
Approvals shows two kinds of item until they are finalised on-chain:
On-chain pending requests posted with Wallet. They wait for the time lock, then for an approval or cancellation.
Stored signed transactions created with Sign, or imported from a signed file. They wait for someone to submit them before they expire.
When there is nothing open the page reads "Nothing open — On-chain requests and off-chain signed payloads appear here until they are finalized on-chain."
Tabs, columns and filters
All (n)
Everything open
Pending (n)
On-chain requests waiting for the time lock or an approval
Approved (n)
Signed transactions waiting for an Execute
Operation
Action name, requester address and age
Change
The decoded effect (amount and asset) where the Platform can decode it, otherwise "—"
State
Time-lock chip: Blocked , left / Ready, Cancel · left, Expired
Action button
Approve, Execute, Delete or View, depending on the item and your wallet
The tabs above and the search box are the only controls that narrow this list; the search box matches on operation and requester.
Approve or cancel a request
Click a Pending row. The Approve request dialog opens with the status chip (for example Awaiting Approval).
Check Requester and the decoded parameters. Advanced settings exposes gas overrides.
In ACTION SUMMARY, pick a method:
Wallet: "Approves or cancels on-chain after the timelock." Your wallet sends the approval transaction and the operation executes in the same step.
Sign: signs an approval or cancellation as a meta-transaction. A broadcaster submits it (the Signed approval path).
Watch TIMELOCK. Blocked means the delay has not run; Approve stays disabled. Unblocked means you may proceed. Cancel is available during the block for roles that may cancel.
Click Approve or Cancel and confirm in your wallet.
The dialog offers three views: Summary (what you see first), Details (raw parameters, selectors, target) and Activity (the timeline of request, approval and execution events).
If your wallet is not permitted, the card says "This wallet cannot approve or cancel with Wallet or Sign for this request. Check roles or try another wallet."
Execute a signed transaction
Rows on the Approved tab open the Signed transaction dialog.
Execute submits the signed payload on-chain. Your connected wallet must be allowed to submit: a Broadcaster, or another role the owner permitted at the Execute step. It pays the gas.
Delete "removes it from local storage only". The signature itself is unaffected; if a copy exists elsewhere it can still be submitted until it expires.
An expired item shows "Expired. Execution disabled. Delete this invalid entry."
Signed transactions are stored in this browser. To move one to another device, use the export and Import signed file flow described in Signed files.
Status label reference
New
Request created locally, not yet posted or signed
Awaiting Approval
On-chain, waiting for an approver
Awaiting Your Approval
Same, and your connected wallet may approve
Approved
Approval signed, waiting for submission
Cancelled
Cancelled on-chain; nothing will execute
Expired
Signature deadline passed; must be redone
Ready to Execute
Signed payload can be submitted now
Ready to Submit Cancellation
Signed cancellation can be submitted now
Executing
Execution transaction sent, waiting for the block
Executed
Operation completed on-chain
Submitting
Signed payload is being broadcast
Pending Confirmation
Transaction in the mempool or too few confirmations
Confirmed
Transaction confirmed on-chain
Failed
Transaction reverted; see History for the hash
Row-level status text uses shorter phrases: Waiting Period, Awaiting Approval, Execution Ready.
Related
Last updated
Was this helpful?