Troubleshooting Errors

Dexo Self Troubleshooting

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: 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: insufficient_output_amount.

You're trying to swap tokens, but your slippage tolerance is too low or liquidity is too low.

Solution

1. Refresh your page and try again later.

2. Try trading a smaller amount at one time.

3. Increase your slippage tolerance:

Tap the settings icon on the swap page. Increase your slippage tolerance a little and try again.

4. Lastly, try inputting an amount with fewer decimal places.

Reason

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 that cannot be sold. In this case, Dexo isn't able to block a token or return funds.

Router: EXPIRED

The transaction cannot succeed due to error: Router: 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.

The transaction cannot succeed due to an error: This is probably an issue with one of the tokens you are swapping.

Try modifying the amount on the “To” field. Therefore putting the "(estimated)" symbol on “From”. Then initiate the swap immediately.

TRANSFER_FAILED

The transaction cannot succeed due to an error: execution reverted: TRANSFER_FAILED.

Make sure you have 30% more tokens in your wallet that 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 can not Succeed

Try trading for a smaller amount, or increasing slippage tolerance via the settings icon and try again. This may be caused by the low liquidity available for that pair.

Price Impact Too High

Try trading a smaller amount, or increasing slippage tolerance via the settings icon and try again. This may be caused by the low liquidity available for that pair.

Estimate Gas Failed

This transaction would fail. Please contact support

Solution

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 about the token you're trying to swap. This issue must be resolved by the project team.

Reason

This issue (while swapping) is caused by tokens that have hard-coded the Dexo router into their contract.

While this practice is ill-advised at best, the reason for these projects having done this appears to be due to their tokenomics, in which each purchase sends a % of the token to LPs.

The projects affected will likely not work with the V2 router: they will most likely need to create new versions of their tokens pointing to our new router address, and migrate any existing token holders to their new token.

We recommend that any projects which created such tokens should also make efforts to prevent their users from adding them to V2 LP. The up-to-date router address is

https://bscscan.com/address/0x10ED43C718714eb63d5aA57B78B54704E256024E

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

1. Attempt the transaction again with an increased slippage allowance.

2. If this does not resolve your problem, consider using another wallet such as SafePal for your transaction.

Reason

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.

First Tab

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.

Second Tab

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.

Out of Gas error

Warning! Error encountered during contract execution [out of gas]

You have set a low gas limit when trying to make a transaction.

First Tab

Try manually increasing the gas limit (not gas price!) in your wallet before signing the transaction.

A limit of 200000 is usually enough.

The above example is from Metamask; check your wallet's documentation if you aren't sure how to adjust the gas limit.

Reason

Basically, your wallet (Metamask, Trust Wallet, etc.) can't finish what it's trying to do.

Your wallet estimates that the gas limit is too low, so the function call runs out of gas before the function call is finished.

BEP20: transfer amount exceeds the allowance

Fail with error 'BEP20: transfer amount exceeds allowance'

Solution

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 spending allowance

3. Try interacting with the contract again.

Reason

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.

BEP20: transfer amount exceeds balance

Fail with error 'BEP20: transfer amount exceeds balance'

If not, you may be trying to send tokens that you don't have in your wallet (for example, trying to send a token that is already assigned to a pending transaction). In this case, just make sure you have the tokens you're trying to use.

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 Dexo Exchange

Unsupported Chain ID

Switch your chain to Binance Smart Chain. Check your wallet's documentation for a guide if you need help.

Issues buying SAFEMOON and similar tokens

To trade SAFEMOON, you must click on the settings icon and set your slippage tolerance to 12% or more. This is because SafeMoon taxes a 10% fee on each transaction:

• 5% fee = redistributed to all existing holders

• 5% fee = used to add liquidity

This is also why you might not receive as much of the token as you expect when you purchase. Read more on How to Buy Safe Moon.

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

Issues with Profile

Oops! We couldn't find any Collectibles in your wallet.

We're investigating the logic behind this issue. Meanwhile please try the workaround.

Work Around 1

1. Go to “Collectible” page, then come back to profile page. If you can’t find the link, go to https://nft.dexo.exchange/collectibles directly
2. Retry profile creation.

Second Tab

Change the environment.

• Clear the cache and retry.

• Retry on a different browser.

• Retry on different wallet apps.

• Retry on a different network (switch between Wi-Fi and cellular)

Checking the username keeps spinning

There are two possible causes.

1. You have multiple wallets installed on the browser.

2. Network issue.

Solution 1

Root cause: You have multiple wallets installed on the browser. It may make a conflict between wallets. This is out of Dexo Exchange's control and we can do nothing.

1. Have only a single wallet installed on the browser, remove the others.

2. Reconnect the wallet and retry setting the username again.

Solution 2

Root cause: Network is unstable. You have to retry. 1. Delete whatever has been entered in the text field completely.

2. Re-type username, then please wait for seconds.

3. If it doesn’t work, reload the page and retry again