Troubleshooting Errors

Search…
Common error messages. Use the sidebar ➡️to jump to the error you're seeing.
​
Sometimes you may find yourself facing a problem that doesn't have a clear solution. These troubleshooting tips may help you solve problems you run into.
Issues on the Exchange
​
INSUFFICIENT_OUTPUT_AMOUNT
The transaction cannot succeed due to error: SwychRouter: INSUFFICIENT_OUTPUT_AMOUNT. This is probably an issue with one of the tokens you are swapping.
the transaction cannot succeed due to error: execution reverted: swychrouter: insufficient_output_amount.
You're trying to swap tokens, but your slippage tolerance is too low or liquidity is too low.
Solution
Reason
1.Refresh your page and try again later.
2.Try trading a smaller amount at one time.
3.Increase your slippage tolerance:
1.Tap the settings icon on the liquidity page.
2.Increase your slippage tolerance a little and try again. 
4.Lastly, try inputting an amount with fewer decimal places.
This usually happens when trading tokens with low liquidity.
That means there isn't enough of one of the tokens you're trying to swap in the Liquidity Pool: it's probably a small-cap token that few people are trading.
However, there's also the chance that you're trying to trade a scam token which cannot be sold. In this case, Swych isn't able to block a token or return funds.
INSUFFICIENT_A_AMOUNT or INSUFFICIENT_B_AMOUNT
Fail with error 'SwychRouter: INSUFFICIENT_A_AMOUNT'
or
Fail with error 'SwychRouter: INSUFFICIENT_B_AMOUNT'
You're trying to add/remove liquidity from a liquidity pool (LP), but there isn't enough of one of the two tokens in the pair.
​
Solution
Reason
Solution for nerds
Refresh your page and try again, or try again later.
Still doesn't work?
1.Tap the settings icon on the liquidity page.
2.Increase your slippage tolerance a little and try again.
The error is caused by trying to add or remove liquidity for a liquidity pool (LP) with an insufficient amount of token A or token B (one of the tokens in the pair).
It might be the case that prices are updating too fast when and your slippage tolerance is too low.
​
OK, so you're really determined to fix this. We really don't recommend doing this unless you know what you're doing.
There currently isn't a simple way to solve this issue from the Swych website: you'll need to interact with the contract directly. You can add liquidity directly via the Router contract, while setting amountAMin to a small amount, then withdrawing all liquidity.
Approve the LP contract
Head to the contract of the LP token you're trying to approve.
For example, here's the ETH/WBNB pair: https://bscscan.com/address/0x70d8929d04b60af4fb9b58713ebcf18765ade422​
1.Select Write Contract, then Connect to Web3 and connect your wallet. 
​
2.In section "1. approve", approve the LP token for the router by entering
1.spender (address): enter the contract address of the LP token you're trying to interact with
2.value (uint256): -1
Query "balanceOf"
1.Switch to Read Contract.
2.In 5. balanceOf, input your wallet address and hit Query.
3.Keep track of the number that's exported. It shows your balance within the LP in the uint256 format, which you'll need in the next step.
Add or Remove Liquidity
Head to the router contract: https://bscscan.com/address/0x05ff2b0db69458a0750badebc4f9e13add608c7f#writeContract​
1.Select Write Contract and Connect to Web3 as above.
2.Find addLiquidity or removeLiquidity (whichever one you're trying to do)
3.Enter the token addresses of both of the tokens in the LP.
4.In liquidity (uint256), enter the uint256 number which you got from "balanceOf" above.
5.Set a low amountAMin or amountBMin: try 1 for both.
6.Add your wallet address in to (address).
7.Deadline must be an epoch time greater than the time the tx is executed.
This can cause very high slippage, and can cause the user to lose some funds if frontrun
SwychRouter: EXPIRED
The transaction cannot succeed due to error: SwychRouter: EXPIRED. This is probably an issue with one of the tokens you are swapping.
Try again, but confirm (sign and broadcast) the transaction as soon as you generate it.
This happened because you started making a transaction, but you didn't sign and broadcast it until it was past the deadline. That means you didn't hit "Confirm" quickly enough.
Swych: K
The transaction cannot succeed due to error: Swych: K. This is probably an issue with one of the tokens you are swapping.
Try modifying the amount on “To” field. Therefore putting "(estimated)" symbol on “From”. Then initiate the swap immediately.
This usually happen when you are trying to swap a token with its own fee.
SWYCH: TRANSFER_FAILED
The transaction cannot succeed due to error: execution reverted: Swych: TRANSFER_FAILED.
Make sure you have 30% more tokens in your wallet than you intend to trade, or try to trade a lower amount. If you want to sell the maximum possible, try 70% or 69% instead of 100%.
Caused by the design of Restorative Rebase tokens like tDoge or tBTC.
Understand how restorative rebase tokens work.
Another possible cause of this issue is the malicious token issuer just suspended the trading for their token. Or they made selling action only possible for selected wallet addresses. Please always do your own research to avoid any potential fraud. If the token you are trying to swap but failed with this error code is coming from an airdrop, that is most likely a scam. Please do not perform any token approval or follow any links, your fund may be at risk if you try to do so.
Transaction cannot succeed
Try trading a smaller amount, or increase slippage tolerance via the settings icon and try again. This is caused by low liquidity.
Price Impact too High
Try trading a smaller amount, or increase slippage tolerance via the settings icon and try again. This is caused by low liquidity.
​
estimateGas failed
This transaction would fail. Please contact support
Solution
Reason
If you got this error while removing liquidity from a BNB pair:
Please select "Receive WBNB" and retry.
If you got this error while trying to swap:
Please contact the project team of the token you're trying to swap. **** This issue must be resolved by the project team.
This issue (while swapping) is caused by tokens which have hard-coded the Swych router into their contract.
This is the official Swych router that must be used in order not to create these problems
The up-to-date router address is 
​https://bscscan.com/address/0x2Bf55D1596786F1AE8160e997D655DbE6d9Bca7A​
Cannot read property 'toHexString' of undefined
"Unknown error: "Cannot read property 'toHexString' of undefined"
When trying to swap tokens, the transaction fails and this error message is displayed. This error has been reported on mobile devices using Trust Wallet.
​
Solution
Reason
Attempt the transaction again with increased slippage allowance.
If 1. does not resolve your problem, consider using another wallet such as SafePal for your transaction
This usually happens when trading tokens with insufficient slippage allowance on Trust Wallet.
The exact details of the problem are still being investigated.
Execution reverted: TransferHelper: TRANSFER_FROM_FAILED.
The transaction cannot succeed due to error: execution reverted: TransferHelper: TRANSFER_FROM_FAILED.
When trying to swap tokens, the transaction fails and this error message is displayed. This error has been reported across platforms.
​
Solution
Reason
1.Check to make sure you have sufficient funds available.
2.Ensure you have given the contract allowance to spend the amount of funds you're attempting to trade with.
This error happens when trading tokens with insufficient allowance, or when a wallet has insufficient funds.
If you're trading tokens with Restorative Rebase like tau assets tDoge or tBTC, make sure you understand how they work first with this guide to Rebase tokens.
​
BEP20: transfer amount exceeds allowance
Fail with error 'BEP20: transfer amount exceeds allowance'
​
Solution
Reason
1.Use Unrekt.net to revoke approval for the smart contract you're trying to interact with
2.Approve the contract again, without setting a limit on spend allowance
3.Try interacting with the contract again.
This happens when you set a limit on your spend allowance when you first approved the contract, then try to swap more than the limit.
​
Other issues
Provider Error
Provider Error
No provider was found
This happens when you try to connect via a browser extension like MetaMask or Binance Chain Wallet, but you haven’t installed the extension.
Solution
Install the official browser extension to connect, or read our guide on how to connect a wallet to Swych.
Unsupported Chain ID
Switch your chain to BNB Smart Chain. Check your wallet's documentation for a guide if you need help.
Already processing eth_requestAccounts. Please wait.
Make sure you are signed in to your wallet app and it's connected to BNB Smart Chain.
Issues buying Titano and similar tokens
To trade TITANO, you must click on the settings icon and set your slippage tolerance to 13% or more.
This is because Titano taxes a 13% fee on each buy transaction:
Buy Trading Fees: 3% - RFV (Risk Free Value). 5% - Liquidity Sustain. 5% - Treasury. 
​
This is also why you might not receive as much of the token as you expect when you purchase.
Internal JSON-RPC errors
"MetaMask - RPC Error: Internal JSON-RPC error. estimateGas failed removeLiquidityETHWithPermitSupportingFeeOnTransferTokens estimateGas failed removeLiquidityETHWithPermit "
Happens when trying to remove liquidity on some tokens via Metamask. Root cause is still unknown. Try using an alternative wallet.
Internal JSON-RPC error. { "code": -32000, "message": "insufficient funds for transfer" } - Please try again.
You don't have enough BNB to pay for the transaction fees. You need more BEP-20 network BNB in your wallet.
​
Error: [ethjs-query]
Error: [ethjs-query] while formatting outputs from RPC '{"value":{"code":-32603,"data":{"code":-32000,"message":"transaction underpriced"}}}"
Increase the gas limit for the transaction in your wallet. Check your wallet's documentation to learn how to increase gas limit.
Swap failed: Error: [ethjs-query] while formatting outputs from RPC '{"value":{"code":-32603,"data":{"code":-32603,"message":"handle request error"}}}'
Cause unclear. Try these steps before trying again:
1.Increase gas limit
2.Increase slippage
3.Clear cache