Transaction Lifecycle
As transactions progress from creation through completion, they can follow several workflows, during which they take on various statuses.
Transaction statuses
The table below lists possible Fordefi transaction statuses and their meanings.
| Status | API request response | Meaning |
|---|---|---|
| PENDING APPROVAL | waiting_for_approval | The transaction is pending approval by the designated approvers. The approvers are those designated by relevant policy rules. |
| PENDING SIGNATURE | approved | The transaction was approved and waiting for the relevant signer (initiator/API signer/end user) to sign it. |
| WAITING TO BE PUSHED | signed | The transaction was signed by Fordefi and is waiting to be sent to the blockchain. |
| WAITING TO BE MINED | pushed_to_blockchain | The transaction was signed and pushed into the mempool and is waiting to be mined. Note: Transactions are mined in the order they were submitted to the mempool, per vault and chain. |
| QUEUED | queued | Transactions in Ethereum-based blockchains are mined in order, based on the nonces that were allocated to them. In case there is already a transaction from the same vault in the WAITING TO BE MINED or STUCK state, any new signed transaction will be displayed as QUEUED, to differentiate it from the first one (per vault and chain) that is pending mining. * Transactions with sequential nonces can be mined in the same block. In such a case, the transaction will transition from QUEUED to MINED. |
| MINED | mined | The transaction has been mined - meaning the transaction has been added to the blockchain. Not enough blocks have passed to be considered COMPLETED. |
| COMPLETED | completed | The transaction was completed successfully. |
| STUCK | stuck | The transaction is considered stuck. In Fordefi, a transaction becomes STUCK after it has been in the mempool for over ten minutes. This is usually caused by low fees submitted with the transaction. See Accelerate a Transaction and Cancel a Transaction. |
| ACCELERATING | accelerating | The transaction is being replaced by a transaction with exactly the same parameters and a higher price. |
| CANCELING | canceling | The transaction is being canceled and, in its place, a new effectless transaction is being submitted. |
| ACCELERATED | accelerated | The accelerating replacement transaction was mined. Hence, the original transaction was accelerated successfully. See Accelerate a Transaction. |
| CANCELED | canceled | The canceling replacement transaction was mined. The original transaction was canceled successfully. See Cancel a Transaction. |
| ABORTED | aborted | The user who initiated the transaction aborted it. It is possible only if the transaction is PENDING APPROVAL or PENDING SIGNATURE (approved). Afterwards, the transaction is pushed to the blockchain and aborting is not possible anymore -- only cancelation. |
| DROPPED | dropped | A transaction is DROPPED if, within two minutes after it has been sent to the chain, it is not mined. Currently only on the Solana blockchain. |
| ERROR PUSHING TO CHAIN | error_pushing_to_blockchain | An error occurred and the transaction was not pushed to the blockchain. |
| MINED REVERTED | mined_reverted | The transaction has been mined but reverted -- meaning the transaction has been added to the blockchain. Not enough blocks have passed to be considered COMPLETED REVERTED. Usually, the transaction is reverted because of an error in the contract or the way in which the transaction was generated. |
| COMPLETED REVERTED | completed_reverted | The transaction was reverted. Usually, this is because of an error in the contract or the way in which the transaction was generated. |
Mined delay
When transactions are sent to the mempool, they wait to be picked up by a miner and included in a block. However, due to possible forks (where two or more blocks were produced at the same time and one of them will eventually be dropped and not included in the chain), Fordefi keeps a buffer and finds the right balance between showing the most updated status of the transaction, while being as safe as possible from forks.
To provide more information about the current state of the block, Fordefi assigns one of two statuses:
- MINED: Indicates that the transaction has been included in the chain after the specified number of blocks has been mined.
- COMPLETED: Indicates that the transaction has been included in the chain after the specified number of blocks has been mined and now the chances of a fork are practically at zero.
For EVM chains, the expected time to pass until the transaction is mined is about 12 seconds and 60 seconds for completion.
| Functionality | Network | Type | Number of blocks until MINED | Number of blocks until COMPLETED | Seconds between blocks |
|---|---|---|---|---|---|
| Mainnet | Arbitrum One | EVM | 10 | 50 | 0-1 |
| Avalanche | EVM | 5 | 25 | 2 | |
| Base | EVM | 6 | 30 | 2 | |
| BNB Chain | EVM | 4 | 20 | 3 | |
| Blast | EVM | 3 | 30 | 2 | |
| Canto | EVM | 2 | 10 | 6 | |
| Conflux | EVM | 5 | 50 | 1 | |
| Dymension | EVM | 2 | 10 | 6 | |
| Ethereum | EVM | 1 | 5 | 12 | |
| Fantom | EVM | 10 | 50 | 1 | |
| Gnosis | EVM | 20 | 100 | 10 | |
| Kava | EVM | 2 | 10 | 6 | |
| Linea | EVM | 1 | 5 | 12 | |
| Manta Pacific | EVM | 1 | 6 | 10 | |
| Mantle | EVM | 40 | 200 | < 1 | |
| Merlin | EVM | 7 | 36 | 1.67 | |
| Optimisim | EVM | 5 | 25 | 1-2 | |
| Polygon zkEvm | EVM | 25 | 25 | ~120 (batches) | |
| Scroll | EVM | 2 | 10 | 6 | |
| Xai | EVM | 8 | 42 | 1-2 | |
| zkLink Nova | EVM | 6 | 25 | 4 | |
| zkSync Era | EVM | 6 | 30 | 2 | |
| Solana | Solana | 1 | 30 | 0.4 | |
| Akash | Cosmos | - | 1 | 6 | |
| Archway | Cosmos | - | 1 | 6 | |
| Axelar | Cosmos | - | 1 | 6 | |
| Celestia | Cosmos | - | 1 | 12 | |
| Cosmos Hub | Cosmos | - | 1 | 6 | |
| dYdX | Cosmos | - | 1 | 1 | |
| Dymension | Cosmos | - | 1 | 6 | |
| Noble | Cosmos | - | 1 | 6 | |
| Osmosis | Cosmos | - | 1 | 7 | |
| Sei | Cosmos | - | 1 | 0.5 | |
| Stride | Cosmos | - | 1 | 6 | |
| Bitcoin | Bitcoin | 1 | 2 | 600 | |
| Testnet | Arbitrum Sepolia | EVM | 10 | 50 | 0-1 |
| Flare | EVM | 6 | 46 | 1-2 | |
| Mumbai | EVM | 5 | 25 | 6 | |
| Sepolia | EVM | 1 | 5 | 15 | |
| Goerli | EVM | 1 | 5 | 15 | |
| Solana devnet | Solana | - | 10 | 0.4 | |
| Bitcoin Testnet | Bitcoin | 1 | 10 | 600 |
Transaction workflow
The schematic below describes the transaction workflow and possible outcomes.
Updated 4 days ago