Transaction status
Last updated
Last updated
Status | Explanation | Details |
---|---|---|
Please find below list of potential errors that could lead to a failed transaction
Major Causes of Occurrence | Failure operation | Occurrence location (src/dst) |
---|---|---|
Pending
Waiting for user interaction
approve from wallet or changing network will trigger this status
Count down
Estimate time of transaction completion
Please note that this is an estimate and wont indicate a precise time of transfer completion
Completed
Transaction is completed
Your transfer is completed, you can check your wallet
Failed
In rare case, a transaction can failed. The reason of transaction failure can be multiple like destination chain 3rd party contract, liquidity pool, etc..
TOKI has currently set an expiration of 24h for a transaction . If after 24 hour the transaction is still processing, the status will changed for failed. This will update while in Testnet phase
Destination side transfer Token has stopped remittance.
Receiving via pool (e.g., USDC) or Receive Token (eg. TOKI)
destination chain
Src side Token has stopped remittance.
Receive Token (eg. TOKI) via WithdrawConfirm
Source chain
External Contract call is failing.
External Contract call for WithdrawConfirmability via Receive (eg. TOKI) of ComposToken
destination chain
Lack of native coin liquidity in Bridge
Gas on Destination
destination chain
External Contract call is failing.
or
Lack of native coin liquidity in Bridge
External Contract Call for Composability & Gas on Destination
destination chain
Lack of native coin liquidity in Bridge
wont be able to Approve
Source chain
Rate limit
transaction protection when multiple tx is sent in a laps of time. This measure is to protect against hack
destination chain