If you experience difficulties in work with QuipuSwap, please check the following info:
- Do you have enough XTZ to conduct an operation and pay a transaction fee? Check that you have at least 0.5 XTZ left for commissions.
- If your transactions have failed please read this article
- If you work with small liquidity pools, be sure that you have increased a Slippage tolerance and set up at least 3%. Also, you need to swap not more than 30% liquidity pool tokens in one transaction.
- In case you want to create a new liquidity pool, you need to pay a storage fee (around 7 XTZ). Check if you have enough balance in your wallet and follow this guide.
- Sometimes your wallet or QuipuSwap can't connect to the Node. In this case, you need to try to conduct a swap operation a little bit later. Also, if you use the Temple wallet, you can change a default node in the settings.
- If you are trying to add a Liquidity and get a "Transaction backtracked" you need to repeat this operation later (read more in the "error messages" section).
- Check that your wallet and QuipuSwap use the Tezos Mainet network.
Some error messages may describe multiply issues, however, the most common are provided here:
- Error: "Dex/wrong-min-out"
Means that while the transaction was running, the state in the pool changed. And the amount that was specified in the transaction is no longer relevant.
This issue can be mitigated by increasing slippage.
- "Simulation error: A FAILWITH instruction was reached > Dex/dust-output".
A possible problem is that you are trying to remove liquidity with the wrong params. For example, you request a too small or too large token amount.
This error may also appear when designated slippage is too low.
- "Something went wrong" - possible issue with the Node connection. Try to conduct an operation again.
- "Transaction backtracked" - usually happens for batched transactions when one of the transactions failed, so the others get backtracked, and you see backtracked status for the transaction in your wallet.
Why is it happen for QuipuSwap?
The main reason is that the pool's price conditions were changed and info added to the batched transaction became irrelevant, and the Tezos Node refused to execute this transaction. As we know, every new Tezos block is created in one minute, and during this time - conditions in the pool may be changed. Despite the fact that a transaction failed - you will pay a transaction fee.
What to do? Unfortunately, not too much. You need to repeat the desired operation a little bit later.
- "Transaction pending"
This problem indicates that the Tezos node hasn't included this transaction in the blockchain block.
It may be happen for many reasons. Some of them are:
- Sometimes the Tezos node lags and can't synchronize the current transaction fee with other nodes. So, this node provides a low transaction fee estimation for the transaction, and bakers don't want to include this transaction in the block. Usually, this transaction fails after some time.
- The Tezos Node Stuck/Failed. In this situation, the node does not even inform other network participants about the existence of this pending transaction. As a result, this transaction doesn't exist for the blockchain, and you don't see it in the explorer block.
How to solve this issue?
Almost 99% that your pending transaction will fail, so you should don't wait and perform a transaction again.
- For the full list of possible errors that may be happen in the process of work with smart contract you can find in this document.
If nothing helps:
What operations are you trying to conduct (swap, add/remove liquidity)
The token address, which are you trying to swap
A problem description
What an error message do you receive?
What a browser and wallet do you use?