Transaction States
The status sequence shared by every on-chain action in the application, and what each state means.
Almost every action in this section ends in a transaction, and they all follow the same sequence. Rather than repeat it on each page, here it is once.
The sequence#
- You select an action.
- The application validates your input.
- The application asks you to confirm.
- Your wallet displays the approval request.
- You approve or reject it.
- The application submits the transaction.
- The application shows a pending status.
- The application waits for blockchain confirmation.
- The application shows success or failure.
- The relevant data refreshes.
The states#
| State | What it means |
|---|---|
| Ready | Input is valid and the action can be submitted. |
| Awaiting confirmation | The request is with your wallet, waiting for you. |
| Rejected | You declined the request in your wallet. Nothing was submitted. |
| Submitting | The transaction is being sent to the network. |
| Pending | Submitted and waiting to be included in a block. |
| Successful | Confirmed on chain. The application refreshes the affected data. |
| Failed | Submitted but did not succeed. |
Rejected and failed are not the same#
Rejected means nothing reached the network, so nothing changed and you paid no gas. Failed means the transaction was submitted and then reverted, which does cost gas even though the intended change did not happen.
That distinction matters when something goes wrong: a rejection is usually just a mis-click and safe to retry immediately, while a failure means a condition was not met, such as a slippage bound being exceeded, a cooldown not having passed, or an allowance not being in place. Read the failure reason before retrying, because retrying the same transaction unchanged will usually fail the same way.
Last updated:
Edit this page (opens in a new tab)