A stuck transaction means that a user has given away assets on the origin blockchain and gets nothing on the destination blockchain.
A stuck transaction cannot be accomplished; it can be reverted instead.
If you, while doing a cross-chain swap or bridging, did not receive assets on the destination blockchain, please navigate to the Stuck Transaction section of WebApp. The red circle indicates that you have one stuck transaction:
All stuck transactions from all blockchains are listed here:
The transaction will be on the list until you successfully revert it *
* WebApp lists the stuck transactions that happened during the last 10,000 blocks. More ancient transactions can be reverted though they are not shown via WebApp interface. So, if you use WebApp, please do not wait long to perform reverts.
To revert the trade, please press on the Revert icon, confirm the transaction in your wallet and wait a bit to get back you assets.
There are two important things to pay attention to
The reverting transaction is sent to the blockchain where the user has not received assets.
Once the reverting has been accomplished, the user receives stablecoins that may differ from the exchanging token of the origin cross-chain swap.
Let's consider a couple of examples:
A cross-chain swap UNI (Ethereum) -> CAKE (BSC) got stuck. The route for such a cross-chain swap may look like: UNI-> USDC| sUSDC-> BUSD-> CAKE
To revert it, the reverting transaction is sent to BSC, and the user gets USDC on Ethereum.
A cross-chain swap CAKE (BSC) -> UNI (Ethereum) got stuck. The route for such a cross-chain swap may look like: CAKE-> WBNB-> BUSD-> sUSDC| USDC-> WETH-> UNI
To revert it, the reverting transaction is sent to Ethereum, and the user gets sUSDC on BSC.
To illustrate the second example, we set the transaction deadline to a very short time (10 seconds) and perform the following cross-chain swap (CAKE -> UNI):
The sequence of the swaps CAKE-> WBNB-> BUSD-> sUSDC on the origin blockchain (BSC) has been successfully accomplished, but, due to the insane short deadline, the second part of the trade was canceled:
And now we can see this trade on the list of the stuck transactions:
The reverting transaction will be sent to Ethereum (the destination blockchain of our origin trade that got stuck). So, we should have native cryptocurrency on this blockchain to pay the gas fee (ETH in this example).
Once the revert is done, we will get sUSDC tokens on BSC.
Let's revert it > press on the Revert icon and confirm the transaction in the wallet. As soon as the transaction is processed and confirmed:
We get sUSDC tokens on BSC:
Our stuck transaction changed its status from Revert to Reverted:
If you reload the page, the stuck transactions with the Reverted status are gone:
What are sUSDC tokens? sUSDC is an ERC20 token and one of sTokens (wrapped or synthetic tokens) used by the Symbiosis protocol to perform cross-chain swaps. Please refer to Wrapped Token and sToken for more information on sTokens.
What can I do with sTokens? There are three ways to deal with sTokens:
Just keep them,
Swap them to stablecoins on a Symbiosis DEX.
sUSDC tokens from our example can be exchanged for BUSD tokens. Please refer to Dealing with sTokens for instructions on exchanging sTokens.
Become a liquidity provider: add the sTokens to an appropriate liquidity pool, get a reward for providing liquidity and burn them later to get stablecoins on the blockchain that this liquidity pool links to.
sUSDC tokens from our example can be added to the liquidity pool BUSD <> sUSDC located on the BSC network. When we burn sUSDC tokens added to this pool, we get USDC tokens on Ethereum. Please refer to Liquidity Pools for instructions on adding/withdrawing liquidity to/from a liquidity pool.
If you would like to learn more about stuck transactions, please refer to this document.