This page lists frequent technical questions asked by users like different types of transaction failures, slippage, deadline etc. This is most useful for support teams to answer users’ queries.
Note: If it is a tx failure issue, always ask a user the tx hash/link, check the error in the tx and then check this document to understand which issue happens for which reason. If you are unable to find an answer, make a note on Discord to add it to the FAQs.
Nonce issue
If you see the nonce issue in the tx description, then ask the user to contact the wallet provider. The nonce issue happens on the wallet end. We don’t have control over the nonce.
Insufficient output amount
This happens because of slippage. Whenever a user faces this, check the amount user is trying to swap and which pool she is swapping on. Usually, it is resolved by increasing the slippage tolerance on the swap settings. The usual recommendation is 2%, but it could be higher based on the amount and the liquidity in the pool.
tx expired
This failure happens when the tx deadline is passed before tx could confirm on Starknet. It usually happens when the Starknet is congested and it takes more time than the tx expiry time set by the user. For example user might have set the expiry time to 10 minutes and Starknet might take 20 min to confirm the tx, in that case the tx will fail. In those cases ask the user to increase the tx deadline to a longer period.
Will zap cost any additional fees? No. The only fees charged are the network fees(Ethereum and Starknet gas fee) and trading fee(to convert tokens into pool tokens)
Is JediSwap audited, or what are the audit plans? No, JediSwap is not audited yet. We will go for audits once our contracts are deployed in Cairo 1.0 and go through peer review.
Tokens not loading in swap or add liquidity