Get Route Status
This method aims to provide the status of the transaction
Squid Combines Axelar's infrastructure as well as some bespoke on-chain analytics to provide status of cross-chain transactions. You can access this status using the getStatus
method on our SDK.
You can also check completion of most cross chain transactions on Squid by copying the transaction hash into AxelarScan. Note, for some Cosmos transactions and others in the future this will not work.
Type: #getstatus
Request Param:
transactionId
Transaction hash from the transaction submitted to the source chain.
requestId (optional)
Unique request id returned in getRoute response param, e.g. 340c79f3-4f63-4d72-a6e6-3b70edfd3fe3
integratorId (optional)
Unique Integrator Id for integration e.g.
squid-swap-widget
fromChainId
From chain identifier
toChainId
To chain identifier
The most important response param is squidTransactionStatus
This param will tell you what to show the user. There are 5 possible states:
SUCCESS
This indicates the transaction has completed on all chains. Whether a single chain, 2 chain or 3 chain call, the swap, stake, NFT purchase, bridge etc. has completed without any reversions and the user has received the intended funds.
NEEDS_GAS
This state is specific for Axelar transactions. If the gas price has spiked on the destination chain and execution cannot complete, Squid will return this status. The best user flow in this case is to send the user to Axelarscan to view the paused transaction.
ONGOING
There is nothing wrong, nothing to do, just relax and wait. The transaction should have an estimatedRouteDuration in seconds that you can read from the /route response. We generally recommend contacting support after either 15 minutes has passed, or double the estimatedRouteDuration, whichever is larger.
PARTIAL_SUCCESS
This status indicates that the transaction has completed some of its steps. Currently, there is only one case that could cause this state. In the future there will be many, but we will provide more metadata around the PARTIAL_SUCCESS. For now, this is what has happened:
The source chain transaction successfully executed, along with any swaps or contract calls.
The destination chain transaction has executed, but reverted during execution. This is usually due to slippage on volatile assets, but if you are trying to buy an NFT or do some cross-chain staking, then it could indicate that the custom hook had a failure.
If there is a partial success, the user will have received the bridged token in their wallet on the destination chain. In most cases this is axlUSDC.
NOT_FOUND
The Squid API cannot find an on-chain record of the transaction. This is usually due to our various services or service providers not having indexed the completed transaction. This state is often returned for 5-10 seconds after the transaction was executed, while chain indexing occurs.
This should not persist after maximum a few minutes (some chains such as Filecoin take a very long time to index, and for block inclusion). If it does, then get in touch with us on Discord.
How to share block explorer links
Generally, the best thing to do is to share https://axelarscan.io/gm/<txHash> with a user.
With the caveat that if you are doing a transaction between two Cosmos chains, this link may not be correct. For now we simply recommend you always using this approach, we are upgrading our status capability and the status endpoint will always return the correct block explorer link to share.
Response Param:
id
transaction hash
status
Transaction status from Axelarscan:
Our status endpoint aggregates AxelarScan's GMP and token transfer responses.
Depending on transaction type, possible responses are as below:
GMP responses for status
Token transfer responses for status
:
gasStatus
Transaction gas status returned from AxelarScan. The possible gas status response are:
isGMPTransaction
Returns true
if the transaction is a GMP transaction, false
if it is a bridge transfer
fromChain.transactionId
Chain ID of fromChain
fromChain.blockNumber
Transaction block number on fromChain
fromChain.callEventStatus
SquidMulticall contract event status relating to transactionId
on fromChain
fromChain.callEventLog
SquidMulticall event logs for transactionId
on fromChain
toChain.transactionId
Transaction hash on toChain
toChain.blockNumber
Transaction block number on toChain
toChain.callEventStatus
Latest SquidMulticall event status on toChain
toChain.callEventLog
SquidMulticall
event logs on toChain
error
Error returned from Axelarscan GMP API
timeSpent
Time spent on transaction execution
requestId
Request Id passed into Get Route
integratorId
Integrator Id passed into GetRoute
squidTransactionStatus
Simplified status for transaction. It could be either of the value
Example:
You can also access the Axelar GMP block explorer to monitor your transaction status.
Last updated